A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2018-April/152630.html below:

[Python-Dev] Are undocumented functions part of the stable ABI?

[Python-Dev] Are undocumented functions part of the stable ABI? [Python-Dev] Are undocumented functions part of the stable ABI?Jeroen Demeyer J.Demeyer at UGent.be
Thu Apr 5 01:34:55 EDT 2018
On 2018-04-04 17:56, Guido van Rossum wrote:
> It would be helpful if you explained the context of your request.

The context is PEP 575. I guess my question is mostly about 
PyCFunction_Check(). I will not be able to keep it 100% backwards 
compatible simply because the goal of that PEP is precisely changing the 
classes of some objects.

Now the question is: am I allowed to change the implementation of 
PyCFunction_Check()? If it's considered part of the stable ABI, then the 
answer is immediately "no".

By the way, does anybody happen to know why the PyCFunction_* functions 
are undocumented? Is it just an oversight in the docs or is it intentional?

But regardless of the context, I think that the question "Are 
undocumented functions part of the stable ABI?" should be answered in 
PEP 384.


Jeroen.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4