[Python-Dev] Raising objections (was: setuptools in the stdlib)

Neal Norwitz nnorwitz at gmail.com
Wed Apr 19 06:10:20 CEST 2006


On 4/18/06, M.-A. Lemburg <mal at egenix.com> wrote:
> Phillip J. Eby wrote:
> > As for discussion, Guido originally brought up the question here a few
> > months ago, and it's been listed in PEP 356 for a while.  I've also
> > posted things related to the inclusion both here and in distutils-sig.
>
> I know, but the discussions haven't really helped much in
> getting the setuptools design compatible with standard
> distutils.

I'm glad to see the discussions taking place; better late than never. 
However, I think we need to do a better job raising objections
earlier.  I'm not sure how to do this, but one way is to use PEPs. 
There is an outstanding issues section in the 2.5 release PEP 356.  In
this case, perhaps it would have been good to add a bullet item there.
 I've been trying to ensure the issues aren't lost.  There's only one
item in the list that still needs addressing (Fred, you listening? 
You had an idea for solving the problem).

I plan to start a 2.6 release schedule PEP soon (before 2.5 is
released).  It will mostly be a place holder/boilerplate until it can
be filled out when a major feature is implemented, a PEP accepted, or
outstanding issue raised.  The PEP should be updated by a committer
when any of those occur.

If anyone has better ideas how to ensure the issues aren't lost and
are addressed, I'd like to know.

n


More information about the Python-Dev mailing list