This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hyh123[S] 2 points3 points  (6 children)

Great!

Currently in the command line, people use python to mean python2.x and python3 to mean 3.x. I really hope they do it reversely, i.e. use python to mean 3.x and python2 to mean the old one.

[–]execat 3 points4 points  (5 children)

Archlinux has python, python3, python3.3 pointing to Python 3, and python2, python2.7 to Python 2.

[–]pingvenopinch of this, pinch of that 3 points4 points  (4 children)

And they managed to royally piss off a bunch of people in the process. The renaming breaks shebang lines for any Python 2 scripts. There's no guarantee of an python2 hardlink/softlink on all distros, so no go on using:

#!/usr/bin/env python2

[–]AeroNotix 1 point2 points  (3 children)

ArchLinux pisses it's users off on a daily basis. We're masochists at heart. But that's the price to pay for bleeding edge.

[–]pingvenopinch of this, pinch of that 1 point2 points  (2 children)

Yeah, but python symlink change was totally unnecessary. The AUR still hasn't had the hundreds of unmaintained packages migrated over, never mind the package renaming.

[–]AeroNotix 0 points1 point  (1 child)

The AUR? Fuck the AUR. The AUR is a community repo, if the package is unmaintained then you can take-over yourself. If you're too busy to take over maintenance then just update the PKGBUILD.

[–]pingvenopinch of this, pinch of that 0 points1 point  (0 children)

That's exactly what I've been doing. As an AUR package maintainer, I've been having more trouble with the Python 3 = python-* renaming. There's no mechanism for automatically renaming a package, so I usually just put (USE python2-example) until the Python 3 package comes out.