As much as I love Python 3 and think it’s the future of Python, there are those who, for whatever reason, can’t seem to make the jump. So, if you, your clinic, or someone you know might not otherwise use pylinac let me know. It’s not impossible to convert, but it is of course “boring” work and I’d like to know some good would come of it.
I’m also willing to hear other reasons it should be backported.
Cheers,
James
I know there was talk of merging or collaborating with QATrack+ which is still using Python 2.7. However, as that project is moving to a newer version of Django, Python 3 will be supported.
Personally, I think sticking with Python 3 would be ok, as in my experience I have moved all my new projects to support both Py2/3 or exclusively Python 3. I am not targeting solely 2.7 anymore. I know it’s sometimes a hassle to write support for both using six, etc., but with continuous integration, it becomes easy to test compatibility.
Adit
FWIW I’m making one more release of QATrack+ supporting 2.6(!) and 2.7 and then will be supporting only 2.7 and 3.4+ after that. I’m dying to move to Py3 since I feel like I’m being left behind (my day job is all 2.7 as well)!
Honestly I think backporting to support 2.7 (and the extra maintenance burden) isn’t worth your time but I’ll be interested to hear from other people if they’re genuinely stuck on 2.7 for some reason. Afaik Py3 is available on all the major platforms though. Pylinac is young enough that I think it’s totally reasonable to only support Py3.
Randy