skip all the byecode hex data, it's adequately checked
... by the disassembly just below This was tripped up because in exactly the right conditions some qstr could be of the form 'xx 63' and make the expression `\.\+63` match something other than what was intended. This test was re-worked upstream for mpy version 6 so it'll be a conflict to resolve when we get to that. :-/
This commit is contained in:
parent
29a4364ba7
commit
f71831dea9
@ -1,7 +1,6 @@
|
|||||||
File cmdline/cmd_showbc.py, code block '<module>' (descriptor: \.\+, bytecode @\.\+ bytes)
|
File cmdline/cmd_showbc.py, code block '<module>' (descriptor: \.\+, bytecode @\.\+ bytes)
|
||||||
Raw bytecode (code_info_size=\\d\+, bytecode_size=\\d\+):
|
Raw bytecode (code_info_size=\\d\+, bytecode_size=\\d\+):
|
||||||
########
|
########
|
||||||
\.\+63
|
|
||||||
arg names:
|
arg names:
|
||||||
(N_STATE 3)
|
(N_STATE 3)
|
||||||
(N_EXC_STACK 0)
|
(N_EXC_STACK 0)
|
||||||
|
Loading…
Reference in New Issue
Block a user