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 illera88
Recipients illera88, vstinner
Date 2018-07-06.21:03:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1530911021.71.0.56676864532.issue34057@psf.upfronthosting.co.za>
In-reply-to
Content
Hey Victor,

I've spent another number of hours debugging the problem and trying to avoid encodings to be loaded but I've had no luck since initfsencoding is necesary for init_sys_streams to work and that's an important function that sets stdin, stout and sterr. 

It seems that encodings is the only thing that prevents Py_Initialize to be called and therefore for a static python version to be used.

Is there any way to move encodings to pythoncore? Is there any other solution? I'm happy to put my time on this (I've already spent 3 full days debugging the problem).

I think this could be considered a bug since there is no point on statically build python and use it as a library as the README stands if there is still requirements on encodings which need to reside on the filesystem. 

Thank you again for your time
History
Date User Action Args
2018-07-06 21:03:41illera88setrecipients: + illera88, vstinner
2018-07-06 21:03:41illera88setmessageid: <1530911021.71.0.56676864532.issue34057@psf.upfronthosting.co.za>
2018-07-06 21:03:41illera88linkissue34057 messages
2018-07-06 21:03:41illera88create