This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients akitada, bruthasj, tarek, terry.reedy
Date 2010-06-27.00:33:27
SpamBayes Score 0.0005781488
Marked as misclassified No
Message-id <4C269C4A.3020305@udel.edu>
In-reply-to <1277588164.63.0.189064733093.issue1035576@psf.upfronthosting.co.za>
Content
On 6/26/2010 5:36 PM, Tarek Ziadé wrote:
>
> Tarek Ziadé<ziade.tarek@gmail.com>  added the comment:
>
> distutils is now frozen in all branches, so not accepting new
> features but just bug fixes.
>
> although distutils2 will not provide bdist_rpm, and I'd suggest the
> command to live on its own, in a new project (like bdist_deb did in
> stdeb). The benefit is to have a different release cycle which can
> follow the rpm world.

Seems like a good idea.

> So yes, all pending feature requests to build_rpm, should be closed.

Done for the duplicate, and 4 others for bdist_rpm (you should see
messages and counter if not correct.)

There are also bug reports for bdist_rpm. Close these too?
2945 4495 5474 644744 5875 (test failure)

How about any of the other feature requests (there are about 36 others
open for distutils). Should they be retargeted to disutils2?

> ---------- resolution:  ->  wont fix status: open ->  closed type:
> ->  feature request
>
> _______________________________________ Python
> tracker<report@bugs.python.org>
> <http://bugs.python.org/issue1035576>
> _______________________________________
History
Date User Action Args
2010-06-27 00:33:30terry.reedysetrecipients: + terry.reedy, bruthasj, tarek, akitada
2010-06-27 00:33:28terry.reedylinkissue1035576 messages
2010-06-27 00:33:27terry.reedycreate