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, jkloth, josip, l0nwlf, meatballhat, pitrou, schmir, tarek, titus, zubin71
Date 2010-07-20.18:13:29
SpamBayes Score 0.139065
Marked as misclassified No
Message-id <>
configure is not config. As I understand it, the config command aimed to be something like ./configure in autotools, thus usable in combination with build and install. configure is different: it is meant to be run once to create a configure.cache file which saves possibly long and complicated options. IOW, its goal was to be typed only once, not in combination with build or install. This is why build does not call configure. I have written a short doc to explain that, see configure.rst in my repo or the built version at

This message and the linked doc explain the current behavior of configure as I understood its purpose a month ago, IMO respecting what Tarek wrote in the bug report. However, Tarek he did not explain all that he had in mind here, like I wrote here on 2010-07-17 (I don’t have notes on that :/ so I’ll have to ask him again and sort out the setup.cfg/configure.cache overlap). When I get back to configure, the command line “configure --prefix ~ install” will work according to your expectations.
Date User Action Args
2010-07-20 18:13:31eric.araujosetrecipients: + eric.araujo, titus, pitrou, schmir, tarek, jkloth, meatballhat, zubin71, l0nwlf, josip
2010-07-20 18:13:31eric.araujosetmessageid: <>
2010-07-20 18:13:29eric.araujolinkissue8254 messages
2010-07-20 18:13:29eric.araujocreate