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 properly because it was the PATH before the replacement.

How about adding a procedure to verify the __VENV_DIR__ is a valid PATH to the Activate Script?

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 recreated - so if you need a venv in a new location, just create it there and install the desired packages again.

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 invalid path, i thought any warning message or exception handling was necessary. Or (venv) doesn't show up.

> 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 engineered to notice, and so will not behave as you expect.

As venv's aren't meant to be moved, there's no particular reason to engineer for that possibility.

OK to close this issue as "not a bug"?

Okay. Thank you for the detailed explanation.