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
bpo-41132: Use pymalloc allocator in the f-string parser #21173
Conversation
|
Thanks @lysnikolaou for the PR, and @pablogsal for merging it |
|
Sorry, @lysnikolaou and @pablogsal, I could not cleanly backport this to |
|
Sorry @lysnikolaou and @pablogsal, I had trouble checking out the |
|
@lysnikolaou Manual backport party |
On it! |
…nGH-21173) (cherry picked from commit 6dcbc24)
|
GH-21183 is a backport of this pull request to the 3.9 branch. |
|
GH-21184 is a backport of this pull request to the 3.8 branch. |
|
@lysnikolaou In general is preferable to wait for the PRs to land before closing the issue, so we don't forget to land them if something goes wrong, as closing the issue removes it from the front page and the main search |
|
Oh, sorry! I thought it was ok to close the issue before landing the backport PRs, but you're right that it is a bit easier to forget things this way. Thanks for the advise! I'll do that in the future. |
) (GH-21183) (cherry picked from commit 6dcbc24) Automerge-Triggered-By: @pablogsal
No worries! Is just that this has happened to us several times so I want to transfer the knowledge acquired from past mistakes |
) (GH-21184) Automerge-Triggered-By: @pablogsal
Hah! Thanks for all the work, @lysnikolaou and @pablogsal ! |
https://bugs.python.org/issue41132