Developers have been pushing for some time that we drop support for legacy installations (Python2.7 and 32bit Windows) because it makes things harder to maintain.
My own sense is that some users want or need these, but it is getting harder to support them. Below are some of the reasons I know about, but chip in if you know more reasons (especially reasons that we need prolonged support).
On balance, my feeling is that we should soon drop support for legacy options soon (maybe in release 3.1.0), unless I hear arguments otherwise.
Known reasons to drop 32bit support
- I’m currently adding support for a new keyboard/USB lib and audio lib (same code as in psychtoolbox) that should dramatically improve timing of both. These libs only support 64bit Windows.
- The releases pages are getting rather confusing for users because of all the possible downloads for each version
Known reasons to drop Python2 support
- On Mac this has already essentially stopped being supported because it failed to compile recently and I haven’t worked out why
- On windows, I could technically build a 64bit Python3 release but it feels like that’s too many options
- We are also currently avoiding some recent nice features of newer Python versions (like the nicer formatted strings) because of supporting Python2 at the same time
Known reasons to keep dual support
- Currently the pyo audio lib is only 32bit windows, but this will probably change soon, and even if it doesn’t the new lib from psychtoolbox should make it redundant
- the iolabs button box definitely doesn’t have a Python3 so we’d be effectively dropping support for that, but it hasn’t been made for years and, as far as I can tell from google, everyone else dropped support long ago.