Skip to content

Conversation

@ZeroIntensity
Copy link
Member

@ZeroIntensityZeroIntensity commented Nov 22, 2025

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

@bedevere-appbedevere-appbot added docs Documentation in the Doc dir skip news labels Nov 22, 2025
@ZeroIntensity
Copy link
MemberAuthor

The C API WG doesn't seem to be too excited about deprecating these, so I'll mark this as ready for now.

@ZeroIntensityZeroIntensity marked this pull request as ready for review November 28, 2025 00:15
Copy link
Member

@vstinnervstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting core reviewdocsDocumentation in the Doc dirskip news

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

2 participants

@ZeroIntensity@vstinner