Evaluate: Use pipenv to manage virtualenv + pip

[viktorsmari]

Has anyone had a look at these tools?

https://github.com/pyenv/pyenv

https://github.com/pypa/pipenv

Video: https://pipenv.readthedocs.io/en/latest/

Difference explained: https://stackoverflow.com/questions/41573587/what-is-the-difference-between-venv-pyvenv-pyenv-virtualenv-virtualenvwrappe

[bjornlevi]

This looks interesting. Haven't tested it yet though. One has to wonder about the development power behind it and as such the sustainability.

On Mon, Jan 28, 2019 at 11:35 AM Viktor Smári notifications@github.com wrote:

Has anyone had a look at this?

https://github.com/pypa/pipenv

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/piratar/wasa2il/issues/226, or mute the thread https://github.com/notifications/unsubscribe-auth/AAvcMF0jL5ipO-8fve0xHylpSjrsj89zks5vHuCOgaJpZM4aVuqI .

[viktorsmari]

Also: Python 3.6 and newer have a built in way to handle virtual environments, so maybe we wait until we upgrade from 2 -> 3

pyvenv is deprecated as of Python 3.6 and the new way is: python3 -m venv /path/to/new/virtual/environment

Source: https://stackoverflow.com/questions/23842713/using-python-3-in-virtualenv

[helgihg]

Apparently Python 2.7 will be deprecated on January 1, 2020, so it looks like we'll need to upgrade to Python 3.x / Django 2.x this year.

On 1.2.2019 07:52, Viktor Smári wrote:

Also: Python 3.6 and newer have a built in way to handle virtual environments, so maybe we wait until we upgrade from 2 -> 3

pyvenv is deprecated as of Python 3.6 and the new way is: python3 -m venv /path/to/new/virtual/environment

Source: https://stackoverflow.com/questions/23842713/using-python-3-in-virtualenv

[viktorsmari]

Have you had a look at this recently?

Been 2 years since we last discussed, and maybe a 'best practice' has been formed in the Python community?