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 cool-RR
Recipients alexis, cool-RR, eric.araujo, tarek
Date 2011-09-05.01:24:02
SpamBayes Score 0.000751351
Marked as misclassified No
Message-id <1315185843.85.0.324851460345.issue12895@psf.upfronthosting.co.za>
In-reply-to
Content
Currently, when you use an MSI installer (and possibly also EXE) for a Python module, it automatically detects the location of your various system's Python installations. This is very convenient.

However, this can be a problem sometimes, if your Python installation doesn't conform to what's required by the installer. For example, if you want to install the module in a virtualenv:

http://serverfault.com/questions/305008/installing-compiled-python-modules-on-windows-on-a-virtual-env

The installer doesn't give you any option to manually enter a path of a Python installation, so you just can't install!

The installer's automatic Python-finding mechanism should degrade gracefully; it should offer to automatically find your Python installation, but it should allow you to bypass it and type it in yourself.
History
Date User Action Args
2011-09-05 01:24:03cool-RRsetrecipients: + cool-RR, tarek, eric.araujo, alexis
2011-09-05 01:24:03cool-RRsetmessageid: <1315185843.85.0.324851460345.issue12895@psf.upfronthosting.co.za>
2011-09-05 01:24:03cool-RRlinkissue12895 messages
2011-09-05 01:24:02cool-RRcreate