"P.J. Eby" writes:
> http://docs.python.org/distutils/apiref.html#module-distutils.core -
> specifically the run_setup() function. (It appears the docs do not
> have link anchors for individual functions, alas.)
http://docs.python.org/distutils/apiref.html#distutils.core.run_setup>
Sphinx (th
At 08:14 AM 9/12/2009 +1000, Ben Finney wrote:
Specifically, I want to programmatically access the metadata that is
held in the arguments to the âdistutils.setup()â call. Without,
as you say, executing any Distutils command. I am not aware of any
âdistutilsâ public functions that can do
"P.J. Eby" writes:
> If you're talking about setup.py, all you need to do is use the
> distutils functions that allow you to run a setup.py without executing
> any of its commands.
Specifically, I want to programmatically access the metadata that is
held in the arguments to the ‘distutils.setup(
At 11:25 PM 9/9/2009 +1000, Ben Finney wrote:
That's one of the pain points of the current distutils capability:
there's no standard-library way to extract that information.
If you're talking about setup.cfg (and all the other distutils .cfg
files), all you need to do is create a Distribution
Chris Withers writes:
> Do people generally source control their package's setup.cfg?
Yes. I prefer the distribution metadata to be declarative, for the
reasons you touch on later in your message. So where it makes sense I
store it in ‘setup.cfg’ or some other declarative file, and put it under
Hi All,
Do people generally source control their package's setup.cfg?
http://docs.python.org/distutils/configfile.html sort of implies it
should be editable by the person installing the package, but I've never
personally used a package where that's the case...
Assuming the distutils docs are
