mir/pyrogram
2
0
Fork 0
mirror of https://github.com/pyrogram/pyrogram synced 2025-08-30 13:57:54 +00:00
Code Issues Releases Wiki Activity

Documentation fixes

Browse Source
This commit is contained in:
Dan 2022-04-24 11:56:07 +02:00
parent 822e09ae13
commit e80ffd275c
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/source/intro/quickstart.rst
View File

@ -50,7 +50,7 @@ Enjoy the API
That was just a quick overview. In the next few pages of the introduction, we'll take a much more in-depth look of what That was just a quick overview. In the next few pages of the introduction, we'll take a much more in-depth look of what
we have just done above. we have just done above.
If you are feeling eager to continue you can take a shortcut to :doc:`Invoking Methods <../start/invoking>` and come back If you are feeling eager to continue you can take a shortcut to :doc:`../start/invoking` and come back
later to learn some more details. later to learn some more details.
.. _community: https://t.me/Pyrogram .. _community: https://t.me/Pyrogram

4
docs/source/topics/storage-engines.rst
View File

@ -74,8 +74,8 @@ In case you want to use an in-memory storage, but also want to keep access to th
async with Client("my_account", in_memory=True) as app: async with Client("my_account", in_memory=True) as app:
print(await app.export_session_string()) print(await app.export_session_string())
...and save the resulting string. You can use this string as session name the next time you want to login ...and save the resulting string. You can use this string by passing it as Client argument the next time you want to
using the same session; the storage used will still be in-memory: login using the same session; the storage used will still be in-memory:
.. code-block:: python .. code-block:: python

2
docs/source/topics/synchronous.rst
View File

@ -1,7 +1,7 @@
Synchronous Usage Synchronous Usage
================= =================
Pyrogram is an asynchronous framework and as such it is subject to the asynchronous rules. It can, however, run in Pyrogram is an asynchronous framework and as such is subject to the asynchronous rules. It can, however, run in
synchronous mode (also known as non-asynchronous or sync/non-async for short). This mode exists mainly as a convenience synchronous mode (also known as non-asynchronous or sync/non-async for short). This mode exists mainly as a convenience
way for invoking methods without the need of ``async``/``await`` keywords and the extra boilerplate, but **it's not the way for invoking methods without the need of ``async``/``await`` keywords and the extra boilerplate, but **it's not the
intended way to use the framework**. intended way to use the framework**.