Author steve.dower
Recipients ncoghlan, richard, steve.dower, tim.golden, zach.ware
Date 2015-04-14.19:16:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429038990.96.0.956334607163.issue23955@psf.upfronthosting.co.za>
In-reply-to
Content
When Python starts running we (getpathp.c) looks in the registry for its library directory. To avoid this, you can set PYTHONPATH and PYTHONHOME environment variables, but this isn't always easy if you've copied Python into your app's directory.

We should look for a python35.ini alongside python35.dll when initializing and extract values from it. Possibly this could just be an [Environment] section with key-value pairs to set before loading.

This would ensure that app-local Python installations never look for a global install in the registry. (As an aside, for the 3.5 beta we'll be shipping an app-local "installer", which will make this situation easier to end up in, but it also has value for xcopy installs.)
History
Date User Action Args
2015-04-14 19:16:31steve.dowersetrecipients: + steve.dower, richard, ncoghlan, tim.golden, zach.ware
2015-04-14 19:16:30steve.dowersetmessageid: <1429038990.96.0.956334607163.issue23955@psf.upfronthosting.co.za>
2015-04-14 19:16:30steve.dowerlinkissue23955 messages
2015-04-14 19:16:30steve.dowercreate