Skip to content

Document tracing internals #96815

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

Open
gvanrossum opened this issue Sep 14, 2022 · 4 comments
Open

Document tracing internals #96815

gvanrossum opened this issue Sep 14, 2022 · 4 comments
Assignees
Labels
docs Documentation in the Doc dir

Comments

@gvanrossum
Copy link
Member

Let's add a new .md file to the Python directory explaining how tracing is done in the interpreter.

Brandt wrote it up here.

@gvanrossum gvanrossum added the docs Documentation in the Doc dir label Sep 14, 2022
@brandtbucher
Copy link
Member

Yep, I agree this is good to record alongside the code. I've been working on a draft that fleshes out the comment you linked to (should be done soon).

@anujrmohite
Copy link

Hey @brandtbucher ,

Just checking - still is this open, finishing the tracing docs draft?
I'm ready to invest time understanding and contributing to this
as it would help me understand CPython internals further.
Or no problem if you have it covered! Thanks!

@gvanrossum
Copy link
Member Author

I'm not Brandt, but the implementation has changed quite a bit with the implementation of PEP 669 (low-impact monitoring, usually referred to as "instrumentation" in the code). It would still be useful to document the implementation, but I believe @markshannon is the only one who could truly review such documentation.

@anujrmohite
Copy link

sure, thanks for the context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir
Projects
None yet
Development

No branches or pull requests

4 participants