News for hackers. Stuff that matters.
Re:Python 3.5.0 by rizwank on Sunday September 13, 2015 @03:05PM (#10212438)
Is Py3 ready for prime time? Do all the right libraries have support now?
Re:Python 3.5.0 by vikp on Sunday September 13, 2015 @03:09PM (#10212452)
Yes -- I write ~95% of my python code in 3, and scrapy is the only library I commonly use that doesn't support it. Here's a listing of package compatibility: http://py3readiness.org/.
Re:Python 3.5.0 by kodr on Sunday September 13, 2015 @03:17PM (#10212473)
Re:Python 3.5.0 by foob on Sunday September 13, 2015 @04:46PM (#10212743)
In most cases, yes. There are libraries that you might want to use that don't support it yet but the vast majority do. Personally, I'm anxiously waiting for Fabric 2 which has been pending for a long time. This is a good resource for figuring out whether the libraries you need are ready: http://py3readiness.org
Re:Python 3.5.0 by jay_kyburz on Sunday September 13, 2015 @04:44PM (#10212740)
Unfortunately I'm stuck on 2.7 until Google updates App Engine
Re:Python 3.5.0 by wyldfire on Sunday September 13, 2015 @11:00PM (#10213496)
Most of the time I find it pretty easy to make it compatible with both 2.7 and 3.4. Usually just a few "from __future__ import print_function" and a few other tips.

If your codebase is large, it can feel daunting, but it's not usually that bad.

Re:Python 3.5.0 by nickysielicki on Sunday September 13, 2015 @03:26PM (#10212490)
It's been ready for prime time for the past 3 years.
Re:Python 3.5.0 by nstart on Monday September 14, 2015 @12:12AM (#10213602)
Py3 has been prime time for a while now. Been using it full time since Py 3.3 for all my work and I haven't had any issues with it. There were some external libraries such as the library given by a twilio competitor that were incompatible, but easily fixed (almost exclusively, encoding issues).

Although, I still find myself running tests and cursing at the fact that I keep writing print "string" without the brackets :D