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, higery
Date 2011-06-07.15:48:52
SpamBayes Score 6.26012e-06
Marked as misclassified No
Message-id <>
In the current packaging module, the PEP 376 .dist-info directory is generated at install time.  It should be split into two phases, build_distinfo and install_distinfo, to support at least two use cases:

- the develop command, which needs access to .dist-info
- the resources API (packaging.database.get_file), which is intended to work from an uninstalled codebase too.

The normal directory to put the generated files would be the build directory; however, setuptools’ egg_info command generates the file in the same directory as the file.  I’d prefer we avoid it in packaging, for consistency with other build_* commands, and to avoid that every project has to put “*.dist-info” in their VCS ignore file, but I don’t know if there is a technical reason that constrains setuptools to do so.
Date User Action Args
2011-06-07 15:48:53eric.araujosetrecipients: + eric.araujo, alexis, higery
2011-06-07 15:48:53eric.araujosetmessageid: <>
2011-06-07 15:48:52eric.araujolinkissue12279 messages
2011-06-07 15:48:52eric.araujocreate