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 wesley.spikes
Recipients wesley.spikes
Date 2008-04-16.01:05:52
SpamBayes Score 0.023416957
Marked as misclassified No
Message-id <1208307954.26.0.976441320091.issue2642@psf.upfronthosting.co.za>
In-reply-to
Content
I've searched and did not find any open ticket to make suggestions on, 
so I'm posting it here.

You currently have posted "The MSI installers for Python 3.0a4 are 
compiled with the new Visual Studio 2008 Professional version. 
Therefore Python depends on the -Visual C++ runtime library 9.0. We 
currently don't package this library properly, which means that non-
Administrator installation is currently not supported. Contributions to 
fix this problem are welcome."

Two potential fixes, both of which should be very readily doable. First 
one is to set the Linking option in MSVC++ to a static link to the CRT. 
This in-builds the library with Python. (Options /MT and /MTd, for 
release and debug versions, respectively.)

The other potential resolution for Non-Admin installs, which may or may 
not be more stable, is to include the MSVCRT DLLs into the directory 
containing the Python installation. If needed, you may have to register 
these files manually into the HKCU hive.

Hope that helps with your described packaging issue with the installer.

(Classified under Build and Installation, since it deals with both 
halves -- feel free to reclassify as appropriate.)
History
Date User Action Args
2008-04-16 01:05:54wesley.spikessetspambayes_score: 0.023417 -> 0.023416957
recipients: + wesley.spikes
2008-04-16 01:05:54wesley.spikessetspambayes_score: 0.023417 -> 0.023417
messageid: <1208307954.26.0.976441320091.issue2642@psf.upfronthosting.co.za>
2008-04-16 01:05:53wesley.spikeslinkissue2642 messages
2008-04-16 01:05:52wesley.spikescreate