On Thu, Jan 29, 2009 at 10:51 PM, Ben Finney <ben+pyt...@benfinney.id.au> wrote: > Josselin Mouette <j...@debian.org> writes: > >> Le mercredi 28 janvier 2009 à 13:16 -0600, Ian Bicking a écrit : >> > As you mention, there would have to be some extension to >> > pkg_resources (or an equivalent library) to handle finding these >> > files at runtime. Getting a runtime in place is probably the >> > harder thing, as it is more intrusive for the upstream developers. >> >> As I have already explained in the previous discussion, this could >> easily be solved just like autoconf does, with an automatically >> generated config.py file that would hold all variables set at build >> time. > > I would recommend choosing (earlier rather than later) a different > name for that file. 'config.py' suggests rather the run-time > configuration for the program. > > Perhaps 'setup_config.py'? Something that makes it clear that the > configuration is intended for the setup and installation, *not* the > running Python package.
what about "metadata.py" (that can be used by setup.py as well) ++ Tarek _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
