Hacker News Reader

Comment by nemothekid | Hacker News Reader

Python 3.4 is out and unfortunately I still can't write Python3.

Is there anyone else who is still procrastinating moving their workflow to Python3?

This seems to me to be a watershed release. 3.4 is the point where we should move en masse to Python 3 for software development. At the same time, we should conciously abandon the default distro installed Python. Leave that for sysadmin tasks and sysadmin scripting, but for actual applications, install Python 3.4 in a virtualenv and use that going forward. By now you should only occasionally run into non-ported libraries and the details of how to port them are well enough known that you should be able to do the job yourself if you run into one that is important to you.

I have quite a few projects based on django, and these are still 2.7. There are still too many dependencies that are not python3 ready yet.

On the bright side since django 1.5 has been released with python 3 support, many related projects have moved to python3. Still not completely there yet, but moving forward.

Shameless plug: I've been testing little badges to tell which requirements are python 3 ready or not on requires.io (https://requires.io). Should be in production later today or tomorrow.

It's in production.

An example of project that could consider making the jump from Python2 to Python3: https://requires.io/github/canassa/sodexo-api/requirements/?...

I'm still on Python 2.7. I've built up a lot of infrastructure at work surrounding the "scipy stack".

Are there any major libraries that have not yet been ported to Python 3? I'd be interested to hear about others' experiences making the plunge.

https://python3wos.appspot.com has a list.

boto, fabric, Django (still 'experimental'), and various django packages are my blockers.

gevent also doesn't support python 3.x yet afaik. Can the asyncio stuff supercede it?

Twisted is the big one for me. The new async API introduced here sounds really great, but I have so much code built around Twisted that I don't know if it would be worth it for me to switch right away. Maybe I should write my next async project in Python 3.4 and start making a slow transition.

Not a library but I think mercurial currently still only works with Python 2.

All of the core Scipy Stack is ported, though if you use more specialist libraries, they may be missing. The main pain point in switching is with unicode, which is mostly not an issue for scientific/numberical code. Watch out, though, for integer division: now 1/2==0.5 (not 0).

> Watch out, though, for integer division: now 1/2==0.5 (not 0).

There go half of my bugs. ;-)

We started up new development a couple of weeks ago, With it was the choice of language, runtime and so on.

Python3 ended up being the target for server-side bits. Thanks to the fact that Pyramid now is Python3 capable.

We are still finding Python3 issues. Deploying Python3 on RHEL was a bit of a pain, most solved by RH Software Collections providing a python3.3 build, and the functioning state of virtualenv+pip.

Not being able to use mod_wsgi with python3 was a bit of a pain, ( fastcgi wrapper, to the rescue ) but solved.

I recently started moving my existing open source apps to Python 3, now that Django, NumPy and Matplotlib all support it. For new apps I write Python 3 from scratch. Perhaps I'm not getting advantage of all the new stuff, but one app is into serial I/O and I had to rewrite entirely the code dealing with strings, because I read bytes from the serial device.

Debian Jessie will default to Python 3 only I heard. I am starting to only install python3-* packages.

Yes, and I'm planning on moving to 3.4 when it ships with Ubuntu next year. Looks like all the rough edges have been sanded. ;)

What are your blockers?

Reply on news.ycombinator.com