On Mon, Jun 7, 2010 at 2:36 PM, Tarek Ziadé
On Mon, Jun 7, 2010 at 9:20 PM, Ian Bicking
wrote: [..] 1. How will distutils2 updates be made available between Python releases? 2. How will distutils2 features be made available in older Python releases?
Why are you expecting any of these to happen? I don't know what Tarek intends to do in that respect, but he certainly doesn't have any moral obligation to do external releases.
distutils2 won't be in 2.7 at least, and any packaging system not available for Python 2 would be irrelevant.
Distutils2 will be provided for Python 2.4 to 3.x with frequent releases.
Then, once it's added in 3.2 (maybe 3.3 if not ready by then), its release cycle will be driven by Python's one, with backports released at the same pace for Python versions that didn't have it in the stdlib.
So let's say distutils2 gets version parity with Python, so distutils2 3.3 is released with Python 3.3. Then distutils2 3.4 is released with Python 3.4, and is backported to all previous versions of Python... except for Python 3.3, which will always have distutils2 3.3? -- Ian Bicking | http://blog.ianbicking.org