Lib broken on Python 3.12

[christophehenry]

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]

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]

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]

Hi @David-Guillot,

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