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 loewis
Recipients bethard, loewis, tarek
Date 2009-05-04.16:18:40
SpamBayes Score 7.9776186e-12
Marked as misclassified No
Message-id <1241453921.97.0.89326949564.issue5311@psf.upfronthosting.co.za>
In-reply-to
Content
The patch looks fine so far, please apply to trunk and 3k. As this is a
new feature, I think backporting it is not appropriate.

I believe that the support for (pre)install scripts is incorrect; I
would expect that each such script should be executed once per version
for which the package is installed. However, this can be fixed later;
for the moment, it would be good enough to warn at packaging time that
scripts may not work for multi-version packages.

You can also consider providing "Change" installation, allowing the user
to selectively add a package to a python version after that python
version is installed (or to remove it before the python version gets
removed). To do so, just add an option to the MaintenanceTypeDlg that
forks into the feature selection dialog, with the standard INSTALL action.
History
Date User Action Args
2009-05-04 16:18:42loewissetrecipients: + loewis, bethard, tarek
2009-05-04 16:18:41loewissetmessageid: <1241453921.97.0.89326949564.issue5311@psf.upfronthosting.co.za>
2009-05-04 16:18:40loewislinkissue5311 messages
2009-05-04 16:18:40loewiscreate