8000 [3.5] bpo-29537: Tolerate legacy invalid bytecode by ncoghlan · Pull Request #169 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

[3.5] bpo-29537: Tolerate legacy invalid bytecode #169

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
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add NEWS entry
  • Loading branch information
ncoghlan committed Mar 8, 2017
commit 22d1a65284d9a92464ba8dd159a0121fe00a70b1
6 changes: 6 additions & 0 deletions Misc/NEWS
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,12 @@ Release date: XXXX-XX-XX
Core and Builtins
-----------------

- Issue #29537: Restore runtime compatibility with bytecode files generated by
CPython 3.5.0 and 3.5.1, and adjust the eval loop to avoid the problems that
could be caused by the malformed variant of the BUILD_MAP_UNPACK_WITH_CALL
opcode that they may contain. Patch by Petr Viktorin, Serhiy Storchaka,
and Nick Coghlan.

- Issue #28598: Support __rmod__ for subclasses of str being called before
str.__mod__. Patch by Martijn Pieters.

Expand Down
0