Your message dated Sat, 4 Jul 2015 12:43:10 -0700
with message-id <[email protected]>
and subject line Re: Bug#789174: python-virtualenv (Python 2) dependent on
Python 3
has caused the Debian Bug report #789174,
regarding python-virtualenv (Python 2) dependent on Python 3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
789174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789174
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-virtualenv
Version: 1.11.6+ds-1
I have a system that needs Python 2. I have Python 2.7 installed. I also need
`virtualenv`.
`python-virtualenv` states "This is the Python 2 version of the library.”:
https://packages.debian.org/jessie/python-virtualenv
<https://packages.debian.org/jessie/python-virtualenv>
However, it depends on `python-pip-whl`:
https://packages.debian.org/jessie/python-pip-whl
<https://packages.debian.org/jessie/python-pip-whl>
Which, in turn, depends on `python-chardet-whl`:
https://packages.debian.org/jessie/python-chardet-whl
<https://packages.debian.org/jessie/python-chardet-whl>
…and that depends on `python3-pkg-resources`, which requires `python3`.
So, to install `virtualenv` for Python 2, there’s a dependency on Python 3.
This is not right.
--- End Message ---
--- Begin Message ---
Hi Sean (2015.06.18_08:04:42_-0700)
> So, to install `virtualenv` for Python 2, there’s a dependency on Python 3.
> This is not right.
This is intentional.
Before this change was made, creating a virtualenv for Python 3 required
installing Python 2. That was equally "not right".
Now there's a separate package called "virtualenv", that contains this
command. python-virtualenv recommends this, for backwards-compatibility
reasons. If you had it installed, you should still have the virtualenv
command available.
We could go to some effort, with Python applications, to ensure that
both the Python 2 and Python 3 versions install a command that works
identically. However, this requires a lot of complexity, and doesn't
really achieve anything useful.
From the point of view of the user, you just want to create a
virtualenv. You don't care which version of Python was used to do that,
as long as the virtualenv is for the right version of Python.
Consider Python 2 as legacy. Our Python applications will now default to
run on Python 3, where possible.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
