Telethon VS google-api-python-client

1) telegram-upload is based on telethon lib which has default auth parameters. You need to fork and change device ID, name, language pack or else https://github.com/LonamiWebs/Telethon/issues/3194

Above is an example using telethon (https://github.com/LonamiWebs/Telethon), you can read the documentation for more details. also you can export the above message to some file instead of printing it, download media if the message is not a text but a media etc

Try Telethon https://github.com/LonamiWebs/Telethon/wiki/Retrieving-all-chat-members

I'm using Python3+ and working with the Telethon Library (https://docs.telethon.dev/)

Have tried to use both Telethon and Pyrogram but strangely enough I can't find any related API methods at all, there is no documentation and no code examples for such a simple task.

The issue can be found here: https://github.com/LonamiWebs/Telethon/issues/3264

Trio has a really nice aesthetic, although I personally found the concept of nurseries a bit weird at first.

However, I'd be interested to hear why one would use trio today instead of the more widely used (and official) built-in python async / asyncio stack?

Are there any major libraries using trio? (To see how a large, rather well-structured async codebase looks like, see Telethon, an async and complete MTProto implementation [1])

[1] https://github.com/LonamiWebs/Telethon

telethon

We uploaded one of Google’s sample Python scripts to Docuwriter to test some of the code documentation types, starting with General Documentation:

Google has documentation and 'getting started' resources for the GMail API, but the sample script implemented in their 'Python Quickstart' guide is using syntax that is documented separately in the Google API Python Client docs and GMail API docs.

First hit on google: https://github.com/googleapis/google-api-python-client/issues/1640

I'd recommend using one of the clients vs trying to assemble the requests yourself. The Python client is a good place to start.

The main functionality is handled by the Thermostat class. On creation it creates a service object using the Google Python API Client. That's used later to help build and execute API requests. At app exit the service object is closed.

At first, to simplify the procedure, I started with the credentials of an open source email client. I then used the tool mutt_oauth2.py (which is a streamlined version of google-api-python-client).

Based on my understanding, this is now only possible via through OAUTH2. After several failed attempts, it seems I found the official supported library, that is google-api-python-client.

API client for Python

Documentation. I've encountered several non documented requirements on various services that are just frustrating for no reason, until you find the correct answer on StackOverflow or GitHub. This can be a known issue that is unfixed for years, even though it's only a change in documentation. Again, Google's support teams keep claiming to file "internal bug reports" that go nowhere for years. Google is so busy always developing the "next big thing" that they forget to invest in their own existing tools that developers count on. See this example Issue from 2015 that was still gaining comments in 2021!