So as a conclusion to this, I think we can say everyone agrees
virtualenv should have some maintenance for a next few years at least.
Sorin and I offered to help with this, can we get some PyPa people
help with this (e.g. give rights on repo) ?
Thanks!
> It should probably be noted that the
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
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
