Skip to content

Start a chapter on 3.11 interpreter internals #1028

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

Merged
merged 12 commits into from
Jan 16, 2023

Conversation

gvanrossum
Copy link
Member

@gvanrossum gvanrossum commented Jan 14, 2023

I haven't been able to finish this (see TODOs at the end), but I figure that maybe someone else might be interested, or at some point in the future I'd get another bit of inspiration. In the meantime, I'd rather not have my effort so far go to a complete waste.

Note that the 3.12 details are often quite different and deserve a separate chapter, but as 3.12 is still very much in flux I'd rather wait with that.

Who else should I ask for a review? Maybe @brandtbucher ?

Copy link
Member

@CAM-Gerlach CAM-Gerlach left a comment

Choose a reason for hiding this comment

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

Standard reminder: You can apply the suggestions you want in one go with Files changed -> Add to batch -> Commit.

Overall, this was of course very well written, and despite being a relative n00b, there were only a few parts were I was unsure about. My comments, nearly all as suggestions, mostly pertain to:

  • Adding/improving the Sphinx syntax, adding links/cross-references/formatting to the appropriate Python files, functions, classes and C APIs,
  • Clarifying/rephrasing a few bits that I found unclear, ambiguous or difficult to read
  • Fixing a handful of typos and minor grammar/punctuation issues

I must note that the particular choice of line-break style (OSPL) made this a relative joy to review and make suggestions on compared to arbitrary fixed-width hard breaks :)

gvanrossum and others added 6 commits January 16, 2023 09:00
(And one by HvK)

Co-authored-by: C.A.M. Gerlach <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
Neither link works:
- deepfreeze.py was moved between 3.11 and 3.12
- deepfreeze.c is not in the repo
@gvanrossum gvanrossum merged commit 863f854 into python:main Jan 16, 2023
@gvanrossum gvanrossum deleted the internals-interpreter branch January 16, 2023 17:39
@gvanrossum
Copy link
Member Author

I've just landed this, I need to move on to 3.12 again. :-) (faster-cpython/ideas#539, faster-cpython/ideas#540).

@encukou
Copy link
Member

encukou commented Jan 17, 2023

Thank you for writing this! It's great to have a resource on what the code is meant to do – which you can't always tell from the code itself, especially when debugging an issue :)

Also thanks for leaving the TODOs in to show where the gaps are.

@hugovk
Copy link
Member

hugovk commented Jan 17, 2023

The lesser-spotted "explanation" part of Diátaxis :)

@CAM-Gerlach
Copy link
Member

There actually is a todo extensionsion built into Sphinx, which has some handy features to mark todos, list them and control whether and how they are shown in the output, but I didn't want to complicate your life more for now by suggesting you use it :)

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

Successfully merging this pull request may close these issues.

4 participants