Skip to content
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.

Sign up for GitHub

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

docs: Refactor Hydrogram vs Pyrogram page #7

Merged
merged 1 commit into from
Jun 30, 2024
Merged

docs: Refactor Hydrogram vs Pyrogram page #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Update hydrogram-vs-pyrogram.rst
  • Loading branch information
@usernein
usernein authored Dec 9, 2023
commit 9adab12e5d3b7c3b6ec9ecbd53ccb8fb0752df60
32 changes: 21 additions & 11 deletions docs/source/hydrogram-vs-pyrogram.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,18 +7,28 @@ Introduction
This is a non-exhaustive list of differences between Hydrogram and Pyrogram.
It is updated periodically.

Changes
-------

- Support for the latest layer
- Support for threads/topics
- Improvements in IDE support by declaring ``__all__`` in files
- Mark optional parameters in methods as keyword-only, to avoid future breakage when adding new parameters
- Use of newer packaging technologies and standards, such as pyproject.toml
- Use of aiosqlite instead of sqlite3
- Open-source documentation
Key changes
-----------

- Support for the latest MTProto API layer with all new Telegram features
- Support for threads and topics in Telegram groups
- Support for multiple usernames.
- More active development
- Completely refactored, optimized and modernized codes (Using Ruff)
- Completely refactored, optimized and modernized codebase (utilizing Ruff)
- Open-source documentation
- Adopt modern packaging technologies and standards, such as pyproject.toml
- Use aiosqlite instead of sqlite3 for storage handling.
- Added the property `full_name` for User and Chat objects.
- Added the possibility to define a custom storage class

More technical changes
----------------------

- Declared the special variable `__all__` in all files so now we have a better IDE support.
- Specify optional parameters in methods as keyword-only to prevent potential breakage in the future when introducing new parameters.
- Migrated from setuptools to hatchling with rye.
- Transitioned from using `os.path` to utilizing `Pathlib`.
- Start utilizing towncrier to generate changelogs.

Fixes
-----
Expand Down
Loading