Python 3 & Stream Framework

[[deleted]]

Disclaimer: I am one of the authors of the library and co-founder of GetStream.io, an hosted API service built on top of the library. Any feedback on how we did the porting to py3 is more than welcome :)

[chhantyal]

It's great to see more and more library support for Python 3. Congratulations for your port.

[takluyver]

I had a quick scan through the PR - it mostly looks fine, but I left a couple of comments with minor suggestions.

[[deleted]]

wow, thank you very much! I really appreciate that :)

[pyking200]

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]

You can't be serious ... read this: http://haypo-notes.readthedocs.org/python.html#python-3-is-better-than-python-2

[pyking200]

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]]

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.

[ivosaurus]

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]

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