-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
PySequence_In
is not documented
#127896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
New applications shouldn't use it, we just keep it for the limited API. I'm not sure we need to encourage more usage by documenting it. |
It's exactly equivalent to The docs should mention that it's deprecated, and show the preferred spelling. |
If this function is deprecated, should we add Py_DEPRECATED to the declaration? |
No idea what the precedent is here, but I suspect that it should be soft deprecated for compatibility reasons. |
Formally, it's not deprecated yet;)
Maybe not. Search on the Github shows only few projects, which use this. On another hand, support this has 0 maintenance burden. |
Co-authored-by: Sergey B Kirpichev <[email protected]>
…GH-127979) Co-authored-by: Sergey B Kirpichev <[email protected]>
Documentation
PySequence_In
is part of the limited C-API, and has no document. PEP 3100 ( https://peps.python.org/pep-3100/ ) says this function is "To be removed," but it has not been removed in the latest version, so documentation seems to be needed.Linked PRs
PySequence_In
#127979The text was updated successfully, but these errors were encountered: