32.12. dis
– Désassembleur pour le code intermédiaire de Python¶
Code source : Lib/dis.py
La bibliothèque dis
supporte l’analyse du bytecode CPython en le désassemblant. Le code intermédiaire CPython, que cette bibliothèque prend en paramètre, est défini dans le fichier Include/opcode.h
et est utilisé par le compilateur et l’interpréteur.
Le code intermédiaire est un détail d’implémentation de l’interpréteur CPython. Il n’y a pas de garantie que le code intermédiaire sera ajouté, retiré, ou modifié dans les différentes versions de Python. L’utilisation de cette bibliothèque ne fonctionne pas nécessairement sur les machines virtuelles Python ni les différentes versions de Python.
Exemple : Etant donné la fonction myfunc()
:
def myfunc(alist):
return len(alist)
la commande suivante peut-être utilisé pour afficher le désassemblage de myfunc()
:
>>> dis.dis(myfunc)
2 0 LOAD_GLOBAL 0 (len)
3 LOAD_FAST 0 (alist)
6 CALL_FUNCTION 1
9 RETURN_VALUE
(Le « 2 » est un numéro de ligne).
32.12.1. Analyse du code intermédiaire¶
Nouveau dans la version 3.4.
L’analyse de l”API code intermédiaire permet de rassembler des blocs de code en Python dans une classe Bytecode
, qui permet un accès facile aux détails du code compilé.
-
class
dis.
Bytecode
(x, *, first_line=None, current_offset=None)¶ Analyse the bytecode corresponding to a function, generator, method, string of source code, or a code object (as returned by
compile()
).Ceci est wrapper sur plusieurs fonctions de la liste ci-dessous, notamment
get_instructions()
, étant donné qu’une itération sur une instance de la classeBytecode
rend les opérations du code intermédiaire des instances deInstruction
.Si first_line ne vaut pas
None
, elle indique le nombre de la ligne qui doit être considérée comme première ligne source dans le code désassemblé. Autrement, les informations sur la ligne source sont prises directement à partir de la classe du code désassemblé.Si la valeur de current_offset est différente de
None
, c’est une référence à un offset d’une instruction dans le code désassemblé. Cela veut dire quedis()
va générer un marqueur de » l’instruction en cours » contre le code d’opération donné.-
classmethod
from_traceback
(tb)¶ Construisez une instance
Bytecode
à partir de la trace d’appel, en mettant current_offet à l’instruction responsable de l’exception.
-
codeobj
¶ Le code compilé objet.
-
first_line
¶ La première ligne source du code objet (si disponible)
-
dis
()¶ Retourne une vue formatée des opérations du code intermédiaire (la même que celle envoyée par
dis.dis()
, mais comme une chaîne de caractères de plusieurs lignes ).
-
info
()¶ Retourne une chaîne de caractères de plusieurs lignes formatée avec des informations détaillées sur l’objet code comme
code_info()
.
-
classmethod
Exemple :
>>> bytecode = dis.Bytecode(myfunc)
>>> for instr in bytecode:
... print(instr.opname)
...
LOAD_GLOBAL
LOAD_FAST
CALL_FUNCTION
RETURN_VALUE
32.12.2. Analyse de fonctions¶
La bibliothèque dis
comprend également l’analyse des fonctions suivantes, qui envoient l’entrée directement à la sortie souhaitée. Elles peuvent être utiles si il n’y a qu’une seule opération à effectuer, la représentation intermédiaire objet n’étant donc pas utile dans ce cas:
-
dis.
code_info
(x)¶ Return a formatted multi-line string with detailed code object information for the supplied function, generator, method, source code string or code object.
Il est à noter que le contenu exact des chaînes de caractères figurant dans les informations du code dépendent fortement sur l’implémentation, et peuvent changer arbitrairement sous machines virtuelles Python ou les versions de Python.
Nouveau dans la version 3.2.
-
dis.
show_code
(x, *, file=None)¶ Affiche des informations détaillées sur le code de la fonction fournie, la méthode, la chaîne de caractère du code source ou du code objet à file (ou bien
sys.stdout
si file n’est pas spécifié).Ceci est un raccourci convenable de
print(code_info(x), file=file)
, principalement fait pour l’exploration interactive sur l’invite de l’interpréteur.Nouveau dans la version 3.2.
Modifié dans la version 3.4: Ajout du paramètre file.
-
dis.
dis
(x=None, *, file=None)¶ Disassemble the x object. x can denote either a module, a class, a method, a function, a generator, a code object, a string of source code or a byte sequence of raw bytecode. For a module, it disassembles all functions. For a class, it disassembles all methods (including class and static methods). For a code object or sequence of raw bytecode, it prints one line per bytecode instruction. Strings are first compiled to code objects with the
compile()
built-in function before being disassembled. If no object is provided, this function disassembles the last traceback.Le désassemblage est envoyé sous forme de texte à l’argument du fichier file si il est fourni, et à
sys.stdout
sinon.Modifié dans la version 3.4: Ajout du paramètre file.
-
dis.
distb
(tb=None, *, file=None)¶ Désassemble la fonction du haut de la pile des traces d’appels, en utilisant la dernière trace d’appels si rien n’a été envoyé. L’instruction à l’origine de l’exception est indiquée.
Le désassemblage est envoyé sous forme de texte à l’argument du fichier file si il est fourni, et à
sys.stdout
sinon.Modifié dans la version 3.4: Ajout du paramètre file.
-
dis.
disassemble
(code, lasti=-1, *, file=None)¶ -
dis.
disco
(code, lasti=-1, *, file=None)¶ Désassemble un code objet, en indiquant la dernière instruction si lasti est fournie. La sortie est répartie sur les colonnes suivantes :
- le numéro de ligne, pour la première instruction de chaque ligne
- l’instruction en cours, indiquée par
-->
, - une instruction libellée, indiquée par
> >
, - l’adresse de l’instruction,
- le nom de le code d’opération,
- paramètres de l’opération, et
- interprétation des paramètres entre parenthèses.
L’interprétation du paramètre reconnaît les noms des variables locales et globales, des valeurs constantes, des branchements cibles, et des opérateurs de comparaison.
Le désassemblage est envoyé sous forme de texte à l’argument du fichier file si il est fourni, et à
sys.stdout
sinon.Modifié dans la version 3.4: Ajout du paramètre file.
-
dis.
get_instructions
(x, *, first_line=None)¶ Retourne un itérateur sur les instructions dans la fonction fournie, la méthode, les chaînes de caractères du code source ou objet.
Cet itérateur génère une série de n-uplets de
Instruction
qui donnent les détails de chacune des opérations dans le code fourni.Si first_line ne vaut pas
None
, elle indique le nombre de la ligne qui doit être considérée comme première ligne source dans le code désassemblé. Autrement, les informations sur la ligne source sont prises directement à partir de la classe du code désassemblé.Nouveau dans la version 3.4.
-
dis.
findlinestarts
(code)¶ This generator function uses the
co_firstlineno
andco_lnotab
attributes of the code object code to find the offsets which are starts of lines in the source code. They are generated as(offset, lineno)
pairs.
-
dis.
findlabels
(code)¶ Detect all offsets in the code object code which are jump targets, and return a list of these offsets.
-
dis.
stack_effect
(opcode[, oparg])¶ Compute the stack effect of opcode with argument oparg.
Nouveau dans la version 3.4.
32.12.3. Les instructions du code intermédiaire en Python¶
La fonction get_instructions()
et la méthode Bytecode
fournit des détails sur le code intermédiaire des instructions comme Instruction
instances:
-
class
dis.
Instruction
¶ Détails sur le code intermédiaire de l’opération
-
opcode
¶ code numérique pour l’opération, correspondant aux valeurs de l”opcode ci-dessous et les valeurs du code intermédiaire dans la Opcode collections.
-
opname
¶ nom lisible/compréhensible de l’opération
-
arg
¶ le cas échéant, argument numérique de l’opération sinon
None
-
argval
¶ resolved arg value (if known), otherwise same as arg
-
argrepr
¶ human readable description of operation argument
-
offset
¶ start index of operation within bytecode sequence
-
starts_line
¶ line started by this opcode (if any), otherwise
None
-
is_jump_target
¶ True
if other code jumps to here, otherwiseFalse
Nouveau dans la version 3.4.
-
The Python compiler currently generates the following bytecode instructions.
General instructions
-
NOP
¶ Do nothing code. Used as a placeholder by the bytecode optimizer.
-
POP_TOP
¶ Removes the top-of-stack (TOS) item.
-
ROT_TWO
¶ Swaps the two top-most stack items.
-
ROT_THREE
¶ Lifts second and third stack item one position up, moves top down to position three.
-
DUP_TOP
¶ Duplicates the reference on top of the stack.
-
DUP_TOP_TWO
¶ Duplicates the two references on top of the stack, leaving them in the same order.
Unary operations
Unary operations take the top of the stack, apply the operation, and push the result back on the stack.
-
UNARY_POSITIVE
¶ Implements
TOS = +TOS
.
-
UNARY_NEGATIVE
¶ Implements
TOS = -TOS
.
-
UNARY_NOT
¶ Implements
TOS = not TOS
.
-
UNARY_INVERT
¶ Implements
TOS = ~TOS
.
-
GET_ITER
¶ Implements
TOS = iter(TOS)
.
-
GET_YIELD_FROM_ITER
¶ If
TOS
is a generator iterator or coroutine object it is left as is. Otherwise, implementsTOS = iter(TOS)
.Nouveau dans la version 3.5.
Binary operations
Binary operations remove the top of the stack (TOS) and the second top-most stack item (TOS1) from the stack. They perform the operation, and put the result back on the stack.
-
BINARY_POWER
¶ Implements
TOS = TOS1 ** TOS
.
-
BINARY_MULTIPLY
¶ Implements
TOS = TOS1 * TOS
.
-
BINARY_MATRIX_MULTIPLY
¶ Implements
TOS = TOS1 @ TOS
.Nouveau dans la version 3.5.
-
BINARY_FLOOR_DIVIDE
¶ Implements
TOS = TOS1 // TOS
.
-
BINARY_TRUE_DIVIDE
¶ Implements
TOS = TOS1 / TOS
.
-
BINARY_MODULO
¶ Implements
TOS = TOS1 % TOS
.
-
BINARY_ADD
¶ Implements
TOS = TOS1 + TOS
.
-
BINARY_SUBTRACT
¶ Implements
TOS = TOS1 - TOS
.
-
BINARY_SUBSCR
¶ Implements
TOS = TOS1[TOS]
.
-
BINARY_LSHIFT
¶ Implements
TOS = TOS1 << TOS
.
-
BINARY_RSHIFT
¶ Implements
TOS = TOS1 >> TOS
.
-
BINARY_AND
¶ Implements
TOS = TOS1 & TOS
.
-
BINARY_XOR
¶ Implements
TOS = TOS1 ^ TOS
.
-
BINARY_OR
¶ Implements
TOS = TOS1 | TOS
.
In-place operations
In-place operations are like binary operations, in that they remove TOS and TOS1, and push the result back on the stack, but the operation is done in-place when TOS1 supports it, and the resulting TOS may be (but does not have to be) the original TOS1.
-
INPLACE_POWER
¶ Implements in-place
TOS = TOS1 ** TOS
.
-
INPLACE_MULTIPLY
¶ Implements in-place
TOS = TOS1 * TOS
.
-
INPLACE_MATRIX_MULTIPLY
¶ Implements in-place
TOS = TOS1 @ TOS
.Nouveau dans la version 3.5.
-
INPLACE_FLOOR_DIVIDE
¶ Implements in-place
TOS = TOS1 // TOS
.
-
INPLACE_TRUE_DIVIDE
¶ Implements in-place
TOS = TOS1 / TOS
.
-
INPLACE_MODULO
¶ Implements in-place
TOS = TOS1 % TOS
.
-
INPLACE_ADD
¶ Implements in-place
TOS = TOS1 + TOS
.
-
INPLACE_SUBTRACT
¶ Implements in-place
TOS = TOS1 - TOS
.
-
INPLACE_LSHIFT
¶ Implements in-place
TOS = TOS1 << TOS
.
-
INPLACE_RSHIFT
¶ Implements in-place
TOS = TOS1 >> TOS
.
-
INPLACE_AND
¶ Implements in-place
TOS = TOS1 & TOS
.
-
INPLACE_XOR
¶ Implements in-place
TOS = TOS1 ^ TOS
.
-
INPLACE_OR
¶ Implements in-place
TOS = TOS1 | TOS
.
-
STORE_SUBSCR
¶ Implements
TOS1[TOS] = TOS2
.
-
DELETE_SUBSCR
¶ Implements
del TOS1[TOS]
.
Coroutine opcodes
-
GET_AWAITABLE
¶ Implements
TOS = get_awaitable(TOS)
, whereget_awaitable(o)
returnso
ifo
is a coroutine object or a generator object with the CO_ITERABLE_COROUTINE flag, or resolveso.__await__
.
-
GET_AITER
¶ Implements
TOS = get_awaitable(TOS.__aiter__())
. SeeGET_AWAITABLE
for details aboutget_awaitable
-
GET_ANEXT
¶ Implements
PUSH(get_awaitable(TOS.__anext__()))
. SeeGET_AWAITABLE
for details aboutget_awaitable
-
BEFORE_ASYNC_WITH
¶ Resolves
__aenter__
and__aexit__
from the object on top of the stack. Pushes__aexit__
and result of__aenter__()
to the stack.
-
SETUP_ASYNC_WITH
¶ Creates a new frame object.
Miscellaneous opcodes
-
PRINT_EXPR
¶ Implements the expression statement for the interactive mode. TOS is removed from the stack and printed. In non-interactive mode, an expression statement is terminated with
POP_TOP
.
-
CONTINUE_LOOP
(target)¶ Continues a loop due to a
continue
statement. target is the address to jump to (which should be aFOR_ITER
instruction).
-
SET_ADD
(i)¶ Calls
set.add(TOS1[-i], TOS)
. Used to implement set comprehensions.
-
LIST_APPEND
(i)¶ Calls
list.append(TOS[-i], TOS)
. Used to implement list comprehensions.
-
MAP_ADD
(i)¶ Calls
dict.setitem(TOS1[-i], TOS, TOS1)
. Used to implement dict comprehensions.
For all of the SET_ADD
, LIST_APPEND
and MAP_ADD
instructions, while the added value or key/value pair is popped off, the
container object remains on the stack so that it is available for further
iterations of the loop.
-
RETURN_VALUE
¶ Returns with TOS to the caller of the function.
-
YIELD_FROM
¶ Pops TOS and delegates to it as a subiterator from a generator.
Nouveau dans la version 3.3.
-
IMPORT_STAR
¶ Loads all symbols not starting with
'_'
directly from the module TOS to the local namespace. The module is popped after loading all names. This opcode implementsfrom module import *
.
-
POP_BLOCK
¶ Removes one block from the block stack. Per frame, there is a stack of blocks, denoting nested loops, try statements, and such.
-
POP_EXCEPT
¶ Removes one block from the block stack. The popped block must be an exception handler block, as implicitly created when entering an except handler. In addition to popping extraneous values from the frame stack, the last three popped values are used to restore the exception state.
-
END_FINALLY
¶ Terminates a
finally
clause. The interpreter recalls whether the exception has to be re-raised, or whether the function returns, and continues with the outer-next block.
-
LOAD_BUILD_CLASS
¶ Pushes
builtins.__build_class__()
onto the stack. It is later called byCALL_FUNCTION
to construct a class.
-
SETUP_WITH
(delta)¶ This opcode performs several operations before a with block starts. First, it loads
__exit__()
from the context manager and pushes it onto the stack for later use byWITH_CLEANUP
. Then,__enter__()
is called, and a finally block pointing to delta is pushed. Finally, the result of calling the enter method is pushed onto the stack. The next opcode will either ignore it (POP_TOP
), or store it in (a) variable(s) (STORE_FAST
,STORE_NAME
, orUNPACK_SEQUENCE
).
-
WITH_CLEANUP_START
¶ Cleans up the stack when a
with
statement block exits. TOS is the context manager’s__exit__()
bound method. Below TOS are 1–3 values indicating how/why the finally clause was entered:- SECOND =
None
- (SECOND, THIRD) = (
WHY_{RETURN,CONTINUE}
), retval - SECOND =
WHY_*
; no retval below it - (SECOND, THIRD, FOURTH) = exc_info()
In the last case,
TOS(SECOND, THIRD, FOURTH)
is called, otherwiseTOS(None, None, None)
. Pushes SECOND and result of the call to the stack.- SECOND =
-
WITH_CLEANUP_FINISH
¶ Pops exception type and result of “exit” function call from the stack.
If the stack represents an exception, and the function call returns a “true” value, this information is « zapped » and replaced with a single
WHY_SILENCED
to preventEND_FINALLY
from re-raising the exception. (But non-local gotos will still be resumed.)
All of the following opcodes expect arguments. An argument is two bytes, with the more significant byte last.
-
STORE_NAME
(namei)¶ Implements
name = TOS
. namei is the index of name in the attributeco_names
of the code object. The compiler tries to useSTORE_FAST
orSTORE_GLOBAL
if possible.
-
DELETE_NAME
(namei)¶ Implements
del name
, where namei is the index intoco_names
attribute of the code object.
-
UNPACK_SEQUENCE
(count)¶ Unpacks TOS into count individual values, which are put onto the stack right-to-left.
-
UNPACK_EX
(counts)¶ Implements assignment with a starred target: Unpacks an iterable in TOS into individual values, where the total number of values can be smaller than the number of items in the iterable: one of the new values will be a list of all leftover items.
The low byte of counts is the number of values before the list value, the high byte of counts the number of values after it. The resulting values are put onto the stack right-to-left.
-
STORE_ATTR
(namei)¶ Implements
TOS.name = TOS1
, where namei is the index of name inco_names
.
-
DELETE_ATTR
(namei)¶ Implements
del TOS.name
, using namei as index intoco_names
.
-
STORE_GLOBAL
(namei)¶ Works as
STORE_NAME
, but stores the name as a global.
-
DELETE_GLOBAL
(namei)¶ Works as
DELETE_NAME
, but deletes a global name.
-
LOAD_CONST
(consti)¶ Pushes
co_consts[consti]
onto the stack.
-
LOAD_NAME
(namei)¶ Pushes the value associated with
co_names[namei]
onto the stack.
-
BUILD_TUPLE
(count)¶ Creates a tuple consuming count items from the stack, and pushes the resulting tuple onto the stack.
-
BUILD_LIST
(count)¶ Works as
BUILD_TUPLE
, but creates a list.
-
BUILD_SET
(count)¶ Works as
BUILD_TUPLE
, but creates a set.
-
BUILD_MAP
(count)¶ Pushes a new dictionary object onto the stack. Pops
2 * count
items so that the dictionary holds count entries:{..., TOS3: TOS2, TOS1: TOS}
.Modifié dans la version 3.5: The dictionary is created from stack items instead of creating an empty dictionary pre-sized to hold count items.
-
BUILD_TUPLE_UNPACK
(count)¶ Pops count iterables from the stack, joins them in a single tuple, and pushes the result. Implements iterable unpacking in tuple displays
(*x, *y, *z)
.Nouveau dans la version 3.5.
-
BUILD_LIST_UNPACK
(count)¶ This is similar to
BUILD_TUPLE_UNPACK
, but pushes a list instead of tuple. Implements iterable unpacking in list displays[*x, *y, *z]
.Nouveau dans la version 3.5.
-
BUILD_SET_UNPACK
(count)¶ This is similar to
BUILD_TUPLE_UNPACK
, but pushes a set instead of tuple. Implements iterable unpacking in set displays{*x, *y, *z}
.Nouveau dans la version 3.5.
-
BUILD_MAP_UNPACK
(count)¶ Pops count mappings from the stack, merges them into a single dictionary, and pushes the result. Implements dictionary unpacking in dictionary displays
{**x, **y, **z}
.Nouveau dans la version 3.5.
-
BUILD_MAP_UNPACK_WITH_CALL
(oparg)¶ This is similar to
BUILD_MAP_UNPACK
, but is used forf(**x, **y, **z)
call syntax. The lowest byte of oparg is the count of mappings, the relative position of the corresponding callablef
is encoded in the second byte of oparg.Nouveau dans la version 3.5.
-
LOAD_ATTR
(namei)¶ Replaces TOS with
getattr(TOS, co_names[namei])
.
-
COMPARE_OP
(opname)¶ Performs a Boolean operation. The operation name can be found in
cmp_op[opname]
.
-
IMPORT_NAME
(namei)¶ Imports the module
co_names[namei]
. TOS and TOS1 are popped and provide the fromlist and level arguments of__import__()
. The module object is pushed onto the stack. The current namespace is not affected: for a proper import statement, a subsequentSTORE_FAST
instruction modifies the namespace.
-
IMPORT_FROM
(namei)¶ Loads the attribute
co_names[namei]
from the module found in TOS. The resulting object is pushed onto the stack, to be subsequently stored by aSTORE_FAST
instruction.
-
JUMP_FORWARD
(delta)¶ Increments bytecode counter by delta.
-
POP_JUMP_IF_TRUE
(target)¶ If TOS is true, sets the bytecode counter to target. TOS is popped.
-
POP_JUMP_IF_FALSE
(target)¶ If TOS is false, sets the bytecode counter to target. TOS is popped.
-
JUMP_IF_TRUE_OR_POP
(target)¶ If TOS is true, sets the bytecode counter to target and leaves TOS on the stack. Otherwise (TOS is false), TOS is popped.
-
JUMP_IF_FALSE_OR_POP
(target)¶ If TOS is false, sets the bytecode counter to target and leaves TOS on the stack. Otherwise (TOS is true), TOS is popped.
-
JUMP_ABSOLUTE
(target)¶ Set bytecode counter to target.
-
FOR_ITER
(delta)¶ TOS is an iterator. Call its
__next__()
method. If this yields a new value, push it on the stack (leaving the iterator below it). If the iterator indicates it is exhausted TOS is popped, and the byte code counter is incremented by delta.
-
LOAD_GLOBAL
(namei)¶ Loads the global named
co_names[namei]
onto the stack.
-
SETUP_LOOP
(delta)¶ Pushes a block for a loop onto the block stack. The block spans from the current instruction with a size of delta bytes.
-
SETUP_EXCEPT
(delta)¶ Pushes a try block from a try-except clause onto the block stack. delta points to the first except block.
-
SETUP_FINALLY
(delta)¶ Pushes a try block from a try-except clause onto the block stack. delta points to the finally block.
-
LOAD_FAST
(var_num)¶ Pushes a reference to the local
co_varnames[var_num]
onto the stack.
-
STORE_FAST
(var_num)¶ Stores TOS into the local
co_varnames[var_num]
.
-
DELETE_FAST
(var_num)¶ Deletes local
co_varnames[var_num]
.
-
LOAD_CLOSURE
(i)¶ Pushes a reference to the cell contained in slot i of the cell and free variable storage. The name of the variable is
co_cellvars[i]
if i is less than the length of co_cellvars. Otherwise it isco_freevars[i - len(co_cellvars)]
.
-
LOAD_DEREF
(i)¶ Loads the cell contained in slot i of the cell and free variable storage. Pushes a reference to the object the cell contains on the stack.
-
LOAD_CLASSDEREF
(i)¶ Much like
LOAD_DEREF
but first checks the locals dictionary before consulting the cell. This is used for loading free variables in class bodies.
-
STORE_DEREF
(i)¶ Stores TOS into the cell contained in slot i of the cell and free variable storage.
-
DELETE_DEREF
(i)¶ Empties the cell contained in slot i of the cell and free variable storage. Used by the
del
statement.
-
RAISE_VARARGS
(argc)¶ Raises an exception. argc indicates the number of arguments to the raise statement, ranging from 0 to 3. The handler will find the traceback as TOS2, the parameter as TOS1, and the exception as TOS.
-
CALL_FUNCTION
(argc)¶ Calls a callable object. The low byte of argc indicates the number of positional arguments, the high byte the number of keyword arguments. The stack contains keyword arguments on top (if any), then the positional arguments below that (if any), then the callable object to call below that. Each keyword argument is represented with two values on the stack: the argument’s name, and its value, with the argument’s value above the name on the stack. The positional arguments are pushed in the order that they are passed in to the callable object, with the right-most positional argument on top.
CALL_FUNCTION
pops all arguments and the callable object off the stack, calls the callable object with those arguments, and pushes the return value returned by the callable object.
-
MAKE_FUNCTION
(argc)¶ Pushes a new function object on the stack. From bottom to top, the consumed stack must consist of
argc & 0xFF
default argument objects in positional order, for positional parameters(argc >> 8) & 0xFF
pairs of name and default argument, with the name just below the object on the stack, for keyword-only parameters(argc >> 16) & 0x7FFF
parameter annotation objects- a tuple listing the parameter names for the annotations (only if there are any annotation objects)
- the code associated with the function (at TOS1)
- the qualified name of the function (at TOS)
-
MAKE_CLOSURE
(argc)¶ Creates a new function object, sets its __closure__ slot, and pushes it on the stack. TOS is the qualified name of the function, TOS1 is the code associated with the function, and TOS2 is the tuple containing cells for the closure’s free variables. argc is interpreted as in
MAKE_FUNCTION
; the annotations and defaults are also in the same order below TOS2.
-
BUILD_SLICE
(argc)¶ Pushes a slice object on the stack. argc must be 2 or 3. If it is 2,
slice(TOS1, TOS)
is pushed; if it is 3,slice(TOS2, TOS1, TOS)
is pushed. See theslice()
built-in function for more information.
-
EXTENDED_ARG
(ext)¶ Prefixes any opcode which has an argument too big to fit into the default two bytes. ext holds two additional bytes which, taken together with the subsequent opcode’s argument, comprise a four-byte argument, ext being the two most-significant bytes.
-
CALL_FUNCTION_VAR
(argc)¶ Calls a callable object, similarly to
CALL_FUNCTION
. argc represents the number of keyword and positional arguments, identically toCALL_FUNCTION
. The top of the stack contains keyword arguments (if any), stored identically toCALL_FUNCTION
. Below that is an iterable object containing additional positional arguments. Below that are positional arguments (if any) and a callable object, identically toCALL_FUNCTION
. Before the callable object is called, the iterable object is « unpacked » and its contents are appended to the positional arguments passed in. The iterable object is ignored when computing the value ofargc
.Modifié dans la version 3.5: In versions 3.0 to 3.4, the iterable object was above the keyword arguments; in 3.5 the iterable object was moved below the keyword arguments.
-
CALL_FUNCTION_KW
(argc)¶ Calls a callable object, similarly to
CALL_FUNCTION
. argc represents the number of keyword and positional arguments, identically toCALL_FUNCTION
. The top of the stack contains a mapping object containing additional keyword arguments. Below this are keyword arguments (if any), positional arguments (if any), and a callable object, identically toCALL_FUNCTION
. Before the callable is called, the mapping object at the top of the stack is « unpacked » and its contents are appended to the keyword arguments passed in. The mapping object at the top of the stack is ignored when computing the value ofargc
.
-
CALL_FUNCTION_VAR_KW
(argc)¶ Calls a callable object, similarly to
CALL_FUNCTION_VAR
andCALL_FUNCTION_KW
. argc represents the number of keyword and positional arguments, identically toCALL_FUNCTION
. The top of the stack contains a mapping object, as perCALL_FUNCTION_KW
. Below that are keyword arguments (if any), stored identically toCALL_FUNCTION
. Below that is an iterable object containing additional positional arguments. Below that are positional arguments (if any) and a callable object, identically toCALL_FUNCTION
. Before the callable is called, the mapping object and iterable object are each « unpacked » and their contents passed in as keyword and positional arguments respectively, identically toCALL_FUNCTION_VAR
andCALL_FUNCTION_KW
. The mapping object and iterable object are both ignored when computing the value ofargc
.Modifié dans la version 3.5: In versions 3.0 to 3.4, the iterable object was above the keyword arguments; in 3.5 the iterable object was moved below the keyword arguments.
-
HAVE_ARGUMENT
¶ This is not really an opcode. It identifies the dividing line between opcodes which don’t take arguments
< HAVE_ARGUMENT
and those which do>= HAVE_ARGUMENT
.
32.12.4. Opcode collections¶
These collections are provided for automatic introspection of bytecode instructions:
-
dis.
opname
¶ Sequence of operation names, indexable using the bytecode.
-
dis.
opmap
¶ Dictionary mapping operation names to bytecodes.
-
dis.
cmp_op
¶ Sequence of all compare operation names.
-
dis.
hasconst
¶ Sequence of bytecodes that access a constant.
-
dis.
hasfree
¶ Sequence of bytecodes that access a free variable (note that “free” in this context refers to names in the current scope that are referenced by inner scopes or names in outer scopes that are referenced from this scope. It does not include references to global or builtin scopes).
-
dis.
hasname
¶ Sequence of bytecodes that access an attribute by name.
-
dis.
hasjrel
¶ Sequence of bytecodes that have a relative jump target.
-
dis.
hasjabs
¶ Sequence of bytecodes that have an absolute jump target.
-
dis.
haslocal
¶ Sequence of bytecodes that access a local variable.
-
dis.
hascompare
¶ Sequence of bytecodes of Boolean operations.