Skip to content

/ pyrogram

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

Jump to bottom

Towards v1.0 #266

Closed
delivrance opened this issue Jun 30, 2019 · 2 comments
Closed

Towards v1.0 #266

delivrance opened this issue Jun 30, 2019 · 2 comments
Labels
enhancement
Milestone
v1

Comments

@delivrance
Copy link
Member

@delivrance delivrance commented Jun 30, 2019 •
edited

It's time for Pyrogram to head towards v1.0.0. Not only there are already a lot of features worth for a major version, but Pyrogram has also shown itself to be really stable when running. However, the overall API turns out to be changing quite often, mainly because of the many additions, but also because we sometimes realize there's a better way to do things.

One of the goal of the framework is to provide a complete access to the Telegram API, but also to make it easier to work with it. This issue will therefore keep a list of what should be changed for the better.

Everyone is welcome to comment and propose their ideas and opinions here
@delivrance
Copy link
Member Author

@delivrance delivrance commented Jun 30, 2019 •
edited

  • Filters: Each filter should work for all applicable updates and they should all live inside a dedicated sub-package: pyrogram.filters which you can import with from pyrogram import filters and use like this: filters.regex(...) & filters.outgoing.

  • Handlers: Just like filters, handlers should also live inside a dedicated sub-package to separate things in a nice manner: pyrogram.handlers which you can import with from pyrogram import handlers and use like this: handlers.MessageHandler(...)

  • Types: Yet again something like the first two proposals, but for types; move all Pyrogram types into pyrogram.types which you can then import by using from pyrogram.types import User, Message, Chat, ....

This list will be updated as soon as new enhancement ideas come. Feel free to discuss about pros and cons of each!
@delivrance delivrance pinned this issue Jun 30, 2019
@delivrance delivrance added this to the v1 milestone Apr 23, 2020
@delivrance delivrance changed the title Towards v1.0.0 Towards v1.0 Aug 22, 2020
@delivrance
Copy link
Member Author

@delivrance delivrance commented Aug 26, 2020

v1.0 has been released!
@delivrance delivrance closed this Aug 26, 2020
@delivrance delivrance unpinned this issue Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Milestone
v1
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@delivrance
You can’t perform that action at this time.