[Distutils] Changing the "install hooks" mechanism for PEP 426

[Nick Coghlan]

Concrete extension use cases I have in mind that don't fit in the
exports/entry-point data model:

- the mapping of prebuilt executable names to wheel contents
- platform specific external dependencies and other hints for conversion to
platform specific formats (e.g. Windows GUIDs)
- metadata for build purposes (e.g. the working directory to use when
building from a VCS checkout, so you can have multiple projects in the same
repo)
- project specific metadata (e.g. who actually did the release)
- security metadata (e.g. security contact address and email GPG
fingerprint)

This is why extensions/exports were originally separate, and may still
remain that way.

Cheers,
Nick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20130816/de2e1a2b/attachment.html>