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 zach.ware
Recipients BreamoreBoy, brian.curtin, sbt, terry.reedy, tim.golden, zach.ware
Date 2013-05-28.20:35:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Brian Curtin added the comment:
> Don't we already require an existing Python to build some of the third-party stuff, e.g., OpenSSL?

Only for building a 64-bit Python on 32-bit Windows.  Otherwise,
OpenSSL is built using the just-built interpreter.

> I don't think the bootstrapping issue holds that much weight. Adding some huge batch script that maybe one or two people even know how to modify is a much higher cost than just having someone install Python.

Fair enough, but even when Python is installed, there's still the
issue of whether it will be findable on PATH, whether .py is in
PATHEXT, what version of Python is installed (and which one is on
PATH), etc. etc...

However, you've made me think; perhaps configure.bat could build a
minimal Python that can then be used for a  I'll do some
experimenting and see what I can come up with.
Date User Action Args
2013-05-28 20:35:18zach.waresetrecipients: + zach.ware, terry.reedy, tim.golden, brian.curtin, BreamoreBoy, sbt
2013-05-28 20:35:18zach.warelinkissue16895 messages
2013-05-28 20:35:17zach.warecreate