bpo-28810: Document remaining bytecode changes in 3.6#651
Conversation
|
@ilevkivskyi, thanks for your PR! By analyzing the history of the files in this pull request, we identified @birkenfeld, @ncoghlan, @benjaminp, @serhiy-storchaka and @1st1 to be potential reviewers. |
Sorry, something went wrong.
|
@serhiy-storchaka Thanks!
I was also thinking about this. I implemented both your comments in a new commit. |
Sorry, something went wrong.
|
By the way, I have noticed that the example in Objects/lnotab_notes.txt is outdated. It still uses Python 2 and old bytecode (not 2 bytes per instruction). Should I update it in this PR or open a separate issue and make a separate PR? |
Sorry, something went wrong.
OK, will do this. |
Sorry, something went wrong.
serhiy-storchaka
left a comment
There was a problem hiding this comment.
The meaning of HAVE_ARGUMENT was changed too. Now all instructions have an argument, but opcodes < HAVE_ARGUMENT ignore it.
Sorry, something went wrong.
…python into more-bytecode-docs
serhiy-storchaka
left a comment
There was a problem hiding this comment.
I don't know whether the changes use good English, but in general LGTM.
Sorry, something went wrong.
|
@brettcannon Thanks! I fixed both points in a new commit. |
Sorry, something went wrong.
(cherry picked from commit 8f9e1bb)
@serhiy-storchaka @brettcannon
These are two remaining changes to close http://bugs.python.org/issue28810
This needs a backport to 3.6