If these had been available in Python 3.2 or even better 3.0, the switch would have been far easier for corporate users that need benefits before accepting the cost of change...
Before that it would give you an empty venv, not even setuptools
Yes, you can use the Python 2 virtualenv on Py 3 but I remember that there were some problems
python -m venv
I'm not sure what the differences are to old virtualenv, but the biggest feature is that it works out of the box as long as you have Python > 3.4. No more googling "how to install virtualenv" or "easy_install pip; pip install virtualenv" stuff.The big improvement on 16.04 is at least the error message explains what's going on.
That's not the case. See for example https://www.python.org/dev/peps/pep-0484/#type-definition-sy...
i) its not a type checker. It cannot actually ensure type correctness. So may be a more appropriate description would be "a very smart linter".
ii) Its optional
iii) even when switched on it does nothing unless you are explicitly using its features
iv) The "there is only one way to do things in Python" is just vapid marketing. It is not true and has never been true.
It's not even that, the actual quote is "There should be one, and preferably only one, obvious way to do things". The whole "there is only one way to do it" was a joke response to Perl's "There's more than one way to do it" motto.
The original version was too implicit. Unless you are Dutch.