[Python-Dev] PEP 384 accepted

"Martin v. Löwis" martin at v.loewis.de
Sat Dec 4 20:43:27 CET 2010

> At the language summit it was proposed and seemed generally accepted (maybe
> I took silence as consent... it's been almost a year now) that bold new
> modules (and bold rewrites of existing modules since it fell out of the
> distutils/2 discussion) should get implemented in a module on pypi before
> being merged into the python stdlib.  If you wouldn't want to work on any of
> those modules until they were actually integrated into Python, it sounds
> like you disagree with that as a general practice?

No - I just don't feel responsible for projects outside of CPython
(unless I have an interest in the project as a user, i.e. to scratch my
own itches). I have no use for a distutils2 package whatsoever - to
install Python packages, I would either use the builtin distutils
(preferred), or setuptools, or distribute (if the package author
requires setuptools).

I agree that new functionality should stand on its own merits first.
And if it fails that test (i.e. it doesn't get much attraction from
users when stand-alone), it shouldn't be included into Python at all.

Now, distutils2 is different: it's *not* new functionality. So perhaps
yes: I disagree with the principle that bold rewrites should be
developed independently. Such work would be much better carried out in a
branch - it will never stand on its own.


More information about the Python-Dev mailing list