Why Python 3 as the default... why?!

eazy · 2010-11-26 15:17:43

I do not mean to rant, but I'd like to know the real motivation behind the Python 2 -> 3 transition.

It is not retro-compatible, Python 2 has been around since 2000 and we're breaking about the last 10 years of python scripts and packages.
Python 2.7 was the most reasonable choice being retro-compatible, supporting Python 3 syntax and giving warnings about deprecated constructs and modules. Why have you (/we) chosen to break away from it?

I am quite an advanced user, I have no issue changing the interpreter of a python script from "python" to "python2", but when application with embedded python break what can I do? Example: no more lyrics, context pane, DAAP and cover art in Rhythmbox, awesome

I expected such an irresponsible change in actively mantained distrubution such as Ubuntu (remember ALSA -> Pulseaudio transition?), not in Archlinux where we have to wait gazillion of upstream developers to update their packages (The official Python package repository, PyPI, lists 12175 packages for Python 2, less than 1000 for Python 3).

I do absolutely see no reason for this except speeding up Python 3 adoption at the expense of end users. OK, we are advanced users, but we are users nonetheless.

Just my 0,02 €.

Allan · 2010-11-26 15:26:21

This has been covered many times already around here as a simple forums search would have told you. So I have come to the conclusion that you really do not want to know why, but rather complain, so I won't explain it yet again or provide you links ...

markbabc · 2010-11-26 15:27:10

Someone has to do it first to force developers to adopt 3.x standards, if your so pissed about it in your .bashrc just make an alias python='python2' and be done with it

eazy · 2010-11-26 15:33:02

Allan wrote:

a simple forums search would have told you. So I have come to the conclusion that you really do not want to know why, but rather complain, so I won't explain it yet again or provide you links ...

I did, and I have not found a plausible answer. I'm continuing to search though.

I do not care about complaining, as I said I have no problem solving 95% of those breakings.

markbabc wrote:

if your so pissed about it in your .bashrc just make an alias python='python2' and be done with it

This does not solve embedded python errors such as Rhythmbox.

This was meant to be a constructive question, don't need to react that badly. Close the thread if you feel it is useless/threathening/stupid.

aeosynth · 2010-11-26 15:44:00

/usr/bin/python is just a symlink to python3; make it link to python2 and you'll be fine.

jlcordeiro · 2010-11-26 16:24:20

not again...

wonder · 2010-11-26 16:31:58

eazy wrote:

Example: no more lyrics, context pane, DAAP and cover art in Rhythmbox, awesome

for your information, this are not because of python at all. 0.13.2 upstream bugs for the first and last. DAAP i'm not aware of any bugs

jasonwryan · 2010-11-26 17:43:58

jlcordeiro wrote:

not again...

Indeed. Closing.

Arch Linux

#1 2010-11-26 15:17:43

Why Python 3 as the default... why?!

#2 2010-11-26 15:26:21

Re: Why Python 3 as the default... why?!

#3 2010-11-26 15:27:10

Re: Why Python 3 as the default... why?!

#4 2010-11-26 15:33:02

Re: Why Python 3 as the default... why?!

#5 2010-11-26 15:44:00

Re: Why Python 3 as the default... why?!

#6 2010-11-26 16:24:20

Re: Why Python 3 as the default... why?!

#7 2010-11-26 16:31:58

Re: Why Python 3 as the default... why?!

#8 2010-11-26 17:43:58

Re: Why Python 3 as the default... why?!

Board footer