[issue27213] Rework CALL_FUNCTION* opcodes
STINNER Victor
report at bugs.python.org
Mon Sep 12 12:14:13 EDT 2016
STINNER Victor added the comment:
> Why don't we change the magic number before b1 (if your bytecode change is already committed)?
The magic number changed many times between Python 3.5 and the future Python 3.6 beta 1. Maybe we skipped increasing this number for one bytecode change, but it should only impact the few developers who worked on the development version. In this case: just remove all ".pyc" files and it should be fine ;-)
In short: I think it's fine, don't do anything else ;-)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue27213>
_______________________________________
More information about the Python-bugs-list
mailing list