The first thing I looked for on the Bokeh website was some sort of clear statement on the front page about it being Python 3. I don't have an immediate need for it, but if it's Python 3, I'll keep it in mind. If it's just that euphemistic "Python", it may as well be Cobol for all I'd care.
I thought I'd skim over these comments just in case someone asked the obvious question, and someone did. (Thank you.) And, yes, it is apparently Python 3 enough that we wouldn't need to use any Python 2 if we adopted it.
Very nice. Now I wish I DID need it, but maybe I'll do a side project of my own with it, just for fun. I'll be keeping it in mind in any case. I'll bet "Python 3" is mentioned somewhere on the site, but I didn't spot it right away. It might be worth making it a bit more prominent, since it is an important feature for those designing for the future.
good point: a quick search reveals that Py2.x is still in a lot of legacy code (dependencies -- the big one), so I always check first:
- https://python3wos.appspot.com/
- http://stackoverflow.com/questions/30751668/python-2-vs-pyth...
- http://hiltmon.com/blog/2014/01/04/python-its-a-trap/
- https://blog.newrelic.com/2014/01/21/python-3-adoption-web-a...
- http://www.randalolson.com/2015/01/30/python-usage-survey-20...
This is one of the first questions I ask, "is this code Python3 ready?", so I look at the install requirements first. Maybe I'm an edge case. A short cut might be just to say in big words, Python3 ready.
[0] For example this PIL fork, Pillow (python3) https://pillow.readthedocs.org/en/latest/installation.html