status of this repo vs py_grist_api2

[kdeden]

I have contributions to make to Grist's Python API client. Your organization owns two matching repos, this one and another called py_grist_api2.

Could you please specify which repo should be prioritized and update the documentation to direct contributers? Or are both abandoned?

[berhalak]

The py_grist_api2 was an experiment and an attempt to rewrite our "official" (but stale) python API. But it wasn't finished, it is just a proof of concept and it probably lacks some features.

Unfortunately we don't have enough time to contribute to those two client APIs, but it would be wonderful to see one of them completed or updated.

[kdeden]

Thanks for your reply. @berhalak .
I totally understand you cannot spare capacity to maintain these repos. But is there anyone available to merge my PRs and give feedback?
Some other questions -

• Do you have contributor guidelines?
• Can you provide guidance for locally setting up the CI and test tools in this repo? Specifically regarding updating the test fixtures to reflect current Grist database and API responses.
• Are you willing to give up support for Python 2.7?

[neopostmodern]

@berhalak
Both PRs are quite clean and small in scope – would it be possible to merge them, or as @kdeden suggested, outline what steps towards getting PRs merged could be?

[berhalak]

Hi, would you mind checking and giving a feedback on https://github.com/ricpol/pygrister (and a community post about that https://community.getgrist.com/t/pygrister-a-python-client-for-the-grist-api/5015/5). We are wondering whether we should start to recommend that library as an "offical"one.