[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#847524: ITP: distributed -- Dask Distributed computing for Python



On Thu, 08 Dec 2016 16:20:15 -0800
Diane Trout <diane@ghic.org> wrote:

> Package: wnpp
> Severity: wishlist
> Owner: Diane Trout <diane@ghic.org>
> 
> * Package name    : distributed

The package's name is really unfortunate: the word "distributed" is too
broad, and in our era of everything distributed squatting on it is a
very bad idea IMO.  Please consider naming it dask-distributed
or python-dask-distributed instead.

I would say the same applies to the prospective packages of the
dependencies of this one: sticking "python-" in front of their names
would be a sensible thing to do -- just do

  $ apt search ^python-

to get an overview.

>   Version         : 1.14.3
>   Upstream Author : Matthew Rocklin <mrocklin@gmail.com>
> * URL             : https://distributed.readthedocs.io/en/latest/
> * License         : BSD-3-Clause
>   Programming Lang: Python
>   Description     : Dask Distributed computing for Python
> 
>  Dask.distributed is a lightweight library for distributed computing
> in Python. It extends both the concurrent.futures and dask APIs to
>  moderate sized clusters.

If this bit:

> This is the distributed component of dask, and looks really useful.
> 
> Who wouldn't want some APIs that parallize over multiple machines
> random python code, numpy and pandas?
> 

...is a part of the extended package's description, it should be
reworded: package descriptions should be neutral, dry and up to the
point.  That is, passages like "looks really useful" and "Who wouldn't
want to use this piece of software?" are unfit for the purpose.


Reply to: