Skip to content

Move the comment to the right place where it used to be #119085

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 5 commits into from
Aug 7, 2025

Conversation

abhinav-upadhyay
Copy link
Contributor

In GH-116206, the comment about moving reachable objects to next generation got moved from its original place to a place where there is no code below it.

This PR puts it back where the actual movement of reachable objects happen to the next generation.

(I don't think this is a cosmetic change. The purpose of the comment is to document the code underneath it. Either the code and comments have to be in sync, or the comments need to be fixed to reflect the current reality. In this case, the comment is not quite at the right place, misleading for anyone new reading it or changing that code.)

In pythonGH-116206, the comment about moving reachable objects to next generation got moved from its original place to a place where there is no code below it. This PR puts it back where the actual movement of rechable objects happen to the next generation.
Copy link
Member

@Eclips4 Eclips4 left a comment

Choose a reason for hiding this comment

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

Thanks!

@abhinav-upadhyay
Copy link
Contributor Author

Can this be merged, or it requires something more?

@abhinav-upadhyay
Copy link
Contributor Author

@markshannon Maybe you need to review this?

@picnixz picnixz requested a review from markshannon August 28, 2024 08:43
@sergey-miryanov
Copy link
Contributor

@nascheme Please take a look. Maybe we have a change to merge this after yours #136189

@Eclips4 Eclips4 requested a review from nascheme August 7, 2025 18:18
@nascheme nascheme enabled auto-merge (squash) August 7, 2025 20:09
@nascheme
Copy link
Member

nascheme commented Aug 7, 2025

LGTM. I've enabled auto-merge after resolving the merge conflict.

@nascheme nascheme merged commit e3ad900 into python:main Aug 7, 2025
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants