Skip to content

Conversation

@encukou
Copy link
Member

@encukouencukou commented Jan 31, 2025

@picnixz
Copy link
Member

@encukou Actually, I don't know how a backport to 3.9 from a 3.10 branch would be done, so I'll remove the label, but don't forget to backport it to 3.9 since it's blocking 3.9 PRs.

@YVK49
Copy link

hi i would like to work on this issue. could you please assign it to me ? looking forward to contributing!

@picnixz
Copy link
Member

We don't assign issues to people and this is a pull request, not an issue. If you want you can make the PR for the 3.9 branch (be careful not to open a PR against main, and be careful to checkout from the 3.9 branch).

For an easier contribution, I would advise looking through issues with the easy label and pick one (usually documentation issues are good first contributions).

@encukou
Copy link
MemberAuthor

I believe Miss Islington can do the backport just as well as a main one.

@picnixz
Copy link
Member

(Hopefully, we won't have [3.9] [3.10] as the title)

@hugovkhugovk merged commit d09105c into python:3.10Feb 18, 2025
13 checks passed
@miss-islington-app
Copy link

Thanks @encukou for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Feb 18, 2025
…onfig file (pythonGH-129510) (cherry picked from commit d09105c) Co-authored-by: Petr Viktorin <encukou@gmail.com>
@bedevere-app
Copy link

GH-130249 is a backport of this pull request to the 3.9 branch.

hugovk pushed a commit that referenced this pull request Feb 18, 2025
…ile (GH-129510) (#130249) Co-authored-by: Petr Viktorin <encukou@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@encukou@picnixz@YVK49@asvetlov@hugovk