Re: Adopting virtualenv package maintenance
Matthew Brett <[email protected]>
| Newsgroups | gmane.comp.python.distutils.devel |
|---|---|
| Message-ID | <CAH6Pt5pAUDTNBftmOsmH8x4Q6vYBnELequQN7eZgjxWSHbbQ0Q@mail.gmail.com> |
Hi, On Thu, Sep 6, 2018 at 9:42 PM, Alex Becker <[email protected]> wrote: > Another +1 to the utility of a maintainer. I am also working on package > management and have found that venv is not a full replacement for > virtualenv--for example I don't believe the environment can be entered > programatically, while virtualenv provides activate_this.py which can be > exec'd. I'm sure there are many other limitations, so I don't think python > can give up on virtualenv soon. Just to add - I use virtualenv often, and I would be happy to know it is maintained. On reflection, the reason I am not using venv is because a) I still need to test on Python 2.7 and b) I like `virtualenvwrapper`. I suppose someone could rewrite virtualenvwrapper to use venv instead, but a) is only going to stop being a requirement sometime after 2020. Cheers, Matthew -- Distutils-SIG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/2ODF6E3UJLJXK7A5YQHJ7UIFQYUIPOLI/