Re:Key differences between Python 2.7.x and Python 3.x (2014)
by 52-6F-62 on Sunday May 07, 2017 @06:05PM
(#14287961)
I can't offer you any kind of solid case. My Python experience is admittedly limited. I've been working to get more into it lately.
Thanks for the resource.
Can I ask if you see any reason to not abandon Python 2 altogether when starting a new development project?
Re:Key differences between Python 2.7.x and Python 3.x (2014)
by cthalupa on Monday May 08, 2017 @03:33AM
(#14289886)
If you control the deployment environment, none that I can think of.
If not, and you need to deploy to RHEL/Cent 7, then maybe. They're still on 2.7, though software collections will let you install 3.x on either of them.
Re:Key differences between Python 2.7.x and Python 3.x (2014)
by 52-6F-62 on Monday May 08, 2017 @10:24AM
(#14291685)
Oh thanks for the tip. I work with CentOS regularly, but haven't worked on a Python project in that environment yet.
Re:Key differences between Python 2.7.x and Python 3.x (2014)
by convolvatron on Monday May 08, 2017 @12:38AM
(#14289300)
idk, two sound libraries, an image processing library.
i've moved some forward, its not that hard. still seems like a mess
This gets mentioned in every hacknews thread on this subject, but I honestly don't believe I've seen any that weren't either already updated to support Python 3, or didn't have alternatives that worked just as well.
https://python3wos.appspot.com/ has a list of the largest packages in pypi, and there's very few that aren't available in Python3. httplib2 is easily replaced by requests. Supervisor isn't a library, it's an application. Same with carbon and graphite-web. Basically the only things on that list are the mozilla libraries, but IIRC some of those are in progress of being ported anyway.
Twisted is one of the few I can think of that still isn't there, but most of the core APIs are there, as well as a lot of secondary stuff - half a year ago, more than 90% of the unit tests were passing on python3.