On Wed, Jan 25, 2017 at 12:39 PM Dave Page <dpage@pgadmin.org> wrote:
As far as I can see, this breaks usage in development environments, or any configurations where the Python code may be separated from the runtime. Am I missing something?
What kind of setup are you talking about? It's not clear to me.
If the venv doesn't exist, the program name becomes "/python" and you get the standard environment including whatever packages you installed with "pip install" or "pip install --user".
Granted, "/python" is nonsense and should probably just be "python". Also, I think PATH doesn't need to be touched at all anymore, so the lines involving pathEnv can be removed.
How about a settings key to force the program name? That would allow choosing any other virtualenv to run with.
