Closed eltrevii closed 1 year ago
This is actually a problem in the cross disassembler xdis
. Right now no one has added 3.11 opcodes for that or checked it out for 3.11. I have opened issue https://github.com/rocky/python-xdis/issues/98 for this.
Note that it needs a volunteer to fix - hey, how about you?
if there was a workaround i wouldnt [sic] have made this issue
@aritz331 There always is a workaround. This is open-source code, and so is xdis. So you can always go into either and adjust the code.
@rocky im not a python dev
@aritz331 Ok - then another workaround is to pay a python dev to do the things that you can't do.
@rocky are you serious?
@aritz331 Here is some serious advice - to increase the likelihood of issues you report getting worked on by others, (since as you say you aren't able or likely to to do this yourself), you should cut out the attitude in the issue reporting and conversations.
Oh and by the way, if this weren't open source you wouldn't expect someone to volunteer to fix issues.
ok whatever
Description
How to Reproduce
Output Given
Expected behavior
showing a usage message or something, like
usage: uncompyle6 ...
Environment
Uncompyle6 version: output from
uncompyle6 --version
orpip show uncompyle6
uncompyle6 does not work at all;pip
output:Python version for the version of Python the byte-compiled the file:
python -c "import sys; print(sys.version)"
wherepython
is the correct CPython or PyPy binary. bad magic number in .pyc fileOS and Version: [e.g. Ubuntu bionic] windows 10
Workarounds
if there was a workaround i wouldnt have made this issue
Priority
Additional Context