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 carljm
Recipients alexis, carljm, eric.araujo, higery, michael.mulich
Date 2011-07-12.01:44:11
SpamBayes Score 1.8215259e-09
Marked as misclassified No
Message-id <1310435052.08.0.279238638799.issue12279@psf.upfronthosting.co.za>
In-reply-to
Content
You guys are more familiar with the codebase than I am, but it seems to me that the RECORD file should clearly either be not present or empty when metadata has been built but not yet installed. I don't really think the "invalid PEP 376" issue is a problem: PEP 376 describes the metadata for installed distributions; it has nothing to say about built metadata for a distribution which has not yet been installed.

For purposes of the develop command, if a pth file is used to implement develop, then ideally when develop is run a RECORD file would be added containing only the path to that pth file, as thats the only file that has actually been installed (and the only one that should be removed if the develop-installed package is uninstalled).
History
Date User Action Args
2011-07-12 01:44:12carljmsetrecipients: + carljm, eric.araujo, alexis, michael.mulich, higery
2011-07-12 01:44:12carljmsetmessageid: <1310435052.08.0.279238638799.issue12279@psf.upfronthosting.co.za>
2011-07-12 01:44:11carljmlinkissue12279 messages
2011-07-12 01:44:11carljmcreate