Closed kernelsmith closed 9 years ago
The shebang line of the uncompyle2 script is not using /usr/bin/env python causing it to fail to run when invoked as a standalone script
uncompyle2# ./scripts/uncompyle2 -h bash: ./scripts/uncompyle2: python: bad interpreter: No such file or directory
Changing the shebang line to #!/usr/bin/env python fixes the problem and is best practice (or so I'm told)
uncompyle2# ./scripts/uncompyle2 -h Usage: uncompyle2 [OPTIONS]... [ FILE | DIR]... ...snip...
Thanks!
The shebang line of the uncompyle2 script is not using /usr/bin/env python causing it to fail to run when invoked as a standalone script
Changing the shebang line to #!/usr/bin/env python fixes the problem and is best practice (or so I'm told)