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 ncoghlan
Recipients barry, dbzhang800, ncoghlan, palm.kevin, pitrou, srid, steve.dower, tarek, vstinner
Date 2015-08-29.03:49:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440820198.43.0.663323596983.issue11320@psf.upfronthosting.co.za>
In-reply-to
Content
Unfortunately, the answer to the question "Isn't there anybody motivated to fix this bug?" is "No, not really". As far as I am aware, all of the currently active core developers are primarily interested in the use of the default runtime interpreter as is, rather than embedding it in larger applications (which is the main case where PySys_SetPath is needed).

I'm *personally* interested in that area (hence my intermittent updates to PEP 432), but it's purely on my own time rather than being particularly work related.

That said, Steve Dower did do some significant work to provide an embedding friendly variant of the Windows builds for 3.5, so I've added him to the nosy list here in case he might be able to take a look.
History
Date User Action Args
2015-08-29 03:49:58ncoghlansetrecipients: + ncoghlan, barry, pitrou, vstinner, tarek, srid, palm.kevin, dbzhang800, steve.dower
2015-08-29 03:49:58ncoghlansetmessageid: <1440820198.43.0.663323596983.issue11320@psf.upfronthosting.co.za>
2015-08-29 03:49:58ncoghlanlinkissue11320 messages
2015-08-29 03:49:57ncoghlancreate