-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
gh-128813: deprecate cval field of the PyComplexObject struct #137271
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
base: main
Are you sure you want to change the base?
Conversation
7cb20b1
to
7b72948
Compare
7b72948
to
40fc415
Compare
Per PEP-387, the preferred deprecation period is 5 years (so the removal would be in 3.20). Is there a reason to accelerate that? |
Misc/NEWS.d/next/C_API/2025-07-31-11-53-38.gh-issue-128813.axQIxb.rst
Outdated
Show resolved
Hide resolved
Co-authored-by: Petr Viktorin <encukou@gmail.com>
Hmm, probably not soo much. I would bet, that M$ compiler will not have complex types in 3.17 nor in 3.20. Though, maybe we could keep legacy code with Quick search on GH give me very few project (two), that use this undocumented field: |
|
||
The complex number value, using the C :c:type:`Py_complex` representation. | ||
|
||
.. deprecated-removed:: next 3.17 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should recommend PyComplex_AsCComplex() here?
📚 Documentation preview 📚: https://cpython-previews--137271.org.readthedocs.build/