FIX: Generated shebang with path to python invalid if path contains spaces

[ksshen0000]

Pwntools Pull Request

Thanks for contributing to Pwntools! Take a moment to look at CONTRIBUTING.md to make sure you're familiar with Pwntools development.

Please provide a high-level explanation of what this pull request is for.

Testing

Pull Requests that introduce new code should try to add doctests for that code. See TESTING.md for more information.

Target Branch

Depending on what the PR is for, it needs to target a different branch.

You can always change the branch after you create the PR if it's against the wrong branch.

Branch	Type of PR
dev	New features, and enhancements
dev	Documentation fixes and new tests
stable	Bug fixes that affect the current stable branch
beta	Bug fixes that affect the current beta branch, but not stable
dev	Bug fixes for code that has never been released

Changelog

After creating your Pull Request, please add and push a commit that updates the changelog for the appropriate branch.
You can look at the existing changelog for examples of how to do this.

[peace-maker]

This seems to assume Python 3 which might not be installed when using Python 2.

[ksshen0000]

there is another option that is to create a softlink. But the website says python2 is deprecated

[peace-maker]

We're still supporting python 2 installs right now though, so need to think of that.

Another way would be to ignore the shebang line and just add the sys.executable to the argv array directly.

[Arusekk]

Honestly I think it is okay to just always use python3; this is just a thin wrapper, so nothing bad should happen.

[peace-maker]

I think your /usr/bin/env /path/with spaces/python suggestion is better, since it is fully backwards compatible. And I agree it should only be emitted if there are spaces in the sys.executable path.
#2271 (comment)