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 petr.viktorin
Recipients paul.moore, petr.viktorin, steve.dower, tim.golden, zach.ware
Date 2021-04-16.14:48:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618584508.44.0.195246221039.issue43868@roundup.psfhosted.org>
In-reply-to
Content
The inclusion of PyOS_ReadlineFunctionPointer in python3dll.c (*) was a mistake. According to PEP 384:

> functions expecting FILE* are not part of the ABI, to avoid depending on a specific version of the Microsoft C runtime DLL on Windows.

The situation may have changed and it might be reasonable to revisit this decision, but that would call for a larger discussion. There are FILE*-taking functions that are probably much ore useful than this one. (But, I think it's a good idea to limit the stable ABI to file-like Python objects anyway.)

I see PEP 384 as being definitive (where it's not ambiguous). The python3dll.c list and public/private headers do not actually define the stable ABI.

So, I'd like to remove the function from the list.


---

(*) it was actually PC/python3.def in 3.2
History
Date User Action Args
2021-04-16 14:48:28petr.viktorinsetrecipients: + petr.viktorin, paul.moore, tim.golden, zach.ware, steve.dower
2021-04-16 14:48:28petr.viktorinsetmessageid: <1618584508.44.0.195246221039.issue43868@roundup.psfhosted.org>
2021-04-16 14:48:28petr.viktorinlinkissue43868 messages
2021-04-16 14:48:28petr.viktorincreate