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 eric.snow
Recipients brett.cannon, christoph.wiedemann, eric.snow, ncoghlan
Date 2018-08-01.19:32:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1533151977.48.0.56676864532.issue34309@psf.upfronthosting.co.za>
In-reply-to
Content
The matter of unloading extension modules is partly covered in bpo-401713.  However, note that a few things have changed in the last 18 years. :)  I think it would be worth revisiting the decision in that issue at this point.

If that were sorted out would there be other issues to address?

Regardless, If I understood right, your only objective here is to completely reset Python in the current process to the initial state.  You mention "embedded python interpreter", but it sounds more like you mean "embedded python runtime" (particularly since you are using Py_Initialize and Py_Finalize).  Why is completely resetting Python "a strong requirement"?
History
Date User Action Args
2018-08-01 19:32:57eric.snowsetrecipients: + eric.snow, brett.cannon, ncoghlan, christoph.wiedemann
2018-08-01 19:32:57eric.snowsetmessageid: <1533151977.48.0.56676864532.issue34309@psf.upfronthosting.co.za>
2018-08-01 19:32:57eric.snowlinkissue34309 messages
2018-08-01 19:32:57eric.snowcreate