-
-
Notifications
You must be signed in to change notification settings - Fork 33.3k
gh-141070: Add PyObject_Dump() function #141072
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
* Promote _PyObject_Dump() as a public function. * Keep _PyObject_Dump() alias to PyObject_Dump() for backward compatibility. * Replace _PyObject_Dump() with PyObject_Dump().
|
The tests seem to be failing on Windows. |
Ah yes, |
ZeroIntensity
left a comment
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.
LGTM with a few English nitpicks on the docs.
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
|
I think this is a great candidate for unstable API. |
Co-authored-by: Kumar Aditya <kumaraditya@python.org>
Co-authored-by: Petr Viktorin <encukou@gmail.com>
|
I created a C API Working Group decision issue. |
📚 Documentation preview 📚: https://cpython-previews--141072.org.readthedocs.build/