Doug Davis

[`pkg_resources` is part of `setuptools`](https://setuptools.pypa.io/en/latest/pkg_resources.html) (news to me!) and its use is "discouraged" in favor of `importlib` from the stdlib. (so developers can use [whatever packaging library they prefer](https://peps.python.org/pep-0621/#entry-points), not...

Hey @jrbourbeau! The motivation is a bit multidimensional. In general a group of Dask contributors that were at the SciPy sprint last week discussed improving CLI based on some feedback...

Matthew Rocklin ***@***.***> writes: > From my perspective this needs docs, and then we should drop anything that isn't implemented (info). I'm good to merge after that. OK that also...

> we should drop anything that isn't implemented (info). Just for reference, `info` is actually being used as a group that can have command children. So far we are using...

> I'd be interested to explore how much work it would be to also support existing tools that just use `argparse`, is there some kind of type check we can...

> Not all of them do. Dask Yarn and Dask Gateway both have argparse CLI tools. Ah I did not realize more than what's in distributed exists, thanks for pointing...

Alright I think this is ready for review. The partner PR (dask/distributed#6735) should go in with this one, but it relies on installing my dask branch associated with this PR...

thanks @jacobtomlinson! Added a few commits to address those comments

Thanks for the reproducer, @epizut! Adding a full traceback for reference: traceback ```python In [1]: import dask.datasets In [2]: df = dask.datasets.timeseries() In [3]: df = df.map_partitions( ...: lambda part:...

Thanks for writing this up, @rjzamora! Wanted to mention that you have a couple of links to issue 6028 in dask/dask instead of in dask/distributed