.
Then there is a package called python-wrapper, which simply adds the
following symlinks into the Python 3 bin/ directory:
idle - idle3
pydoc - pydoc3
python - python3
It is used internally as an input, so that shebangs need not be rewritten;
but users may also install it if they wish Python 3
l...@gnu.org (Ludovic Courtès) writes:
My understanding was that users (really: Python developers) would expect
to get a ‘python3’ binary when they install the latest, and a ‘python’
binary otherwise.
It depends. I've grown used to having python(-python3) and python2
binaries in
On Sun, Sep 01, 2013 at 07:34:03PM +0200, Ludovic Courtès wrote:
However, my understanding from what Cyril and Brandon said is that users
may prefer to have it called ‘python3’ by default, so they can install
both Python 2 and Python 3 in parallel. Furthermore, they can choose to
have (say)
On Sun, Sep 01, 2013 at 07:40:18PM +0200, Cyril Roelandt wrote:
Packages usually exist in two different versions: python-foo and
python3-foo.
I think this is quite a good way of packaging both Python 2 and 3.
One day, maybe nobody will use Python 2.x any more, and we'll just
use python
Cyril Roelandt tipec...@gmail.com skribis:
On 08/31/2013 05:30 PM, Andreas Enge wrote:
Hello,
python 3 does not ship a python binary any more, just a binary called
python3. That could be useful, since it would allow to install python 2 and 3
side by side. However, all packages relying on a
