-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.16.0 does not work with Python 2.7 anymore #44
Comments
OK, we should remove Python 2 in the metadata then. |
I know Python 2 is EOL and we really shouldn't be putting any resources into supporting it. That being said, I know some scientific equipment runs only on really old computers and works only with really old software that can't be updated, so some users might not have a choice. If anyone can present a compelling argument to include Python 2 support then maybe we can figure out how to do that. |
Just for the record, I personally couldn't care less about Py2. Just incidentally figured that Py2 wasn't working anymore as an automated build of the pyxdf conda-forge package failed. |
Right, that's why pylsl should drop it any time soon. Reading the data back in isn't one of those infrastructure projects where some ancient program/library has to be kept. I don't have the stats, but I guess most of the postprocessing will run on conda so I'd argue Python 3.5 or whatever the second most recent Ubuntu LTS ships is old enough. |
Even if someone really needs to load XDF files on an ancient platform (which I doubt because this is part of data analysis and not recording), they can still use the old 1.15 release. |
* Remove Python 2 from setup.py Fixes #44. * Add changelog entry
Metadata in
setup.py
says it should be compatible with both Py2 and Py3:https://github.com/xdf-modules/xdf-python/blob/049aef3486040851f53ca710cee761c796b6835f/setup.py#L63-L64
The text was updated successfully, but these errors were encountered: