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 eric.araujo
Recipients alexis, eric.araujo, tarek, vinay.sajip
Date 2011-06-27.14:06:12
SpamBayes Score 2.7191345e-05
Marked as misclassified No
Message-id <1309183573.58.0.946383918343.issue12416@psf.upfronthosting.co.za>
In-reply-to
Content
I have no objection, but you may want to ask on the fellowship ML first.

Should the hooks be run before the removal or just after?  (Debian for example has both, which makes four hooks: preinst, postinst, prerm, postrm).  Our setup_hooks (used with pysetup commands) are run right after the setup.cfg file is parsed, before any operation is started.

Regarding implementation: The hook should be defined in the global section of setup.cfg; upon installation, packaging would write this info into the dist-info directory (say in an UNINSTALLHOOKS file), which would be read when preparing an uninstallation.
History
Date User Action Args
2011-06-27 14:06:13eric.araujosetrecipients: + eric.araujo, vinay.sajip, tarek, alexis
2011-06-27 14:06:13eric.araujosetmessageid: <1309183573.58.0.946383918343.issue12416@psf.upfronthosting.co.za>
2011-06-27 14:06:13eric.araujolinkissue12416 messages
2011-06-27 14:06:12eric.araujocreate