[issue44286] venv activate script would be good to show failure.

john kim added the comment: Okay. Thank you for the detailed explanation. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue44286] venv activate script would be good to show failure.

Vinay Sajip added the comment: > i thought any warning message or exception handling was necessary. Or (venv) > doesn't show up. No, because these are just scripts created by venv and placed in the venv's directory tree. If you then move the files to a different location, they aren't engine

[issue44286] venv activate script would be good to show failure.

john kim added the comment: Thank you for your explanation of venv. I understand that venv is not portable. But I was confused because the venv was written on the left side of the terminal line and it looked like it was working. Therefore, if venv does not work, such as if __venv_dir__ is

[issue44286] venv activate script would be good to show failure.

Vinay Sajip added the comment: venvs aren't meant to be portable (i.e. renaming the directory or moving to a new location). Scripts installed into a venv have absolute paths pointing to the location when the venv was created. venvs should be treated as throwaway resources that can be readily

[issue44286] venv activate script would be good to show failure.

Change by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue44286] venv activate script would be good to show failure.

New submission from john kim : I changed the path of the project using venv, so it didn't work properly. I thought it worked successfully because there was a (venv) on the terminal line. However, the __VENV_DIR__ in the set "VIRTUAL_ENV=__VENV_DIR__" in the activate script did not work pr