News for hackers. Stuff that matters.
Re:Updated Packages – Python 3.3 by masklinn on Friday April 05, 2013 @07:41AM (#5497746)
It was not a rejection. Python 3 (project name Python 3000, just to give you the kind of scope we're talking about) was always expected to be a long and rather arduous migration, because it "cleaned up" a number of things in backwards-incompatible manner: the stdlib was reorganized, syntax was added (and removed), semantics altered (the basic string of Python 2 is a bytestring, in Python 3 it's a codepoint sequence and implicit conversions were removed from the language), shuffling between keywords and regular symbols, etc... It might have been even more arduous than the core team expected, but most of the community has been aware it'd take a long time from the start (the initial planning alone took ~30 months: the PEP3000 was created in April 2006 and Python 3.0 was released in December 2008, and as far as I remember Python 3.0 was not considered a production-able Python, more of a "stable" version for experiments and discovery in real-world settings)

Things were moving very slowly at the start, some features were backported to Python 2, others were reintroduced (in Python 3.2 and 3.3) and compatibility packages slowly appeared as people started experimenting with porting strategies and methods.

Since the second half of 2012, things have started picking up steam as bigger packages have started their migration effort (often as single-source, which is now considered the best strategy when possible) which is starting to solve the chicken-and-eggs problem for end-users (applications can't switch until all their dependencies are compatible)[0].

Python 2 will stick around though, there are 20 years of Python code which won't run as-is on Python 3, and may never do barring significant rewrite.

And of course Python 3 may yet be rejected by the community, although it definitely seems to be gaining — rather than losing — steam. The biggest problems in the long term will probably be in the Scientific Python communities.

[0] A few pretty big names are still Python 2 though, Werkzeug and Flask are big ones for webby stuff, the official-ish MySQL adapter is an other one for many, and a bunch are not considered "production-ready" state or side-packages are missing e.g. Django 1.5 is the start of Django's transition but many extensions such as South or the debug-toolbar are not p3-compatible.

Re:Updated Packages – Python 3.3 by swinglock on Friday April 05, 2013 @08:27AM (#5497911)
How I wish Flask would support Python 3. And gevent, Twisted, PIL, NumPy, PyPy and... can I have gevent and PyPy working together as well? Oh well, back to reality!
Re:Updated Packages – Python 3.3 by nknighthb on Friday April 05, 2013 @08:48AM (#5498029)
> PIL

https://pypi.python.org/pypi/Pillow/2.0.0

> NumPy

We're at almost three years now that people have been wrongly complaining about NumPy not being on Python 3. When do you think it will end?

http://www.mail-archive.com/[email protected]/msg26...

> PyPy

It's getting close.

http://morepypy.blogspot.com/2013/03/py3k-status-update-10.h...

Re:Updated Packages – Python 3.3 by viraptor on Friday April 05, 2013 @11:36AM (#5499030)
PIL barely works on python 2. You can't even install the official distribution inside a virtualenv without running into problems, so I don't expect them to sort anything out quickly.

Pillow works on py3 as others have already mentioned.

Re:Updated Packages – Python 3.3 by masklinn on Friday April 05, 2013 @08:38AM (#5497971)
Pillow supports Python 3 IIRC, and I think PIL can be built on Py3 as well/
Re:Updated Packages – Python 3.3 by untitaker_ on Friday April 05, 2013 @04:26PM (#5500841)
Flask porting is WIP.

For current status see https://gist.github.com/untitaker/5321447 (Werkzeug is the most significant Flask dependency)

Re:Updated Packages – Python 3.3 by Goranek on Friday April 05, 2013 @12:00PM (#5499201)
Flask is the only thing that keeps me away from python 3 :(
Re:Updated Packages – Python 3.3 by SiVal on Friday April 05, 2013 @02:12PM (#5500035)
Python3 is the only thing keeping me away from Flask.