This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients idle947, vinay.sajip
Date 2021-06-03.13:03:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622725390.31.0.643130572126.issue44286@roundup.psfhosted.org>
In-reply-to
Content
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.
History
Date User Action Args
2021-06-03 13:03:10vinay.sajipsetrecipients: + vinay.sajip, idle947
2021-06-03 13:03:10vinay.sajipsetmessageid: <1622725390.31.0.643130572126.issue44286@roundup.psfhosted.org>
2021-06-03 13:03:10vinay.sajiplinkissue44286 messages
2021-06-03 13:03:10vinay.sajipcreate