Author pablogsal
Recipients brett.cannon, eric.snow, htgoebel, ncoghlan, ned.deily, pablogsal
Date 2018-03-27.22:21:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522189319.27.0.467229070634.issue33128@psf.upfronthosting.co.za>
In-reply-to
Content
It seems that the problem is that `_Py_InitializeEx_Private` calls  `_Py_InitializeCore` and `_Py_InitializeMainInterpreter`. The first one calls at the end `initimport` that in turns calls `importlib._install_external_importers` that sets the PathFinder. Then, `_Py_InitializeMainInterpreter` calls  `initexternalimport` that in turns calls again `importlib._install_external_importers` and therefore we end with two PathFinders in sys.meta_path.

I think the solution is removing the call to initexternalimport in `_Py_InitializeMainInterpreter` as it has been alreade initialized by `_Py_InitializeCore`.
History
Date User Action Args
2018-03-27 22:21:59pablogsalsetrecipients: + pablogsal, brett.cannon, htgoebel, ncoghlan, ned.deily, eric.snow
2018-03-27 22:21:59pablogsalsetmessageid: <1522189319.27.0.467229070634.issue33128@psf.upfronthosting.co.za>
2018-03-27 22:21:59pablogsallinkissue33128 messages
2018-03-27 22:21:59pablogsalcreate