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 steve.dower
Recipients Dieter Weber, paul.moore, pyscripter, steve.dower, tds333, tim.golden, vstinner, zach.ware
Date 2019-02-04.17:29:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1549301381.94.0.323813730576.issue35706@roundup.psfhosted.org>
In-reply-to
Content
> The idea is that python, in the embedding application, should work as in the python executable.

I disagree that this is the idea. Python in the embedding application should work as in the embedding application, not the standalone one. The embedding application should be able to easily opt-in to "standalone-like configuration", which is also what I said above, but right now that doesn't exist (it's under development).

Now, I'd be very much in favour of being able to embed Python without having to load any encodings. That ought to get us to the point where you can call "site.main()" in your embedding app, which does most of the work of what you consider the "default" behavior. But right now you just have to provide enough search path to initialize before doing that.
History
Date User Action Args
2019-02-04 17:29:43steve.dowersetrecipients: + steve.dower, paul.moore, tds333, vstinner, tim.golden, pyscripter, zach.ware, Dieter Weber
2019-02-04 17:29:41steve.dowersetmessageid: <1549301381.94.0.323813730576.issue35706@roundup.psfhosted.org>
2019-02-04 17:29:41steve.dowerlinkissue35706 messages
2019-02-04 17:29:41steve.dowercreate