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 Jeff.Edwards
Recipients Jeff.Edwards, brett.cannon, vinay.sajip
Date 2020-01-28.18:32:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAEWphW1=Oe=3gi_Z8qjVRco+LnXfmcB1bAw8U0Ca3fXUVc-baw@mail.gmail.com>
In-reply-to <1580236076.96.0.281019160279.issue39469@roundup.psfhosted.org>
Content
I would say they’re not designed to be, but the also aren’t designed to not
be portable.  This is often useful where open network access isn’t
reasonable, so access to Pip/pipx/pipenv is limited at best.

Suffice to say, is there a significant reason to not allow it?

On Tue, Jan 28, 2020 at 10:28 AM Brett Cannon <report@bugs.python.org>
wrote:

>
> Brett Cannon <brett@python.org> added the comment:
>
> Do note that virtual environments are not designed to be portable in
> general, so this would be a fundamental change in the design and purpose of
> virtual environments.
>
> ----------
> nosy: +brett.cannon, vinay.sajip
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue39469>
> _______________________________________
>
History
Date User Action Args
2020-01-28 18:32:16Jeff.Edwardssetrecipients: + Jeff.Edwards, brett.cannon, vinay.sajip
2020-01-28 18:32:16Jeff.Edwardslinkissue39469 messages
2020-01-28 18:32:16Jeff.Edwardscreate