| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The C API WG doesn't seem to be too excited about deprecating these, so I'll mark this as ready for now. |
Sorry, something went wrong.
There was a problem hiding this comment.
@ambv: Hi! I don't know well DTrace. Do we have to expose PyDTrace_xxx() functions in the public C API? Or DTrace users are not supposed to use them directly, but they should use static markers instead. In that case, these functions can be moved to the internal C API.
Sorry, something went wrong.
|
Anything left here? |
Sorry, something went wrong.
|
I'm going to merge this without review, as the change is relatively trivial (most of the diff is just mapping macros in the table). If someone has any strong objections, please send a revert and tag me. |
Sorry, something went wrong.
|
Thanks @ZeroIntensity for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
|
Thanks @ZeroIntensity for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
(cherry picked from commit 1dfe99a) Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
(cherry picked from commit 1dfe99a) Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
|
GH-145958 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
GH-145959 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
These seem like a potential candidate for deprecation.
📚 Documentation preview 📚: https://cpython-previews--141856.org.readthedocs.build/en/141856/howto/instrumentation.html#c-entry-points