[Python-ideas] Moving development out of the standard library

Tarek Ziadé ziade.tarek at gmail.com
Mon Jun 7 21:57:26 CEST 2010

On Mon, Jun 7, 2010 at 9:39 PM, Ian Bicking <ianb at colorstudy.com> wrote:
> On Mon, Jun 7, 2010 at 2:36 PM, Tarek Ziadé <ziade.tarek at gmail.com> wrote:
>> On Mon, Jun 7, 2010 at 9:20 PM, Ian Bicking <ianb at colorstudy.com> 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,

yes, in other word, it's part of the stdlib

> 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?

Distutils2 will behave exactly like other packages in the standard
library. That is:

- the development is going on in trunk
- bug fixes are backported to older python releases that have this
package present
- some feature or small refactoring are also backported when it makes sense

So Python 3.3.2 will have Distutils 3.3.2, but also os.path 3.3.2, and
shutil 3.3.2
Like Python 3.4 its own versions.

Now for older versions of Python, I will provide a backport at PyPI,
so people can use
it under Python 2.x. This backport will probably be made with the
trunk so the 2.x line has the latest
code. IOW the latest 2.7 release might be more advanced than the one
provided in 3.3 for example,
but I don't see this as a problem.


Tarek Ziadé | http://ziade.org

More information about the Python-ideas mailing list