[Distutils] Re: Adopting virtualenv package maintenance

On Sun, 16 Sep 2018 at 15:08, Nick Coghlan wrote: > So if folks are still interested in the general idea of improving virtualenv > and venv interoperability, then my last message to that thread and Paul's > follow up would be a decent place to start: >

[Distutils] Re: Adopting virtualenv package maintenance

Sorry, hit the send button too soon. Here’s the project: https://github.com/sarugaku/virtenv > On 16/9/2018, at 22:50, Tzu-ping Chung wrote: > > Thanks for pointing out the PR, I didn’t know that exists :D > > I made a thin wrapper around virtualenv/venv

[Distutils] Re: Adopting virtualenv package maintenance

Thanks for pointing out the PR, I didn’t know that exists :D I made a thin wrapper around virtualenv/venv a while ago too. My intention is to use it to abstract away library differences so I can bring native venv support to Pipenv more easily, so the library has some special quirks (e.g. uses

[Distutils] Re: Adopting virtualenv package maintenance

On Sat, 8 Sep 2018 at 13:34, Brett Cannon wrote: > On Fri., Sep. 7, 2018, 16:32 Dan Ryan, wrote: > >> I’m thinking (and correct me if I’m wrong here) that Brett’s message >> might be motivated more by a desire to standardize and centralize effort >> by first assessing what the issue is. >> >

[Distutils] Re: Adopting virtualenv package maintenance

my // e: d...@danryan.co From: Tzu-ping Chung [mailto:uranu...@gmail.com] Sent: Friday, September 07, 2018 5:42 PM To: Brett Cannon Cc: Alex Becker; sorin.sbar...@gmail.com; distutils-sig@python.org Subject: [Distutils] Re: Adopting virtualenv package maintenance On 08/9/2018, at 02:23, Brett Cannon wrote

[Distutils] Re: Adopting virtualenv package maintenance

On Sat, 8 Sep 2018 at 04:36, Brett Cannon wrote: > - activate_this.py (which provides critical inline activation for us when >> people invoke "pipenv run" from the command line) >> > It might make sense to try and add an 'activate' command to venv, e.g. > 'python -m venv --activate .venv' as a

[Distutils] Re: Adopting virtualenv package maintenance

Hi, On Thu, Sep 6, 2018 at 9:42 PM, Alex Becker 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

[Distutils] Re: Adopting virtualenv package maintenance

On Fri, Sep 7, 2018, 14:41 Tzu-ping Chung wrote: > > Just want to mention that adding activate_this.py to venv has been > proposed, and rejected. > https://bugs.python.org/issue21496 > Looks like the reason for the rejection was just that the submitter didn't provide a good rationale. If this

[Distutils] Re: Adopting virtualenv package maintenance

> On 08/9/2018, at 02:23, Brett Cannon wrote: > > > > On Fri, 7 Sep 2018 at 11:18 Nathaniel Smith > wrote: > On Fri, Sep 7, 2018, 10:48 Brett Cannon > wrote: > > > On Thu, 6 Sep 2018 at 13:44 Alex Becker >

[Distutils] Re: Adopting virtualenv package maintenance

On Fri, 7 Sep 2018 at 11:18 Nathaniel Smith wrote: > On Fri, Sep 7, 2018, 10:48 Brett Cannon wrote: > >> >> >> On Thu, 6 Sep 2018 at 13:44 Alex Becker 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

[Distutils] Re: Adopting virtualenv package maintenance

On Fri, Sep 7, 2018, 10:48 Brett Cannon wrote: > > > On Thu, 6 Sep 2018 at 13:44 Alex Becker 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

[Distutils] Re: Adopting virtualenv package maintenance

On Thu, 6 Sep 2018 at 13:44 Alex Becker 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

[Distutils] Re: Adopting virtualenv package maintenance

"What is the difference between venv, pyvenv, pyenv, virtualenv, virtualenvwrapper, pipenv, etc?" https://stackoverflow.com/questions/41573587/what-is-the-difference-between-venv-pyvenv-pyenv-virtualenv-virtualenvwrappe virtualenvwrapper still depends on virtualenv, AFAIU

[Distutils] Re: Adopting virtualenv package maintenance

I'm maintainer of tox and tox is heavily relying on virtualenv. I would be up for being a co maintainer, but for now I don't have availability for heavy undertakings. I've had a discussion with Donald at Pycon us about it and there certainly is a desire and place for virtualenv. the issue is

[Distutils] Re: Adopting virtualenv package maintenance

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

[Distutils] Re: Adopting virtualenv package maintenance

I don’t have the authority to do it, but I would really love to see virtualenv getting maintenance. Pipenv still depends on virtualenv because for not only Python 2. I am already working on switching to venv for Python 3.5+, but we will continue to need virtualenv for quite a while due to some