Thomas Wouters wrote: > > I've got a few distutils fixes pending (the unixcompiler thing, and > Just/Jack mentioned a few Mac/Metroworks fixes they wanted in) but I'm not > sure how to handle this; distutils has a separate version number, and I seem > to recall it is/was developed seperately. Basically I'm distutils-ignorant, > as I hardly have a need to distribute my scripts :) > > Anyway, should I apply the fixes and up the version number ? Apply the fixes > but keep quiet about them ? Hand the fixes over to someone with distutils > clue ? Scream and shout ? (Always my favorite, that ;P) > > (BTW, Jack, Just, I'm waiting for one of you to follow up on the metroworks > thing; just mail me the patches, preferably written in blood, with a signed > confession that they won't break any code what so ever :-) Why not simply include the latest stable distutils version in Python 2.1.1 and add the new patches/features to the next distutils release (which would then go into 2.1.2, etc.) ? -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Consulting & Company: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4