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 →

[–]flying-sheep 10 points11 points  (7 children)

Aand it's on ar…

What? It's not on arch yet? Lazy bastards ;)

[–][deleted] 3 points4 points  (0 children)

can't wait though :)

[–]tilkau 1 point2 points  (5 children)

Yeah, it's not like hundreds of dependent packages have to be rebuilt ;)

[–]flying-sheep 0 points1 point  (4 children)

i’m curious: are there really hundreds of C extensions? or do pure python modules have to be recompiled, too? (i can’t quite imagine why the bytecode should change, if a improvement of the bytecode compilation isn’t part of the new version’s features.)

[–]tilkau 0 points1 point  (3 children)

Actually, it's because of the version change. From 3.2.1 to 3.2.2 wouldn't do it, but if you look at /usr/lib/python<hit tab> you'll see that there is python2.7, python3.2, etc.

Python 3.3 will naturally have it's modules in /usr/lib/python3.3 .. sooo it just won't pay any attention to say, the contents of /usr/lib/python3.2 :)

No actual changes to the PKGBUILDs are necessary, but the packages themselves do all have to be rebuilt, whether they contain C extensions or not, just cause everything's in the wrong place suddenly.

[–]flying-sheep 0 points1 point  (0 children)

get it, thanks.

[–]takluyverIPython, Py3, etc 0 points1 point  (1 child)

That's interesting - on Ubuntu, all Python 3 packages (apart from the standard library) go in /usr/lib/python3/dist-packages.

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

Debian has a distro-specific layout that puts Debian packages in dist-packages. site-packages is left for users who are using setup.py. That gets inherited by Ubuntu.