[issue33104] Documentation for EXTENDED_ARG in dis module is incorrect for >=3.6

[Eric Appelt]

Eric Appelt  added the comment:

Yes, thanks. I failed to see the duplicate searching for open issues, closing.

--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33104] Documentation for EXTENDED_ARG in dis module is incorrect for >=3.6

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Isn't this a duplicate of issue32625?

--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue33104] Documentation for EXTENDED_ARG in dis module is incorrect for >=3.6

[Eric Appelt]

New submission from Eric Appelt :

The documentation for the EXTENDED_ARG instruction in the dis module 
documentation refers to the way the opcode worked before 3.6: 
https://docs.python.org/3.6/library/dis.html#opcode-EXTENDED_ARG

As I understand, since moving to 2-byte wordcode in 3.6, each EXTENDED_ARG 
effectively adds a byte to the argument of the next instruction and they can be 
chained to allow up to a 32-bit argument. The current documentation refers the 
2-byte arguments from the older bytecode used in 3.5 and below.

I'm trying to think of a clear and concise wording for how it works now and 
will add a PR to fix this issue unless someone gets to it before me.

--
assignee: docs@python
components: Documentation
messages: 314100
nosy: Eric Appelt, docs@python
priority: normal
severity: normal
status: open
title: Documentation for EXTENDED_ARG in dis module is incorrect for >=3.6
versions: Python 3.6, Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com