we're absolutely not dropping support for 2.7, I'm sorry if the post gave you this impression. I don't know of any font apps that have made the jump to py3.
My point was that if someone wants to make an effort to port robofab to py3 (even if not many apps use it, someone might need it), it might be a better investment of time to port a new ufo3 ready project, not the old one.
On 28 sep. 2014, at 16:16, Adam Twardoch (List) <list...@twardoch.com
> I know that there's still a large user community and many projects sticking with Python 2.7 or trying to provide Py 2.7 + 3 compatibility. I myself haven't moved to Py 3, though perhaps it is time.
> I have no opinion myself, so what's your (& others') view:
> 1. Will RFab be Python 3-only? (I.e. dropping 2.7?)
> 2. Is Supol and RFont moving to Python 3?
> I would appreciate your insight and advice. For FontLab VI, we still can make a choice.
I think it is great the language developers want to clean things up and I will not second guess Guido's decisions. But at the same time, these changes cause so much code to break (and not just ours, but *all* scripts and systems *everyone* has built with robofab). Given the way python is used in the type community the long term advantages of py3 appear very distant and far removed from the very practical reasons why we need python in our tools in the first place.
"Why is my code broken?"
"Someone at Python central thinks it is better this way"
I think we probably have to start this discussion at some point (maybe Robothon?), but I am not at all sure about the outcome.
Superpol and RoboFont will move to UFO3 soon. Not Python3. Also 3, but a different 3.