Hello,
This is a follow-up of the Pycon summit + sprints on packaging.
This is what we have planned to do:
- refactor distutils in a new standalone version called distutils2 [this is done already and we are actively working in the code]
- completely revert distutils in Lib/ and Doc/ so the code + doc is the same than the current 2.6.x branch
- leave the new sysconfig module, that is used by the Makefile and the site module
The rest of the work will happen in distutils2 and we will try to release a version asap for Python 2.x and 3.x (2.4 to 3.2), and the goal is to put it back in the stdlib in Python 3.3
Distutils in Python will be feature-frozen and I will only do bug fixes there. All feature requests will be redirected to Distutils2.
I think the easiest way to manage this for me and for the feedback of the community is to add in bugs.python.org a "Distutils2" component, so I can start to reorganize the issues in there and reassign new issues to Distutils2 when it applies.
Regards Tarek
-- Tarek Ziadé | http://ziade.org
On Fri, Feb 26, 2010 at 13:44, Tarek Ziadé ziade.tarek@gmail.com wrote:
Hello,
This is a follow-up of the Pycon summit + sprints on packaging.
This is what we have planned to do:
- refactor distutils in a new standalone version called distutils2 [this is done already and we are actively working in the code]
- completely revert distutils in Lib/ and Doc/ so the code + doc is the same than the current 2.6.x branch
- leave the new sysconfig module, that is used by the Makefile and the site module
The rest of the work will happen in distutils2 and we will try to release a version asap for Python 2.x and 3.x (2.4 to 3.2), and the goal is to put it back in the stdlib in Python 3.3
Distutils in Python will be feature-frozen and I will only do bug fixes there. All feature requests will be redirected to Distutils2.
I think the easiest way to manage this for me and for the feedback of the community is to add in bugs.python.org a "Distutils2" component, so I can start to reorganize the issues in there and reassign new issues to Distutils2 when it applies.
I assume you want the Distutils2 component to auto-assign to you like Distutils currently does? If so I can add the component for you if people don't object to the new component.
-Brett
Regards Tarek
-- Tarek Ziadé | http://ziade.org
Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org
On Fri, Feb 26, 2010 at 11:13 PM, Brett Cannon brett@python.org wrote: [..]
I assume you want the Distutils2 component to auto-assign to you like Distutils currently does? If so I can add the component for you if people don't object to the new component.
Sounds good -- Thanks
On Fri, Feb 26, 2010 at 14:15, Tarek Ziadé ziade.tarek@gmail.com wrote:
On Fri, Feb 26, 2010 at 11:13 PM, Brett Cannon brett@python.org wrote: [..]
I assume you want the Distutils2 component to auto-assign to you like Distutils currently does? If so I can add the component for you if people don't object to the new component.
Sounds good -- Thanks
Done.
-Brett
Just FYI : I am post-poning the revert of Distutils to 2.6.x right after 2.7a4 has been tagged to avoid any problems (this is in 3 days)
The revert is ready but 3 days is not long enough to make sure everything is going smooth.
On Fri, Feb 26, 2010 at 10:44 PM, Tarek Ziadé ziade.tarek@gmail.com wrote:
Hello,
This is a follow-up of the Pycon summit + sprints on packaging.
This is what we have planned to do:
- refactor distutils in a new standalone version called distutils2 [this is done already and we are actively working in the code]
- completely revert distutils in Lib/ and Doc/ so the code + doc is the same than the current 2.6.x branch
- leave the new sysconfig module, that is used by the Makefile and the site module
The rest of the work will happen in distutils2 and we will try to release a version asap for Python 2.x and 3.x (2.4 to 3.2), and the goal is to put it back in the stdlib in Python 3.3
Distutils in Python will be feature-frozen and I will only do bug fixes there. All feature requests will be redirected to Distutils2.
I think the easiest way to manage this for me and for the feedback of the community is to add in bugs.python.org a "Distutils2" component, so I can start to reorganize the issues in there and reassign new issues to Distutils2 when it applies.
Regards Tarek
-- Tarek Ziadé | http://ziade.org
-- Tarek Ziadé | http://ziade.org
-
Brett Cannon -
Tarek Ziadé