Sorry, something went wrong.
Sorry, something went wrong.
✅ Deploy Preview for python-cpython-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Sorry, something went wrong.
|
Thanks! Unfortunately, nearly all Python PRs are made against the main branch, and then backported to maintenance branches after they've been merged. The best thing to do is to recreate the PR based against main. |
Sorry, something went wrong.
|
This is against main. I'm sure I missed something, but I couldn't find the button to make a new branch from the docs. I hit edit on the file, and it auto-forked it and gave me the option to merge it back in. If you can point me in the right direction @AlexWaygood I'm happy to do the extra steps. Unless those steps are to sync & build the whole repo on my local, which is what the cpython docs were telling me to do. Really, the most confusing thing is talking about backporting. Which I don't understand how that's applicable to this at all. |
Sorry, something went wrong.
|
This is against main. I'm sure I missed something, but I couldn't find the button to make a new branch from the docs. I hit edit on the file, and it auto-forked it and gave me the option to merge it back in. If you can point me in the right direction @AlexWaygood I'm happy to do the extra steps. Unless those steps are to sync & build the whole repo on my local, which is what the cpython docs were telling me to do. Really, the most confusing thing is talking about backporting. Which I don't understand how that's applicable to this at all. Apologies! Your PR title confused me. We usually use the [3.11] tag for PRs that are against the 3.11 branch. The "backport" PR will be done automatically by a robot after this PR is merged. You won't need to worry about it. |
Sorry, something went wrong.
|
We will need you to sign the CLA, however :) |
Sorry, something went wrong.
|
Oh, oh oh. That makes sense. I had been seeing the other PRs and most seemed to have the version in the name. It wasn't mentioned in the comment, but I thought I was being a keener. I'll keep this in mind next time! |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good! As soon as you sign the CLA we can merge this in.
Sorry, something went wrong.
|
Thanks @Beweeted for the PR, and @ethanfurman for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Sorry, something went wrong.
|
GH-100181 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
Changed from multiples of 3 to powers of 3 to match the class name.