Skip to content
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

Open
christophehenry opened this issue Nov 27, 2023 · 3 comments
Open

Lib broken on Python 3.12 #4

christophehenry opened this issue Nov 27, 2023 · 3 comments

Comments

@christophehenry
Copy link

py_grist_api uses python-future which is broken on Python 3.12 because imp 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.

@ressy
Copy link

ressy commented Jan 13, 2024

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 standard_library.install_aliases() line, but I actually ended up just using requests package directly, since that was so simple for read-only access. (This repo feels like an example for how you might edit tables within a document over the API, but it doesn't seem to give you anything over using the API directly when it comes to other use cases.)

@David-Guillot
Copy link

David-Guillot commented Feb 27, 2025

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 uv)?

@berhalak
Copy link
Contributor

Hi @David-Guillot,

Yes it is opened to PRs any contribution is welcomed, we are actually planning to drop Python2 support entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants