News for hackers. Stuff that matters.
Re:Show HN: Virtualenv-mv – Move (rename) Python virtualenvs by m_mueller on Sunday June 12, 2016 @03:36AM (#11887109)
No, my point is rather: Why do we need virtualenv at all (and worse, more wrappers around it)? Why should, say, pip packages have any problems with each other as long as they aren't imported directly in a python sourcefile. It seems like versioning of packages isn't solved correctly at the interpreter level, that's why we have the virtualenv crutch.
Re:Show HN: Virtualenv-mv – Move (rename) Python virtualenvs by neuroid on Sunday June 12, 2016 @08:10AM (#11887734)
Why should, say, pip packages have any problems with each other as long as they aren't imported directly in a python sourcefile.

Are you suggesting that package versions should be explicitly provided as part of import statements? Or that import statements should be mangled depending on the versions specified in setup.py?

Re:Show HN: Virtualenv-mv – Move (rename) Python virtualenvs by m_mueller on Sunday June 12, 2016 @09:18AM (#11887957)
> Are you suggesting that package versions should be explicitly provided as part of import statements?

Yep, see also my suggestion in the other subthread.