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 chris.jerdonek
Recipients alexis, chris.jerdonek, eric.araujo, loewis, tarek
Date 2012-07-07.02:54:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341629663.84.0.45410534752.issue15266@psf.upfronthosting.co.za>
In-reply-to
Content
With regard to the maintenance issue, what about the idea of aiming for PyPI to include that logic in a separately packaged module?  Then there would be no need to cut and paste -- just include the right version.

If that were done, depending on how the pysetup change is done, users might be able to use PyPI's latest version even if pysetup was out of synch and hadn't been updated yet.
History
Date User Action Args
2012-07-07 02:54:23chris.jerdoneksetrecipients: + chris.jerdonek, loewis, tarek, eric.araujo, alexis
2012-07-07 02:54:23chris.jerdoneksetmessageid: <1341629663.84.0.45410534752.issue15266@psf.upfronthosting.co.za>
2012-07-07 02:54:23chris.jerdoneklinkissue15266 messages
2012-07-07 02:54:23chris.jerdonekcreate