shebangs in packaged venv are unusable without activating environment

[manuco]

Today, venv_pack replaces all shebang of console scripts with the "/usr/bin/env python" trick that will use the path. This approach only works when the venv is "activated" and the python interpreter of this venv is placed in the $PATH. With a proper shebang, those commands would be usable without activating the environment, thus working more reliably.

The proper way to do this would be to have a post-unarchive script that fix things all around (fix the venv to base interpreter simlink, the shebang, etc.). This script could lay in the bin directory of the environment and fix this env when called with the local python interpreter. Another idea is to add an option which allow the caller to set the destination shebang. It is not as convenient, but will allow packaging scripts to set shebangs to something they can compute.

Is there any plan to do a thing like this? Is this idea ok, or am I missing something?