Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Add section about the design of CPython's garbage collector #562
Conversation
a3b94ff
to
42d4a50
|
Preview available here: https://deploy-preview-562--cpython-devguide.netlify.com/garbage_collector.html |
d8105aa
to
e59e382
Co-Authored-By: Tim Peters <tim.peters@gmail.com>
Co-Authored-By: Tim Peters <tim.peters@gmail.com>
|
@tim-one I hope you like this addition to the dev guide :) |
Co-Authored-By: Tim Peters <tim.peters@gmail.com>
Co-Authored-By: Tim Peters <tim.peters@gmail.com>
|
This is getting very big already so am going to go ahead and land it and future improvements/fixes can be made as separate PRs. Thanks a lot to everyone involved for your useful comments, reviews and suggestions |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
The design of CPython's garbage collector is normally not very well documented anywhere in detail or the documentation is dispersed across multiple places and it on top of that it has plenty of arcane implementation details that difficulties its understanding by just reading the code.
This section is an expanded version of my talk at PyconUS: https://www.youtube.com/watch?v=CLW5Lyc1FN8&t=1428s