Depend on dask-core not dask

[conda-forge-admin]

The dask dependency drags in distributed which is rather huge for most people.

Hi! This is the friendly automated conda-forge-webservice.

I've started rerendering the recipe as instructed in #16.

If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!

Here's a checklist to do before merging.

• Bump the build number if needed.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[hmaarrfk]

Thank you for considering

[hmaarrfk]

versioneer bites again!

[jakirkham]

Thanks Mark! 🙏

Would like to see dask-core adopt some constraints (say to numpy or other dependencies) to make this more manageable ( conda-forge/dask-core-feedstock#171 )

Unfortunately with the current approach (not on you to solve though), users are left to figure these out on their own, which is subpar

Sadly that doesn't seem to have gotten much attention

Edit: Wonder if this should just be an upstream Dask issue at this point

[hmaarrfk]

I feel like there has been some turn over at dark and maybe we can revive the effort for the split packages.

not sure if you want me to upstream these current patches or workarounds.

it's the standard versioneer issues and distutils version

[jakirkham]

FWIW there was some discussion here: conda-forge/dask-core-feedstock#173 (comment)

The feedback was essentially to try and complete the work in PR: conda-forge/dask-feedstock#172

Maybe someone who is interested can pick that up