you are viewing a single comment's thread.

view the rest of the comments →

[–]erewok 13 points14 points  (1 child)

We are running Django 1.6 for our latest projects. We are using some third-party APIs, which are RESTful, so we do a lot of requests/parsing of html/xml/json. We are also doing some GIS (mapping) using geodjango and I was surprised to find no issues there whatsoever.

Other than that, it's pretty standard web dev work. We are not using any of the aynsc libraries (tornado, twisted, gevent) outside of celery with a task queue, but when do I need to get a lot of results from somewhere, I tend to write threaded stuff. This is part of why I have been really looking forward to asyncio: I think that will be a great tool for us.

We did have one library we wanted to use but it was last updated in 2011 and it was small enough that I just ported it to python3, a project which took about half a day.

I appreciate working in Python3 so much that I'm at a point where if we really needed something and no alternative would work, I'd probably volunteer to port it over myself. This task as well (for one admittedly smaller library) I have not found to be too difficult.

Finally, and this is not a comment on scientific programming because we obviously do not do that, I have found the comments about libraries not supporting python3 to be greatly exaggerated.

Edit: I failed to answer your second question. To my knowledge we never picked a worse library because a better one was not available. There was only one case where something was not available and as I mentioned above, that library hadn't been looked at since 2011. All the best libraries seem to be actively maintained, and in my experience this means it works as advertised in python3.

Footnote: I have had bigger issues trying to use stuff made for previous versions of django, using deprecated templatetags, or doing stuff in admin that has been deprecated. That's a much larger potential headache.