pyrogram1
This is a fork of Pyrogram v1 (Last: v1.4.16) which installs the library with name pyrogram1 so that you can use both major versions at the same time.
- Install this only if you need both version. If you only need major version 1, use
pip install pyrogram==1.*. - Please install this before the latest
pyrogramversion so that dependencies, if conflicting, can be overwritten.
This isn't exactly the right way, but it is the only way. Also, dependencies may (and will in the future) create a problem!
Installation
PyPI
pip install pyrogram1
Usage
Just change pyrogram to pyrogram1 in your imports. For example:
from pyrogram1 import Client
If you are using both clients in same file:
from pyrogram1 import Client as Client1
Credits
Original Author - Dan
Original Repository - pyrogram
1 maintainer
Metadata
1 maintainer
Release files for pyrogram1 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyrogram1-0.1.0.tar.gz | 322.8 kB | Without provenance | Details |
Release files / pyrogram1-0.1.0.tar.gz
| Download URL | pyrogram1-0.1.0.tar.gz |
|---|---|
| Size | 322.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
56c3655e60822652cf062b3be339557ed3ebfc13dda493cc9211c03e5ea13bee
|
|
BLAKE2b-256 checksum How to use checksums |
759d7549e22326e3d8466206183d1a1c501f6f6b58c9ffa597324c2d635cf549
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Security for pyrogram1 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
