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.

Author eric.araujo
Recipients eric.araujo, l, tarek
Date 2014-03-12.09:11:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394615462.64.0.00304402883463.issue18970@psf.upfronthosting.co.za>
In-reply-to
Content
> The principle of least surprise suggests that run_setup() should behave equivalently
> to a command line invocation of setup.py.

That’s debatable: distutils.core.setup corresponds to a command-line invocation of setup.py, but run_setup is documented as something else: http://docs.python.org/3.4/distutils/apiref#distutils.core.run_setup

In general, distutils lends itself poorly to programmatic usage.  Can you tell more about your use case for calling run_setup directly?

> Many setup.py scripts use the idiomatic 'conditional script' stanza
> "if __name__ == '__main__'".

That’s surprising to me: setup.py scripts are not modules-that-also-work-as-scripts, only scripts.
History
Date User Action Args
2014-03-12 09:11:02eric.araujosetrecipients: + eric.araujo, tarek, l
2014-03-12 09:11:02eric.araujosetmessageid: <1394615462.64.0.00304402883463.issue18970@psf.upfronthosting.co.za>
2014-03-12 09:11:02eric.araujolinkissue18970 messages
2014-03-12 09:11:02eric.araujocreate