7 ms·

Virtualenv 20.0.0 Released

26 points by jorshman 7y ago

Nicksil 7y ago
Post's link seems to 404. This may be the correct URL: https://virtualenv.pypa.io/en/stable/changelog.html https://virtualenv.pypa.io/en/stable/changelog.html
ktm5j 7y ago
Link is broken. Looks like it should be: https://virtualenv.pypa.io/en/latest/changelog.html https://virtualenv.pypa.io/en/latest/changelog.html instead of: https://virtualenv.pypa.io/en/latest/changelog/ https://virtualenv.pypa.io/en/latest/changelog/
takeda 7y ago
Any benefits of using this project, virtualenv is now built in in Python 3, and it never was missing anything when I was using it.
- Flimm 7y ago
  venv is shipped with Python 3, not virtualenv, unless I am mistaken.
  - takeda 7y ago
    Yeah, I guess it's called different, but has the same functionality and is a drop-in replacement. I'm surprised there's still development on virtualenv after 2.7 is EOL.
maccam94 7y ago
This isn't the most readable changelog, the main takeaway is at the bottom: The package has been completely rewritten.
- mmebane 7y ago
  This announcement of the 20.0.0 beta is useful for understanding why it was rewritten: https://discuss.python.org/t/virtualenv-20-0-0-beta1-is-available/3077 https://discuss.python.org/t/virtualenv-20-0-0-beta1-is-avai...
downerending 7y ago
I've just been using conda environments lately. How much am I missing by not using virtualenv instead?
- seemslegit 7y ago
  Why did you take up conda in the first place ? venv and pip are part of the python project and conda seems to be yet another package manager in the already crowded and shady space of npm, brew, ports apt yum etc. I've always been puzzled at how they managed to shoehorn themselves into the python ecosystem while offering no distinct value as far as I can see.
  - woodson 7y ago
    They provide useful packages that aren't (easily) available via pip. For example, numpy with MKL or Tensorflow GPU builds that don't require/presuppose CPU support for new vector instructions. Moreover, their package installs don't break as randomly as some pip packages, presumably because someone bothered to do more testing of commonly used packages included in the default package repository.
  - downerending 7y ago
    This is an HPC environment, so besides a nice, working version of TensorFlow, there are large numbers of pre-built scientific/bioinformatics packages. This is a huge win when you're running with a skeleton crew. Also, note this is for system-wide, not per-user usage. I'm kind of vague on how virtualenv would handle this, plus it feels like it's changed a lot over time. (?)
ZeroCool2u 7y ago
This release is exciting, but taking a step back, it's still really disappointing how minimal and rough around the edges venv is considering how important the library ecosystem has been to Python's continued success. I really wish we had a packaging/environment tool the same quality as Rust's cargo.
bsagdiyev 7y ago
This explains why chef started yelling at work 4am PST. Upgrading virtualenv via pip install --upgrade virtualenv would fail. This sort of broken upgrade also happened with pip itself recently and required a manual fix, package maintainers refused to revert the release.

26 points by jorshman 7y ago

Post's link seems to 404. This may be the correct URL: https://virtualenv.pypa.io/en/stable/changelog.html https://virtualenv.pypa.io/en/stable/changelog.html

ktm5j 7y ago

Link is broken. Looks like it should be: https://virtualenv.pypa.io/en/latest/changelog.html https://virtualenv.pypa.io/en/latest/changelog.html instead of: https://virtualenv.pypa.io/en/latest/changelog/ https://virtualenv.pypa.io/en/latest/changelog/

takeda 7y ago

Any benefits of using this project, virtualenv is now built in in Python 3, and it never was missing anything when I was using it.

Flimm 7y ago
venv is shipped with Python 3, not virtualenv, unless I am mistaken.
- takeda 7y ago
  Yeah, I guess it's called different, but has the same functionality and is a drop-in replacement. I'm surprised there's still development on virtualenv after 2.7 is EOL.

maccam94 7y ago

This isn't the most readable changelog, the main takeaway is at the bottom: The package has been completely rewritten.

mmebane 7y ago
This announcement of the 20.0.0 beta is useful for understanding why it was rewritten: https://discuss.python.org/t/virtualenv-20-0-0-beta1-is-available/3077 https://discuss.python.org/t/virtualenv-20-0-0-beta1-is-avai...

downerending 7y ago

I've just been using conda environments lately. How much am I missing by not using virtualenv instead?

seemslegit 7y ago
Why did you take up conda in the first place ? venv and pip are part of the python project and conda seems to be yet another package manager in the already crowded and shady space of npm, brew, ports apt yum etc. I've always been puzzled at how they managed to shoehorn themselves into the python ecosystem while offering no distinct value as far as I can see.
- woodson 7y ago
  They provide useful packages that aren't (easily) available via pip. For example, numpy with MKL or Tensorflow GPU builds that don't require/presuppose CPU support for new vector instructions. Moreover, their package installs don't break as randomly as some pip packages, presumably because someone bothered to do more testing of commonly used packages included in the default package repository.
- downerending 7y ago
  This is an HPC environment, so besides a nice, working version of TensorFlow, there are large numbers of pre-built scientific/bioinformatics packages. This is a huge win when you're running with a skeleton crew. Also, note this is for system-wide, not per-user usage. I'm kind of vague on how virtualenv would handle this, plus it feels like it's changed a lot over time. (?)

ZeroCool2u 7y ago

This release is exciting, but taking a step back, it's still really disappointing how minimal and rough around the edges venv is considering how important the library ecosystem has been to Python's continued success. I really wish we had a packaging/environment tool the same quality as Rust's cargo.

bsagdiyev 7y ago

This explains why chef started yelling at work 4am PST. Upgrading virtualenv via pip install --upgrade virtualenv would fail. This sort of broken upgrade also happened with pip itself recently and required a manual fix, package maintainers refused to revert the release.