➜

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 serhiy.storchaka
Recipients brett.cannon, eric.snow, indygreg, ncoghlan, petr.viktorin, serhiy.storchaka
Date 2021-09-27.09:59:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632736742.84.0.391844721289.issue41994@roundup.psfhosted.org>
In-reply-to
Content 
_PyImport_FindExtensionObject is a private API. It was added in 3.3 because import.c and importdl.c needed to share code. Since 3.5 it was only used in import.c, so there is no longer need to expose it. It was removed in 3.10 because there was an issue with this API: it returned a borroved reference which could be invalid at the time of returning.

I can restore and fix _PyImport_FindExtensionObject in 3.10, but is not it too later to do after 3.10.0rc2?

If it is essential to you, propose to add a new public API (perhaps better designed).
History
Date User Action Args
2021-09-27 09:59:02serhiy.storchakasetrecipients: + serhiy.storchaka, brett.cannon, ncoghlan, petr.viktorin, eric.snow, indygreg
2021-09-27 09:59:02serhiy.storchakasetmessageid: <1632736742.84.0.391844721289.issue41994@roundup.psfhosted.org>
2021-09-27 09:59:02serhiy.storchakalinkissue41994 messages
2021-09-27 09:59:02serhiy.storchakacreate