mir/pyrogram
2
0
Fork 0
mirror of https://github.com/pyrogram/pyrogram synced 2025-08-31 22:35:36 +00:00
Code Issues Releases Wiki Activity

Fix cross-reference links

Browse Source
This commit is contained in:
Dan
2019-05-13 18:04:44 +02:00
parent 29ac51f256
commit 0914654ba6
10 changed files with 38 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/source/topics/advanced-usage.rst
View File

@@ -125,12 +125,9 @@ For example, given the ID *123456789*, here's how Pyrogram can tell entities apa
So, every time you take a raw ID, make sure to translate it into the correct ID when you want to use it with an
high-level method.
.. _methods: ../pyrogram/Client.html#messages
.. _types: ../pyrogram/Types.html
.. _plenty of them: ../pyrogram/Client.html#messages
.. _raw functions: ../pyrogram/functions
.. _raw types: ../pyrogram/types
.. _methods: ../api/methods
.. _types: ../api/types
.. _plenty of them: ../api/methods
.. _raw functions: ../telegram/functions
.. _raw types: ../telegram/types
.. _Community: https://t.me/PyrogramChat

6
docs/source/topics/config-file.rst
View File

@@ -54,7 +54,7 @@ The ``[pyrogram]`` section contains your Telegram API credentials: *api_id* and
api_id = 12345
api_hash = 0123456789abcdef0123456789abcdef
`More info about API Key. <../start/Setup.html#configuration>`_
`More info about API Key. <../intro/setup#api-keys>`_
Proxy
^^^^^
@@ -70,7 +70,7 @@ The ``[proxy]`` section contains settings about your SOCKS5 proxy.
username = <your_username>
password = <your_password>
`More info about SOCKS5 Proxy. <SOCKS5Proxy.html>`_
`More info about SOCKS5 Proxy. <proxy>`_
Plugins
^^^^^^^
@@ -87,4 +87,4 @@ The ``[plugins]`` section contains settings about Smart Plugins.
exclude =
module fn2
`More info about Smart Plugins. <SmartPlugins.html>`_
`More info about Smart Plugins. <smart-plugins>`_

4
docs/source/topics/faq.rst
View File

@@ -11,7 +11,7 @@ What is Pyrogram?
-----------------
**Pyrogram** is an elegant, easy-to-use Telegram_ client library and framework written from the ground up in Python and
C. It enables you to easily create custom applications using both user and bot identities (bot API alternative) via the
C. It enables you to easily create custom applications for both user and bot identities (bot API alternative) via the
`MTProto API`_ with the Python programming language.
.. _Telegram: https://telegram.org
@@ -30,7 +30,7 @@ How old is Pyrogram?
Pyrogram was first released on December 12, 2017. The actual work on the framework began roughly three months prior the
initial public release on `GitHub`_.
.. _GitHub: <https://github.com/pyrogram/pyrogram>
.. _GitHub: https://github.com/pyrogram/pyrogram
Why do I need an API key for bots?
----------------------------------

4
docs/source/topics/more-on-updates.rst
View File

@@ -218,5 +218,5 @@ The output of both (equivalent) examples will be:
1
2
.. _`update handlers`: UpdateHandling.html
.. _`filters`: UsingFilters.html
.. _`update handlers`: ../start/updates
.. _`filters`: filters

4
docs/source/topics/session-settings.rst
View File

@@ -5,8 +5,8 @@ As you may probably know, Telegram allows users (and bots) having more than one
in the system at the same time.
Briefly explaining, sessions are simply new logins in your account. They can be reviewed in the settings of an official
app (or by invoking `GetAuthorizations <../functions/account/GetAuthorizations.html>`_ with Pyrogram). They store some
useful information such as the client who's using them and from which country and IP address.
app (or by invoking `GetAuthorizations <../telegram/functions/account/GetAuthorizations.html>`_ with Pyrogram). They
store some useful information such as the client who's using them and from which country and IP address.
.. figure:: https://i.imgur.com/lzGPCdZ.png
:width: 70%

4
docs/source/topics/smart-plugins.rst
View File

@@ -65,7 +65,7 @@ after importing your modules, like this:
app.run()
This is already nice and doesn't add *too much* boilerplate code, but things can get boring still; you have to
manually ``import``, manually :meth:`add_handler <pyrogram.Client.add_handler>` and manually instantiate each
manually ``import``, manually :meth:`add_handler() <pyrogram.Client.add_handler>` and manually instantiate each
:obj:`MessageHandler <pyrogram.MessageHandler>` object because **you can't use those cool decorators** for your
functions. So, what if you could? Smart Plugins solve this issue by taking care of handlers registration automatically.
@@ -156,7 +156,7 @@ found inside each module will be, instead, loaded in the order they are defined,
.. note::
Remember: there can be at most one handler, within a group, dealing with a specific update. Plugins with overlapping
filters included a second time will not work. Learn more at `More on Updates <MoreOnUpdates.html>`_.
filters included a second time will not work. Learn more at `More on Updates <more-on-updates>`_.
This default loading behaviour is usually enough, but sometimes you want to have more control on what to include (or
exclude) and in which exact order to load plugins. The way to do this is to make use of ``include`` and ``exclude``