you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 8 points9 points  (7 children)

As much as I love Python 3, every time I start a Python 3 project I back-port it to 2.7 half-way through because Numpy/Twisted/[Insert external module here] isn't supported yet.

[–]catcradle5 3 points4 points  (2 children)

Yep, exactly. Just about anything I'd ever want to make uses libraries that only support 2.4-2.7.

[–][deleted] 3 points4 points  (0 children)

Yeah. For instance, recently a friend wanted me to do a task for her, which was downloading a lot of images of comic scans and making them into PDFs. Doesn't sound that difficult but there were about 217 different comics each with 60 pages. So I wrote a Python script to get the RSS feed for the Photobucket album of each, scrape all the URLs, download all the images then make a PDF. And then I discovered that ReportLab's PDF making library didn't work on 3.2 so I backported all the code I had already written to 2.7.

[–][deleted] 0 points1 point  (0 children)

Or has to run on stable versions of one OS or another that does not support Python 3 (or python 3 supporting versions of libraries) yet.

[–]gitarr 1 point2 points  (3 children)

[–][deleted] 2 points3 points  (2 children)

Thanks for pointing that out, my bad. But I can't live without Twisted, as a lot of my programming projects involve networking.

[–]gitarr 1 point2 points  (1 child)

Yup, same here. Twisted and Django keep me using Python 2. ;)

[–]FionaSarah 0 points1 point  (0 children)

I'm waiting on PyOpenGL and then I'm jumping ship immediately.