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 DamlaAltun, brett.cannon, uranusjr, vinay.sajip
Date 2019-11-29.22:22:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1575066154.37.0.890114710159.issue35003@roundup.psfhosted.org>
In-reply-to
Content
> so maybe proposing a simple `venv --activate <path>` that does nothing more than set those key environment variables

If venv is run in a child process of the shell, how does it set those variables in the parent shell? I thought that wasn't possible (on POSIX, anyway), which is why e.g. pew spawns a subshell.

> Sure, but then that doesn't mean activation isn't convenient

Indeed it is. But many less experienced users think that it's always a necessary step, when it isn't always so.
History
Date User Action Args
2019-11-29 22:22:34vinay.sajipsetrecipients: + vinay.sajip, brett.cannon, uranusjr, DamlaAltun
2019-11-29 22:22:34vinay.sajipsetmessageid: <1575066154.37.0.890114710159.issue35003@roundup.psfhosted.org>
2019-11-29 22:22:34vinay.sajiplinkissue35003 messages
2019-11-29 22:22:34vinay.sajipcreate