Skip to content

Conversation

@markshannon
Copy link
Member

@markshannonmarkshannon commented Apr 11, 2025

@markshannonmarkshannon merged commit 132bdf6 into python:3.13Apr 29, 2025
40 checks passed
@Yhg1s
Copy link
Member

Yhg1s commented Jun 5, 2025

Looks like this changes behaviour in a couple of subtle ways (see #135171) and it's not suitable for backport. I'm not sure if the changed behaviour is suitable for 3.14, but I'll leave that to @hugovk to investigate ;p

@Roman513
Copy link

Roman513 commented Jun 5, 2025

Maybe it worth to check later if alternative closed PR from @efimov-mikhail has better handling of this for such cases: #126408 - at least for 3.14.

Yhg1s added a commit to Yhg1s/cpython that referenced this pull request Jun 11, 2025
814ac0d (pythonGH-134788) and 132bdf6 (pythonGH-132384), which changed bytecode (not allowed in patch releases) and semantics (also problematic in patch releases). This reopens pythonGH-127682 as an issue.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@markshannon@Yhg1s@Roman513@iritkatriel