Public bug reported:

So we're drifting into complicated territory.

 - Python 2 is still the default?
 - Package: python-virtualenv is Python2
 - Package: virtualenv is Python 3 and replaces python-virtualenv
 - Therefore you can't install both

The Ubuntu-Python packaging team needs to decide what takes precedence.
Allowing the names to conflict like this is confusing, unneccessary and
a little bit evil.

For the sanity of devops, I would plead that virtualenv remain a Python
2 binary, the "virtualenv" package be thrown into the sun and
python3-virtualenv changes its binary to virtualenv3 (or people use the
module directly like they have forever `python3 -mvenv ...`)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: virtualenv 14.0.5+ds-2
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Feb 28 13:21:39 2016
PackageArchitecture: all
SourcePackage: python-virtualenv
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-virtualenv (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug xenial

** Description changed:

  So we're drifting into complicated territory.
-  
-  - Python 2 is still the default?
-  - Package: python-virtualenv is Python2
-  - Package: virtualenv is Python 3 and replaces python-virtualenv
-  - Therefore you can't install both
+ 
+  - Python 2 is still the default?
+  - Package: python-virtualenv is Python2
+  - Package: virtualenv is Python 3 and replaces python-virtualenv
+  - Therefore you can't install both
+ 
+ The Ubuntu-Python packaging team needs to decide what takes precedence.
+ Allowing the names to conflict like this is confusing, unneccessary and
+ a little bit evil.
  
  For the sanity of devops, I would plead that virtualenv remain a Python
  2 binary, the "virtualenv" package be thrown into the sun and
  python3-virtualenv changes its binary to virtualenv3 (or people use the
  module directly like they have forever `python3 -mvenv ...`)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: virtualenv 14.0.5+ds-2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 28 13:21:39 2016
  PackageArchitecture: all
  SourcePackage: python-virtualenv
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550923

Title:
  16.04's virtualenv uses Python 3 but python executable is Python 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1550923/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to