Fix some typos and add note about BotFather in migration guide (073b87b by Lonami)

Update to layer 148 and document new more errors (#3970) (fb43f63 by SpEcHiDe)

Fix get_dialogs could fail when count % chunk_size = 0 (2c85ffe by Lonami)

Sort updates preemptively (8ae75db by Lonami)

The StackOverflow question PyQt, Telethon. How to send a message on button click? prompted me to write a Wrapper to launch async tasks from threaded code. This is in my opinion one of the cleanest way in which you can combine threaded code with async code (a.k.a. Telethon).

Note that I still recommend you to avoid threaded code when possible, and use only async, but if you can't for some reason, this wrapper will setup and manage a new thread just for async code to run. Then you can use as many threads as you want, and communicate safely with the async code via a shared queue.

Version 1.26 (view new and changed raw API methods)

Bump to v1.26 and update layer to 149 (bd1ba3b by Lonami)

Set documentation language to en (ba7fc24 by Lonami)
Fix sending copies of a file message should ignore parse mode (4f51604 by Lonami)

Don't error when calling disconnect after logout (83f13da by Lonami)

Fix calls to disconnect after logout (4a6ef97 by Lonami)

Update documentation and list of known errors (b2925f8 by Lonami)

Given the amount of trolls having fun with the reactions here, I've toned them down a bit. If you had a legitimate reason to react with a poop emoji or middle finger, please message me privately argumenting why you think it's a bad idea to disable that reaction, and I may reconsider. If you're a troll though, I'll simply report you and go on with my life.

Change updates add_done_callback to discard tasks more reliably (5080715 by Lonami)

Introduce trace-level logs to MessageBox (c72c7b1 by Lonami)

Fix messagebox state trace was not logging the object (a8ce308 by Lonami)
Promote messagebox warnings to errors (59ffad0 by Lonami)
Add more debug traces to the messagebox (e750eb7 by Lonami)

Fix payment.py example (#4005) (061a84b by yumupdate)

Version 1.26.1 has been released which should fix PersistentTimestampEmptyError. Thanks to everyone who reported the issue.

The problem occured when a new channel was created and an update for "message read" arrived before "new message", which caused Telethon to initialize the state for the new channel as 0, which led to the error above. Telethon now knows why and when it happens, and correctly sets the initial state as 1 when this occurs (Telegram seems to be aware of this issue, as it sends the second update with a value of 2 instead of the expected 1).

Fix PERSISTENT_TIMESTAMP_EMPTY for new entries with pts 1, count 0 (6d2a5da by Lonami)
Bump to v1.26.1 (979e381 by Lonami)
Update to layer 150 (7288c99 by Lonami)

Update to layer 151 (2007c83 by Lonami)