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.
On Thu, Sep 6, 2018 at 12:48 AM Tzu-ping Chung <uranu...@gmail.com> wrote: > 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 > compatibility issues, even on Python 3. We occasionally get bug reports > about virtual environment > creation, and those generally are due to some long standing bugs in > virtualenv. It would be awesome > if we could point reporters somewhere to actually get things fixed, > instead of say sorry with a shrug. > > I am not suggesting in particular who should be the maintainer(s) (but > also not objecting to Sorin’s > proposal), but virtualenv really needs a maintainer. > > TP > > > > On 05/9, 2018, at 16:56, Sorin Sbarnea <sorin.sbar...@gmail.com> wrote: > > > > As it seems that virtualenv package is in need of some maintenance > effort, focused mostly on doing reviews, closing or merging them and > eventually doing a new release once a month. > > > > I know that virtualenv is in deprecation mode as its would be no longer > needed when Python2 will no longer be used. The reality is that Python 2.x > will still be in production after January 1st, 2020 because there are > deployed products with LTS contracts which will need some time to get > updated to newer versions that use py3. This automatically translates to > the need to have a working virtualenv for testing them. I am part of the > OpenStack team and I am sure that, even if I like it or not, I would have > to deal with some amount of py2 even after the magic date. > > > > The current situation with virtualenv is pretty bad because there are > lots of open pull-requests which are not reviewed or merged, mostly because > there is nobody available to do that boring extra work. I had few changes > that were improving the CI testing of virtualenv which soon will be one > year old,... most of them without any feedback. Even finding whom to ping > by email or irc was a challenge as I got two responses: no response at all > or someone else telling me that they are not maintainers of the virtualenv > package. Example > https://groups.google.com/forum/#!topic/pypa-dev/YMVsRbNoVpg > > > > For these reasons I would like to become a maintainer for virtualenv, > preferably working with two others on keeping it alive for a couple of > years till we could organize a big wake ceremony for it. > > > > It would be preferable if two others would join the maintenance > "taskforce" because merging a change should almost always involve at least > two reviewers. > > > > While I cannot make any guarantees regarding dealing with all reported > bugs, I can commit on assuring that there are no PRs that are not reviewed > for longer than 30 days (aiming for one week). Now there are ~75 open PRs. > I have being doing open source for a long time and I respect all the time > and efforth put by project maintainers and at the same time I always tried > to do my best dealign with incoming PRs because if someone spended his time > trying to make a contribution that is passing CI, they probably deserve at > least a review. > > > > https://github.com/pypa/virtualenv/pulls > > > > Thanks > > Sorin Sbarnea > > @ssbarnea on irc/github/... > > -- > > Distutils-SIG mailing list -- distutils-sig@python.org > > To unsubscribe send an email to distutils-sig-le...@python.org > > https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ > > Message archived at > https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/EOXOL3742HVDLAIQDODL36UNRGU4R6SG/ > -- > Distutils-SIG mailing list -- distutils-sig@python.org > To unsubscribe send an email to distutils-sig-le...@python.org > https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ > Message archived at > https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/TFUYTDYSOLT3KJ2SRPM7Y7K6GNDK5TMW/ >
-- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-le...@python.org https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/KPA3KB43OFHZ76VMTZTXSV7PLQMLDIG2/
