New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which is the Best Fork of Pyrogram? #1396
Comments
Has their own updated documentation page https://telegramplayground.github.io/pyrogram/ I have not migrated to that fork yet, but is the best I've find so far. |
Why? |
That's exactly the what's new that I'm looking for! Thanks a lot. |
That doesn't answer the question of how this fork is better than others |
I know, I just provided the features the fork provides which the person you asked might have found the best. |
Hello, cause of the bad error handling described in #1306, i have tested the fork of @KurimuzonAkuma. https://github.com/KurimuzonAkuma/pyrogram/releases/tag/v2.1.16 This version is awesome, i was not able to test the error handling yet, but the threading behaviour was improved a lot. It has a huge performance boost and maybe this will eliminate the telegram limits i faced in some circumstances. You can easily upgrade to this version with pip
|
@KurimuzonAkuma |
Everyone has their own way of looking at it |
Checklist
Description
Forgive me if it's rude to ask this question here.
Pyrogram is my favourite bot framework for Telegram, but sadly it seems to stop updating, as #1382 mentions.
Various features introduced in newer versions of Bot API are missing in Pyrogram comapred to other Python wrappers.
After doing a quick search I found some forks that are actively maintained:
I appreciate their work, but these projects' docs don't contain a section clarifying what's new comapred to the original Pyrogram (
v2.0.106
), like bug fixes, new / removed functions, etc.Could anyone recommend which is best (not confined to the forks above) with some reasons? Thank you.
✅ Resolved: Changes in this Fork from TelegramPlayGround / pyrogram
The text was updated successfully, but these errors were encountered: