538f1e3972
- Pyrogram core is now fully asynchronous - Ditched Python 3.5, welcome 3.6 as minimum version. - Moved all types to pyrogram.types - Turned the Filters class into a module (filters) - Moved all filters to pyrogram.filters - Moved all handlers to pyrogram.handlers - Moved all emoji to pyrogram.emoji - Renamed pyrogram.api to pyrogram.raw - Clock is now synced with server's time - Telegram schema updated to Layer 117 - Greatly improved the TL compiler (proper type-constructor hierarchy) - Added "do not edit" warning in generated files - Crypto parts are executed in a thread pool to avoid blocking the event loop - idle() is now a separate function (it doesn't deal with Client instances) - Async storage, async filters and async progress callback (optional, can be sync too) - Added getpass back, for hidden password inputs
50 lines
1.3 KiB
ReStructuredText
50 lines
1.3 KiB
ReStructuredText
Quick Start
|
|
===========
|
|
|
|
The next few steps serve as a quick start for all new Pyrogrammers that want to see Pyrogram in action as fast as
|
|
possible. Let's go!
|
|
|
|
Get Pyrogram Real Fast
|
|
----------------------
|
|
|
|
1. Install Pyrogram with ``pip3 install -U pyrogram``.
|
|
|
|
2. Get your own Telegram API key from https://my.telegram.org/apps.
|
|
|
|
3. Open your best text editor and paste the following:
|
|
|
|
.. code-block:: python
|
|
|
|
from pyrogram import Client
|
|
|
|
api_id = 12345
|
|
api_hash = "0123456789abcdef0123456789abcdef"
|
|
|
|
with Client("my_account", api_id, api_hash) as app:
|
|
app.send_message("me", "Greetings from **Pyrogram**!")
|
|
|
|
4. Replace *api_id* and *api_hash* values with your own.
|
|
|
|
5. Save the file as ``pyro.py``.
|
|
|
|
6. Run the script with ``python3 pyro.py``
|
|
|
|
7. Follow the instructions on your terminal to login.
|
|
|
|
8. Watch Pyrogram send a message to yourself.
|
|
|
|
9. Join our `community`_.
|
|
|
|
10. Say, "hi!".
|
|
|
|
Enjoy the API
|
|
-------------
|
|
|
|
That was just a quick overview that barely scratched the surface!
|
|
In the next few pages of the introduction, we'll take a much more in-depth look of what we have just done above.
|
|
|
|
Feeling eager to continue? You can take a shortcut to :doc:`Calling Methods <../start/invoking>` and come back later to
|
|
learn some more details.
|
|
|
|
.. _community: https://t.me/Pyrogram
|