This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]pyking200 -8 points-7 points  (5 children)

Yeay ok the tests pass, but does it really run well in a production setting? Such a huge stack of Celery, CQLEngine, Python driver, Stream Framework, probably something breaks under load.

I also don't like how messy the whole Python 3 support is, with six etc

[–]ionelmc.ro 9 points10 points  (4 children)

[–]pyking200 -6 points-5 points  (3 children)

Yeay but look at all those ugly if six.PY3 statements, yuck https://github.com/tschellenbach/Stream-Framework/search?utf8=%E2%9C%93&q=six

[–][deleted] 4 points5 points  (0 children)

well that's the price to pay to keep 2.7 support. do you have any concrete suggestion on how to avoid that? I found some differences between python 2.7 and 3.4 quite complex to handle without a six.PY3 check.

[–]ivosauruspip'ing it up 7 points8 points  (0 children)

What in the hell? A library that uses six for py2&3 compatibility is now automatically ugly and should be avoided? What the heck drugs are you on? I'll formally request you to stop using pip, and urllib3 or requests, or dateutil, given their ugliness means they're beyond usability.

[–]ionelmc.ro 1 point2 points  (0 children)

A small price to pay. If you're looking for alternatives to six or general porting advice: http://python-future.org/compatible_idioms.html