New submission from Éric Araujo mer...@netwok.org:
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.
--
assignee: tarek
components: Distutils2
messages: 145021
nosy: alexis, eric.araujo, tarek
priority: normal
severity: normal
status: open
title: setup.cfg in [sb]dists should be static
versions: 3rd party, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13116
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
