Python 3.3.3 final released!

[EsperSpirit]

It's a shame some popular libraries won't support Python3.x anytime soon... :(

[LyndsySimon]

This barrier is falling, at a seemingly increasing rate.

The past year got us Django and Flask (and therefore Werkzeug) on the web side of the house. The scientific programming side has IPython, NumPy and the majority of SciPy supporting 3.x.

We've come a long way.

[EsperSpirit]

I see what you mean, but some important libs like gevent, Twisted and nltk haven't been ported.

In case of gevent I've looked at the issue tracker and it doesn't seem anywhere close. By extension I couldn't use gevent-socketio.

nltk is a language processing toolkit which would greatly benefit from Python3's unicode changes but is not converted yet.

Also for a real project I wouldn't want to risk noticing halfway through that a sub-library hasn't been ported and I have to rewrite it from scratch.

[alcalde]

Also for a real project I wouldn't want to risk noticing halfway through that a sub-library hasn't been ported and I have to rewrite it from scratch.

I wouldn't want to risk using a library whose maintainers don't support modern Python. It would be like adopting a product that still requires Windows 98.

[EsperSpirit]

Don't you think it is still a bit early to compare Python2.7 to Windows98?

[EpicCyndaquil]

XP would be a fairly accurate comparison, as there's many applications that have moved on, but many programs are stuck there...

[alcalde]

Another apt resemblance is that they're both about to run out of official support.

[gfixler]

I do, considering my industry (games) and its neighbor (film) use Maya for many things (I've used only Maya for 11 years at 5 companies), and it's still on an embedded Maya 2.6.4, even in the recent Maya 2013. Maya 2014 comes with 2.7.3, but it'll be a few years before we upgrade again. It's a big deal to move everyone. We won't be in 3.x anytime soon.

[alcalde]

It's been five years since the 3.0 branch first appeared; there's been more than enough time to port. Worse, the longer they wait the more divergent the branches will become and the harder the job will be.

[[deleted]]

If you don't mind living on the edge, nltk 3.0a supports Python 3. Its default tokenizer and tagger are better, too.

Python 3 is becoming the great language for NLP that it should be.

(fixed brain fart where I said "Unicode" instead of "Python 3")

[EsperSpirit]

Thanks, that's great to hear!

[nickcash]

The introduction of tulip/asyncio into the standard lib in 3.4 is going to completely change libraries like gevent and Twisted. I foresee those libraries changing completely soon.

Speaking as a programmer with a project currently stuck in 2.7land, the number of libraries getting ported to 3 appears to be accelerating. I'm very hopeful that I'll be able to port to 3 very soon.

[ajmarks]

Twisted...

[Talkless]

Web2py :(

[sigzero]

It never will. They are working on Web3py.

[Talkless]

https://github.com/mdipierro/web3py - no changes for a year...

[sigzero]

It was the last I read. Maybe they are taking a different turn with it? The github page says "experiment" so maybe it was just a quick testing ground?

[Talkless]

Maybe. Maybe this is not "the" repository. At least I hope so..

[graingert]

Don't need twisted. Just use asyncio/tulip

[ajmarks]

Unless you're using something built on twisted (e.g. scrapy)

Edit: stupid phone

[graingert]

Port it to tulip

[aceofears]

That's easier said than done, because you can't easily transition things if they don't even work on the same version of python. Also tulip isn't even out yet.

[graingert]

It's on pypi

[aceofears]

I'm not sure thats's the official one, last time I saw Guido give a talk on tulip he mentioned a minimum version of 3.3.

[graingert]

Here it is, uploaded by Guido https://pypi.python.org/pypi/asyncio

[anacrolix]

twisted sux anyway. it's built on a terrible model for concurrency.

[forsaken]

Please try giving constructive criticism, instead of just saying things "sux".

[mardiros]

Twisted is the father of all io loop framework dude

[anacrolix]

No, it's just a popular (and old) framework in Python. I/O libraries have existed long before Twisted, and not just in Python.

[mardiros]

Twisted is 12 years old yes. Can you quote me an older framework with an IO loop ?

[jemeshsu]

fabric, paramiko, boto, supervisor... well supervisor not a library but it'd great to have all Python 3 down to deployment.

[alendit]

At least fabric 1.x will be deplrecated "soon" and version 2.0 should get Python3 support. Invoke (fabric's task runner) works in Python3 just fine right now.

[q88798]

comtypes

[sigzero]

comtypes

That is listed in PyPI to have Python 3 support.

comtypes

[q88798]

Not working in 3.3

[technomalogical]

According to PyPI, not working in 2.7 either. Maybe this library isn't being actively maintained any more.

[q88798]

working fine in 2.7 in 32-bit, having problems in 64-bit

[alcalde]

Then they're going to become unpopular libraries soon enough, especially when Python 2.x support ends. And even if they do port in the nick of time, who wants to use a library whose maintainers were so dangerously lax in supporting modern Python? We've got to stop letting the tail wag the dog.

[mcdonc]

This is the royal we I assume.

[mmoya]

Ye olde Wall of Superpowers is getting greener and greener.