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.

classification
Title: setup.cfg in [sb]dists should be static
Type: enhancement Stage: resolved
Components: Distutils2 Versions: Python 3.3, 3rd party
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: tarek Nosy List: alexis, eric.araujo, ncoghlan, tarek
Priority: normal Keywords:

Created on 2011-10-06 15:42 by eric.araujo, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (1)
msg145021 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2011-10-06 15:42
Some people (hi Ronny :) want to use a setup hook to get the version from the VCS, but the setup.cfg file in sdists and bdists should be fully static, because getting the VCS info is not possible and maybe for other reasons too (not requiring development dependencies for example, the same argument that makes people include generated HTML docs in sdists).

The way to handle that seems simple: sdist runs setup hooks and writes back the modified config object to the setup.cfg file that’s included in sdists and bdists.  Command hooks are unaffected, as are post/pre install/remove hooks (to be added in #12416).

Another idea would be to split global hooks into two kinds.  The code would run the volatile hooks, write the modified config as setup.cfg for *dists, and then run regular hooks.  Users installing a *dist will execute the regular hooks.
History
Date User Action Args
2022-04-11 14:57:22adminsetgithub: 57325
2014-03-13 00:41:48eric.araujosetstatus: open -> closed
nosy: + ncoghlan

resolution: out of date
stage: needs patch -> resolved
2012-05-06 21:25:53ezio.melottisettype: enhancement
stage: needs patch
2011-10-06 15:42:41eric.araujocreate