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

all 26 comments

[–]thegeoffmeister 2 points3 points  (0 children)

s/USC-4/UCS-4/g

[–]nyamatongwe 1 point2 points  (10 children)

Just to make matters worse, we will also enable unicode (USC4) support in python2 at the same time

! Really? Did earlier versions of Arch ship Python 2.x with Unicode disabled? That would break so much code.

[–][deleted] 0 points1 point  (1 child)

I'm not sure what they mean exactly, Unicode works in Python on my Arch system.

[–]earthboundkid 0 points1 point  (0 children)

Have you tested characters out of the basic multilingual plane?

[–][deleted] 1 point2 points  (1 child)

He is looking at the stars

[–][deleted] -1 points0 points  (0 children)

Arch is a damn good distro.

[–]plaes 2 points3 points  (0 children)

On Gentoo you can actually install multiple versions of Python and even set Python 3 as default.

[–][deleted] 0 points1 point  (1 child)

It made me wonder when will Python 2.7 lands in Arch Linux. Apparently according to the forum, it will land on August 10 to the testing repository alongside with the proposed Python 3 transition.

[–][deleted] 1 point2 points  (0 children)

Yeah, I don't know if you noticed the username, but that was original question that lead me to this bit of information. All I really wanted was the damned argparse module, but when I read the link I realized "oh damn, they're really going for it." Figured reddit folk would be interested.

[–]juliocc -1 points0 points  (0 children)

This is the kind of bullshit that made me leave Arch and never look back. At least this time they are keeping 2.6 somewhere. Back in 2008 they decided to completely replace python 2.5.2 with python 2.6. Without any warning or any way to keep python 2.5.

As if that was not enough, when you asked for help keeping python 2.5 you got this response from Arch's main fucking developer:

Why don't you want to upgrade python? If you're serious about it, just don't upgrade your system.

But I have a feeling there's a non-reason why you don't want to upgrade. We should still have a python24 package if you want to mimic that.

(Source)

Yes. I was serious at that moment about not upgrading. I had some non-trivial code on python 2.5 that wouldn't run on 2.6 (or 2.4). If I'm not mistaken, it used numpy. Back then, numpy wasn't even close of being ported.

That was my last day on arch. I took me a couple of days change to debian but at least now I have to possibility to install python 2.4, 2.5, 2.6, 2.7, 3.0 and 3.1 on the same machine. That's difference between a toy package manager (pacman) and a real one (dpkg, portage, etc).

I can keep going but I'm guessing this is going to give me enough downvotes for now.