Josh ef0f83232f call python via /usr/bin/env python =more portable ...

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

```Shell
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)

```Shell
uncompyle2# ./scripts/uncompyle2 -h

Usage: uncompyle2 [OPTIONS]... [ FILE | DIR]...
...snip...
```

2015-06-23 15:55:55 -05:00

..

uncompyle2

call python via /usr/bin/env python =more portable

2015-06-23 15:55:55 -05:00