-
Notifications
You must be signed in to change notification settings - Fork 5
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
Lib broken on Python 3.12 #4
Comments
I just ran into this now with Python 3.12. For what it's worth it seemed OK when I just blindly commented out those imports and the |
Hi there, Actually it goes beyond that: every Python version that is marked as supported by this lib has reach EOL for at least a year. The lib itself seems great, it's hosted under the official Grist org, it has no competitors (gristlabs/py_grist_api2 remained a WIP, ricpol/pygrister is not official), it has everything to succeed, but... new applications can't use it. @berhalak @dsagal is this project opened to a PR that would drastically modernize the lib (drop Python2 support, setup a CI that runs tests for a matrix of active Python versions, setup automated PyPI packaging, maybe even use |
Hi @David-Guillot, Yes it is opened to PRs any contribution is welcomed, we are actually planning to drop Python2 support entirely. |
py_grist_api
usespython-future
which is broken on Python 3.12 becauseimp
module was removed. Even though this issue was fixed a month and half ago, no release fix has been published yet.Is
python-future
still necessary? Support for Python 2.7 has ended nearly 3 years ago now and the oldest still supported Python version is 3.8.The text was updated successfully, but these errors were encountered: