Motion to centralize Python SDK documentation

TagoIO Getting Started
1

Hi everyone,

It has been relatively confusing to get started working with the TagoIO Python SDK as the documentation is fragmented.

When searching for SDK links in the forum posts about APIs (https://help.tago.io/portal/en/kb/articles/31-api-overview) we get linked to: https://py.sdk.tago.io/
When searching the web we get linked to: https://tago-sdk-python.readthedocs.io/en/latest/index.html

Both documentations seem to be valid but they both contain varying information and examples.
I found myself using deprecated properties etc which I didn’t know were deprecated because the documentation was showing them.
It would be much better and more fun to work with an SDK that is documented well and for which all the information is in one place!

Just my 2 cents :slight_smile:

Thanks!

2

Hi,

Thank you for reaching out. I understand that each documentation is specific to a different Python SDKs. It’s noted that the most recent Python SDK documentation is not up-to-date with the code. However, there are open pull requests aimed at updating the documentation, which are pending review by the internal team at TagoIO.

https://github.com/tago-io/sdk-python/pulls

It’s also important to mention that the Python SDK at TagoIO does not receive as much support as other SDKs. Therefore, it is recommended to use the JavaScript SDK, as it is more frequently updated and maintained.

https://www.npmjs.com/package/@tago-io/sdk

3

Hi Mateus,

Thanks for your response.

Good to see some progress is being made and what a shame to hear the Python SDK doesn’t receive as much support as the others as its so much more approachable. As long as the stuff I built keeps working I’m happy :))).

Br