Merge pull request #348 from python-telegram-bot/urllib3_fix_proxy_auth

Urllib3 fix proxy auth

.codeclimate.yml

@@ -0,0 +1,5 @@
+languages:
+  Python: true
+exclude_paths:
+- "telegram/emoji.py"
+- "tests/*"

.coveragerc

@@ -0,0 +1,5 @@
+[run]
+source = telegram
+
+[report]
+omit = tests/

.git-blame-ignore-revs

@@ -1,7 +0,0 @@
-# .git-blame-ignore-revs
-# Use locally as `git blame file.py --ignore-revs-file .git-blame-ignore-revs`
-# or configure git to always use it: `git config blame.ignoreRevsFile .git-blame-ignore-revs`
-# First migration to code style Black (#2122)
-264b2c9c72691c5937b80e84e061c52dd2d8861a
-# Use Black more extensively (#2972)
-950d9a0751d79b92d78ea44344ce3e3c5b3948f9

.github/CONTRIBUTING.rst

@@ -1,114 +1,93 @@
-=================
 How To Contribute
 =================
 
 Every open source project lives from the generous help by contributors that sacrifice their time and ``python-telegram-bot`` is no different. To make participation as pleasant as possible, this project adheres to the `Code of Conduct`_ by the Python Software Foundation.
 
 Setting things up
-=================
+-----------------
 
 1. Fork the ``python-telegram-bot`` repository to your GitHub account.
 
 2. Clone your forked repository of ``python-telegram-bot`` to your computer:
 
-   .. code-block:: bash
+   ``$ git clone https://github.com/<your username>/python-telegram-bot``
 
-      $ git clone https://github.com/<your username>/python-telegram-bot
-      $ cd python-telegram-bot
+   ``$ cd python-telegram-bot``
 
 3. Add a track to the original repository:
 
-   .. code-block:: bash
-
-      $ git remote add upstream https://github.com/python-telegram-bot/python-telegram-bot
+   ``$ git remote add upstream https://github.com/python-telegram-bot/python-telegram-bot``
 
 4. Install dependencies:
 
-   .. code-block:: bash
-
-      $ pip install -r requirements-dev-all.txt
+   ``$ pip install -r requirements.txt -r requirements-dev.txt``
 
 
 5. Install pre-commit hooks:
 
-   .. code-block:: bash
-
-      $ pre-commit install
+   ``$ pre-commit install``
 
 Finding something to do
-=======================
+-----------------------
 
 If you already know what you'd like to work on, you can skip this section.
 
 If you have an idea for something to do, first check if it's already been filed on the `issue tracker`_. If so, add a comment to the issue saying you'd like to work on it, and we'll help you get started! Otherwise, please file a new issue and assign yourself to it.
 
-Another great way to start contributing is by writing tests. Tests are really important because they help prevent developers from accidentally breaking existing code, allowing them to build cool things faster. If you're interested in helping out, let the development team know by posting to the `Telegram group`_, and we'll help you get started.
-
-That being said, we want to mention that we are very hesitant about adding new requirements to our projects. If you intend to do this, please state this in an issue and get a verification from one of the maintainers.
+Another great way to start contributing is by writing tests. Tests are really important because they help prevent developers from accidentally breaking existing code, allowing them to build cool things faster. If you're interested in helping out, let the development team know by posting to the `developers' mailing list`_, and we'll help you get started.
 
 Instructions for making a code change
-=====================================
+-------------------------------------
 
 The central development branch is ``master``, which should be clean and ready for release at any time. In general, all changes should be done as feature branches based off of ``master``.
 
-If you want to do solely documentation changes, base them and PR to the branch ``doc-fixes``. This branch also has its own `RTD build`_.
-
 Here's how to make a one-off code change.
 
 1. **Choose a descriptive branch name.** It should be lowercase, hyphen-separated, and a noun describing the change (so, ``fuzzy-rules``, but not ``implement-fuzzy-rules``). Also, it shouldn't start with ``hotfix`` or ``release``.
 
 2. **Create a new branch with this name, starting from** ``master``. In other words, run:
 
-   .. code-block:: bash
+   ``$ git fetch upstream``
 
-      $ git fetch upstream
-      $ git checkout master
-      $ git merge upstream/master
-      $ git checkout -b your-branch-name
+   ``$ git checkout master``
+
+   ``$ git merge upstream/master``
+
+   ``$ git checkout -b your-branch-name``
 
 3. **Make a commit to your feature branch**. Each commit should be self-contained and have a descriptive commit message that helps other developers understand why the changes were made.
-   We also have a check-list for PRs `below`_.
 
    - You can refer to relevant issues in the commit message by writing, e.g., "#105".
 
    - Your code should adhere to the `PEP 8 Style Guide`_, with the exception that we have a maximum line length of 99.
 
-   - Provide static typing with signature annotations. The documentation of `MyPy`_ will be a good start, the cheat sheet is `here`_. We also have some custom type aliases in ``telegram._utils.types``.
-
-   - Document your code. This step is pretty important to us, so it has its own `section`_.
-
-   - For consistency, please conform to `Google Python Style Guide`_ and `Google Python Style Docstrings`_.
+   - For consistency, please conform to `Google Python Style Guide`_ and `Google Python Style Docstrings`_. In addition, code should be formatted consistently with other code around it.
 
    - The following exceptions to the above (Google's) style guides applies:
 
-     - Documenting types of global variables and complex types of class members can be done using the Sphinx docstring convention.
+        - Documenting types of global variables and complex types of class members can be done using the Sphinx docstring convention.
 
-   -  In addition, PTB uses some formatting/styling and linting tools in the pre-commit setup. Some of those tools also have command line tools that can help to run these tools outside of the pre-commit step. If you'd like to leverage that, please have a look at the `pre-commit config file`_ for an overview of which tools (and which versions of them) are used. For example, we use `Black`_ for code formatting. Plugins for Black exist for some `popular editors`_. You can use those instead of manually formatting everything.
+   - Please ensure that the code you write is well-tested.
 
-   - Please ensure that the code you write is well-tested and that all automated tests still pass. We
-     have dedicated an `testing page`_ to help you with that.
-
-   - Don't break backward compatibility.
+   - Don’t break backward compatibility.
 
    - Add yourself to the AUTHORS.rst_ file in an alphabetical fashion.
 
-   - If you want run style & type checks before committing run
+   - Before making a commit ensure that all automated tests still pass:
 
-     .. code-block:: bash
+      ``$ make test``
 
-        $ pre-commit run -a
+   - To actually make the commit (this will trigger tests for yapf, lint and pep8 automatically):
 
-   - To actually make the commit (this will trigger tests style & type checks automatically):
+      ``$ git add your-file-changed.py``
 
-     .. code-block:: bash
+        - yapf may change code formatting, make sure to re-add them to your commit.
 
-        $ git add your-file-changed.py
+      ``$ git commit -a -m "your-commit-message-here"``
 
    - Finally, push it to your GitHub fork, run:
 
-     .. code-block:: bash
-
-      $ git push origin your-branch-name
+      ``$ git push origin your-branch-name``
 
 4. **When your feature is ready to merge, create a pull request.**
 
@@ -120,173 +99,88 @@ Here's how to make a one-off code change.
 
 5. **Address review comments until all reviewers give LGTM ('looks good to me').**
 
-   - When your reviewer has reviewed the code, you'll get a notification. You'll need to respond in two ways:
+   - When your reviewer has reviewed the code, you'll get an email. You'll need to respond in two ways:
 
-     - Make a new commit addressing the comments you agree with, and push it to the same branch. Ideally, the commit message would explain what the commit does (e.g. "Fix lint error"), but if there are lots of disparate review comments, it's fine to refer to the original commit message and add something like "(address review comments)".
+       - Make a new commit addressing the comments you agree with, and push it to the same branch. Ideally, the commit message would explain what the commit does (e.g. "Fix lint error"), but if there are lots of disparate review comments, it's fine to refer to the original commit message and add something like "(address review comments)".
 
-     - In order to keep the commit history intact, please avoid squashing or amending history and then force-pushing to the PR. Reviewers often want to look at individual commits.
-
-     - In addition, please reply to each comment. Each reply should be either "Done" or a response explaining why the corresponding suggestion wasn't implemented. All comments must be resolved before LGTM can be given.
+       - In addition, please reply to each comment. Each reply should be either "Done" or a response explaining why the corresponding suggestion wasn't implemented. All comments must be resolved before LGTM can be given.
 
    - Resolve any merge conflicts that arise. To resolve conflicts between 'your-branch-name' (in your fork) and 'master' (in the ``python-telegram-bot`` repository), run:
 
-     .. code-block:: bash
+      ``$ git checkout your-branch-name``
 
-        $ git checkout your-branch-name
-        $ git fetch upstream
-        $ git merge upstream/master
-        $ ...[fix the conflicts]...
-        $ ...[make sure the tests pass before committing]...
-        $ git commit -a
-        $ git push origin your-branch-name
+      ``$ git fetch upstream``
+
+      ``$ git merge upstream/master``
+
+      ``$ ...[fix the conflicts]...``
+
+      ``$ ...[make sure the tests pass before committing]...``
+
+      ``$ git commit -a``
+
+      ``$ git push origin your-branch-name``
 
    - At the end, the reviewer will merge the pull request.
 
 6. **Tidy up!** Delete the feature branch from both your local clone and the GitHub repository:
 
-   .. code-block:: bash
+   ``$ git branch -D your-branch-name``
 
-      $ git branch -D your-branch-name
-      $ git push origin --delete your-branch-name
+   ``$ git push origin --delete your-branch-name``
 
 7. **Celebrate.** Congratulations, you have contributed to ``python-telegram-bot``!
 
-Check-list for PRs
-------------------
-
-This checklist is a non-exhaustive reminder of things that should be done before a PR is merged, both for you as contributor and for the maintainers.
-Feel free to copy (parts of) the checklist to the PR description to remind you or the maintainers of open points or if you have questions on anything.
-
-- Added ``.. versionadded:: NEXT.VERSION``, ``.. versionchanged:: NEXT.VERSION``, ``.. deprecated:: NEXT.VERSION`` or ``.. versionremoved:: NEXT.VERSION`` to the docstrings for user facing changes (for methods/class descriptions, arguments and attributes)
-- Created new or adapted existing unit tests
-- Documented code changes according to the `CSI standard <https://standards.mousepawmedia.com/en/stable/csi.html>`__
-- Added myself alphabetically to ``AUTHORS.rst`` (optional)
-- Added new classes & modules to the docs and all suitable ``__all__`` s
-- Checked the `Stability Policy <https://docs.python-telegram-bot.org/stability_policy.html>`_ in case of deprecations or changes to documented behavior
-
-**If the PR contains API changes (otherwise, you can ignore this passage)**
-
-- Checked the Bot API specific sections of the `Stability Policy <https://docs.python-telegram-bot.org/stability_policy.html>`_
-- Created a PR to remove functionality deprecated in the previous Bot API release (`see here <https://docs.python-telegram-bot.org/en/stable/stability_policy.html#case-2>`_)
-
--  New classes:
-
-   - Added ``self._id_attrs`` and corresponding documentation
-   - ``__init__`` accepts ``api_kwargs`` as kw-only
-
--  Added new shortcuts:
-
-   - In :class:`~telegram.Chat` & :class:`~telegram.User` for all methods that accept ``chat/user_id``
-   - In :class:`~telegram.Message` for all methods that accept ``chat_id`` and ``message_id``
-   - For new :class:`~telegram.Message` shortcuts: Added ``quote`` argument if methods accepts ``reply_to_message_id``
-   - In :class:`~telegram.CallbackQuery` for all methods that accept either ``chat_id`` and ``message_id`` or ``inline_message_id``
-
--  If relevant:
-
-   - Added new constants at :mod:`telegram.constants` and shortcuts to them as class variables
-   - Link new and existing constants in docstrings instead of hard-coded numbers and strings
-   - Add new message types to :attr:`telegram.Message.effective_attachment`
-   - Added new handlers for new update types
-
-     - Add the handlers to the warning loop in the :class:`~telegram.ext.ConversationHandler`
-
-   - Added new filters for new message (sub)types
-   - Added or updated documentation for the changed class(es) and/or method(s)
-   - Added the new method(s) to ``_extbot.py``
-   - Added or updated ``bot_methods.rst``
-   - Updated the Bot API version number in all places: ``README.rst`` (including the badge) and ``telegram.constants.BOT_API_VERSION_INFO``
-   - Added logic for arbitrary callback data in :class:`telegram.ext.ExtBot` for new methods that either accept a ``reply_markup`` in some form or have a return type that is/contains :class:`~telegram.Message`
-
-Documenting
-===========
-
-The documentation of this project is separated in two sections: User facing and dev facing.
-
-User facing docs are hosted at `RTD`_. They are the main way the users of our library are supposed to get information about the objects. They don't care about the internals, they just want to know
-what they have to pass to make it work, what it actually does. You can/should provide examples for non obvious cases (like the Filter module), and notes/warnings.
-
-Dev facing, on the other side, is for the devs/maintainers of this project. These
-doc strings don't have a separate documentation site they generate, instead, they document the actual code.
-
-User facing documentation
--------------------------
-We use `sphinx`_ to generate static HTML docs. To build them, first make sure you're running Python 3.9 or above and have the required dependencies installed as explained above.
-Then, run the following from the PTB root directory:
-
-.. code-block:: bash
-
-   $ make -C docs html
-
-or, if you don't have ``make`` available (e.g. on Windows):
-
-.. code-block:: bash
-
-   $ sphinx-build docs/source docs/build/html
-
-Once the process terminates, you can view the built documentation by opening ``docs/build/html/index.html`` with a browser.
-
-- Add ``.. versionadded:: NEXT.VERSION``, ``.. versionchanged:: NEXT.VERSION`` or ``.. deprecated:: NEXT.VERSION`` to the associated documentation of your changes, depending on what kind of change you made. This only applies if the change you made is visible to an end user. The directives should be added to class/method descriptions if their general behaviour changed and to the description of all arguments & attributes that changed.
-
-Dev facing documentation
-------------------------
-We adhere to the `CSI`_ standard. This documentation is not fully implemented in the project, yet, but new code changes should comply with the `CSI` standard.
-The idea behind this is to make it very easy for you/a random maintainer or even a totally foreign person to drop anywhere into the code and more or less immediately understand what a particular line does. This will make it easier
-for new to make relevant changes if said lines don't do what they are supposed to.
-
-
-
 Style commandments
 ==================
 
-Assert comparison order
------------------------
+Specific commandments
+---------------------
 
-Assert statements should compare in **actual** == **expected** order.
-For example (assuming ``test_call`` is the thing being tested):
+- Avoid using "double quotes" where you can reasonably use 'single quotes'.
 
-.. code-block:: python
+AssertEqual argument order
+--------------------------
 
-    # GOOD
-    assert test_call() == 5
-
-    # BAD
-    assert 5 == test_call()
+assertEqual method's arguments should be in ('actual', 'expected') order.
 
 Properly calling callables
 --------------------------
 
 Methods, functions and classes can specify optional parameters (with default
 values) using Python's keyword arg syntax. When providing a value to such a
-callable we prefer that the call also uses keyword arg syntax. For example:
+callable we prefer that the call also uses keyword arg syntax. For example::
 
-.. code-block:: python
+    # GOOD
+    f(0, optional=True)
 
-   # GOOD
-   f(0, optional=True)
-
-   # BAD
-   f(0, True)
+    # BAD
+    f(0, True)
 
 This gives us the flexibility to re-order arguments and more importantly
 to add new required arguments. It's also more explicit and easier to read.
 
+Properly defining optional arguments
+------------------------------------
 
-.. _`Code of Conduct`: https://policies.python.org/python.org/code-of-conduct/
+It's always good to not initialize optional arguments at class creation, 
+instead use ``**kwargs`` to get them. It's well known Telegram API can 
+change without notice, in that case if a new argument is added it won't 
+break the API classes. For example::
+
+    # GOOD
+    def __init__(self, id, name, **kwargs):
+       self.last_name = kwargs.get('last_name', '')
+
+    # BAD
+    def __init__(self, id, name, last_name=''):
+       self.last_name = last_name
+
+
+.. _`Code of Conduct`: https://www.python.org/psf/codeofconduct/
 .. _`issue tracker`: https://github.com/python-telegram-bot/python-telegram-bot/issues
-.. _`Telegram group`: https://telegram.me/pythontelegrambotgroup
-.. _`PEP 8 Style Guide`: https://peps.python.org/pep-0008/
-.. _`sphinx`: https://www.sphinx-doc.org/en/master
-.. _`Google Python Style Guide`: https://google.github.io/styleguide/pyguide.html
-.. _`Google Python Style Docstrings`: https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html
+.. _`developers' mailing list`: mailto:devs@python-telegram-bot.org
+.. _`PEP 8 Style Guide`: https://www.python.org/dev/peps/pep-0008/
+.. _`Google Python Style Guide`: https://google-styleguide.googlecode.com/svn/trunk/pyguide.html
+.. _`Google Python Style Docstrings`: http://sphinx-doc.org/latest/ext/example_google.html
 .. _AUTHORS.rst: https://github.com/python-telegram-bot/python-telegram-bot/blob/master/AUTHORS.rst
-.. _`MyPy`: https://mypy.readthedocs.io/en/stable/index.html
-.. _`here`: https://mypy.readthedocs.io/en/stable/cheat_sheet_py3.html
-.. _`pre-commit config file`: https://github.com/python-telegram-bot/python-telegram-bot/blob/master/.pre-commit-config.yaml
-.. _`Black`: https://black.readthedocs.io/en/stable/index.html
-.. _`popular editors`: https://black.readthedocs.io/en/stable/integrations/editors.html
-.. _`RTD`: https://docs.python-telegram-bot.org/
-.. _`RTD build`: https://docs.python-telegram-bot.org/en/doc-fixes
-.. _`CSI`: https://standards.mousepawmedia.com/en/stable/csi.html
-.. _`section`: #documenting
-.. _`testing page`: https://github.com/python-telegram-bot/python-telegram-bot/blob/master/tests/README.rst
-.. _`below`: #check-list-for-prs

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,31 @@
+<!--
+Thanks for reporting issues of python-telegram-bot!
+To make it easier for us to help you please enter detailed information below.
+-->
+### Steps to reproduce
+1.
+
+2.
+
+3.
+
+### Expected behaviour
+Tell us what should happen
+
+### Actual behaviour
+Tell us what happens instead
+
+### Configuration
+**Operating System:**
+
+
+**Version of Python:**
+
+``$ python -V``
+
+**Version of python-telegram-bot:**
+
+``$ python -c 'import telegram; print(telegram.__version__)'``
+
+### Logs
+Insert logs here (if necessary)

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,76 +0,0 @@
-name: Bug Report
-description: Create a report to help us improve
-title: "[BUG]"
-labels: ["bug :bug:"]
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for reporting issues of python-telegram-bot!
-
-        Use this template to notify us if you found a bug.
-
-        To make it easier for us to help you please enter detailed information below.
-
-        Please note, we only support the latest version of python-telegram-bot and master branch. Please make sure to upgrade & recreate the issue on the latest version prior to opening an issue.
-      
-  - type: textarea
-    id: steps-to-reproduce
-    attributes:
-      label: Steps to Reproduce
-      value: |
-        1. 
-        2.
-        3.
-    validations:
-      required: true
-        
-  - type: textarea
-    id: expected-behaviour
-    attributes:
-      label: Expected behaviour
-      description: Tell us what should happen
-    validations:
-      required: true
-      
-  - type: textarea
-    id: actual-behaviour
-    attributes:
-      label: Actual behaviour
-      description: Tell us what happens instead
-    validations:
-      required: true
-      
-  - type: markdown
-    attributes:
-      value: "### Configuration"
-
-  - type: input
-    id: operating-system
-    attributes:
-      label: Operating System
-    validations: 
-      required: true
-
-  - type: textarea
-    id: versions
-    attributes:
-      label: Version of Python, python-telegram-bot & dependencies
-      description: Paste the output of `$ python -m telegram` here. This will be automatically formatted into code, so no need for backticks.
-      render: shell
-    validations: 
-      required: true
-      
-  - type: textarea
-    id: logs
-    attributes:
-      label: Relevant log output
-      description: Insert logs here (if necessary). This will be automatically formatted into code, so no need for backticks.
-      render: python
-
-  - type: textarea
-    id: additional-context
-    attributes:
-      label: Additional Context
-      description: You may provide any other additional context to the bug here.

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Telegram Group
-    url: https://telegram.me/pythontelegrambotgroup
-    about: Questions asked on the group usually get answered faster.
-  - name: GitHub Discussions
-    url: https://github.com/python-telegram-bot/python-telegram-bot/discussions
-    about: For getting answers to usage on GitHub, Discussions is even better than this bug tracker :)

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,37 +0,0 @@
-name: Feature Request
-description: Suggest an idea for this project
-title: "[FEATURE]"
-labels: ["enhancement"]
-
-body:
-  - type: textarea
-    id: related-problem
-    attributes:
-      label: "What kind of feature are you missing? Where do you notice a shortcoming of PTB?"
-      description: "A clear and concise description of what the problem is."
-      placeholder: "Example: I want to do X, but there is no way to do it."
-    validations:
-      required: true
-      
-  - type: textarea
-    id: solution
-    attributes:
-      label: "Describe the solution you'd like"
-      description: "A clear and concise description of what you want to happen."
-      placeholder: "Example: I think it would be nice if you would add feature Y so I can do X."
-    validations:
-      required: true
-        
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: "Describe alternatives you've considered"
-      description: "A clear and concise description of any alternative solutions or features you've considered."
-      placeholder: "Example: I considered Z to be able to do X, but that didn't work because..."
-      
-  - type: textarea
-    id: additional-context
-    attributes:
-      label: "Additional context"
-      description: "Add any other context or screenshots about the feature request here."
-      placeholder: "Example: Here's a photo of my cat!"

.github/ISSUE_TEMPLATE/question.yml

@@ -1,70 +0,0 @@
-name: Question
-description: Get help with errors or general questions
-title: "[QUESTION]"
-labels: ["question"]
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Hey there, you have a question? We are happy to answer. Please make sure no similar question was opened already.
-
-        To make it easier for us to help you, please read this [article](https://github.com/python-telegram-bot/python-telegram-bot/wiki/Ask-Right).
-
-        Please mind that there is also a users' [Telegram group](https://t.me/pythontelegrambotgroup) for questions about the library. Questions asked there might be answered quicker than here. Moreover, [GitHub Discussions](https://github.com/python-telegram-bot/python-telegram-bot/discussions) offer a slightly better format to discuss usage questions.
-        
-        If you have asked the same question elsewhere (e.g. the [Telegram group](https://t.me/pythontelegrambotgroup) or [StackOverflow](https://stackoverflow.com/questions/tagged/python-telegram-bot)), provide a link to that thread.
-
-  - type: textarea
-    id: issue-faced
-    attributes:
-      label: "Issue I am facing"
-      description: "Please describe the issue here in as much detail as possible"
-    validations:
-      required: true
-      
-  - type: textarea
-    id: traceback
-    attributes:
-      label: "Traceback to the issue"
-      description: "If you are facing a specific error message, please paste the traceback here. This will be automatically formatted into python code, so no need for backticks."
-      placeholder: |
-        Traceback (most recent call last):
-          File "/home/bot.py", line 1, in main
-            foo = bar()
-          ...
-        telegram.error.BadRequest: Traceback not found
-      render: python
-        
-  - type: textarea
-    id: related-code
-    attributes:
-      label: "Related part of your code"
-      description: "This will be automatically formatted into code (python), so no need for backticks."
-      placeholder: |
-        logging.basicConfig(
-            format="%(asctime)s - %(name)s - %(levelname)s - %(message)s", level=logging.INFO
-        )
-
-        logger = logging.getLogger(__name__)
-      render: python
-
-  - type: markdown
-    attributes:
-      value: "### Configuration"
-
-  - type: input
-    id: operating-system
-    attributes:
-      label: Operating System
-    validations: 
-      required: true
-      
-  - type: textarea
-    id: versions
-    attributes:
-      label: Version of Python, python-telegram-bot & dependencies
-      description: Paste the output of `$ python -m telegram` here. This will be automatically formatted into code, so no need for backticks.
-      render: shell
-    validations: 
-      required: true

.github/dependabot.yml

@@ -1,14 +0,0 @@
-version: 2
-updates:
-  - package-ecosystem: "pip"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-      day: "friday"
-
-  # Updates the dependencies of the GitHub Actions workflows
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    schedule:
-      interval: "monthly"
-      day: "friday"

.github/labeler.yml

@@ -1,9 +0,0 @@
-# Config file for workflows/labelling.yml
-
-version: 1
-
-labels:
-- label: "dependencies"
-  authors: ["dependabot[bot]", "pre-commit-ci[bot]"]
-- label: "code quality ✨"
-  authors: ["pre-commit-ci[bot]"]

.github/pull_request_template.md

@@ -1,6 +0,0 @@
-<!--
-Hey! You're PRing? Cool!
-Please be sure to check out our contribution guide (https://github.com/python-telegram-bot/python-telegram-bot/blob/master/.github/CONTRIBUTING.rst).
-Especially, please have a look at the check list for PRs (https://github.com/python-telegram-bot/python-telegram-bot/blob/master/.github/CONTRIBUTING.rst#check-list-for-prs). Feel free to copy (parts of) the checklist to the PR description to remind you or the maintainers of open points or if you have questions on anything.
--->
-

.github/workflows/dependabot-prs.yml

@@ -1,38 +0,0 @@
-name: Process Dependabot PRs
-
-on:
-  pull_request:
-    types: [opened, reopened]
-
-jobs:
-  process-dependabot-prs:
-    permissions:
-      pull-requests: read
-      contents: write
-
-    runs-on: ubuntu-latest
-    if: ${{ github.event.pull_request.user.login == 'dependabot[bot]' }}
-    steps:
-
-    - name: Fetch Dependabot metadata
-      id: dependabot-metadata
-      uses: dependabot/fetch-metadata@v2.1.0
-
-    - uses: actions/checkout@v4
-      with:
-        ref: ${{ github.event.pull_request.head.ref }}
-
-    - name: Update Version Number in Other Files
-      uses: jacobtomlinson/gha-find-replace@v3
-      with:
-        find: ${{ steps.dependabot-metadata.outputs.previous-version }}
-        replace: ${{ steps.dependabot-metadata.outputs.new-version }}
-        regex: false
-        exclude: CHANGES.rst
-
-    - name: Commit & Push Changes to PR
-      uses: EndBug/add-and-commit@v9.1.4
-      with:
-        message: 'Update version number in other files'
-        committer_name: GitHub Actions
-        committer_email: 41898282+github-actions[bot]@users.noreply.github.com

.github/workflows/docs-linkcheck.yml

@@ -1,27 +0,0 @@
-name: Check Links in Documentation
-on:
-  schedule:
-    # First day of month at 05:46 in every 2nd month
-    - cron: '46 5 1 */2 *'
-
-jobs:
-  test-sphinx-build:
-    name: test-sphinx-linkcheck
-    runs-on: ${{matrix.os}}
-    strategy:
-      matrix:
-        python-version: [3.9]
-        os: [ubuntu-latest]
-      fail-fast: False
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v5
-        with:
-          python-version: ${{ matrix.python-version }}
-      - name: Install dependencies
-        run: |
-          python -W ignore -m pip install --upgrade pip
-          python -W ignore -m pip install -r requirements-dev-all.txt
-      - name: Check Links
-        run: sphinx-build docs/source docs/build/html -W --keep-going -j auto -b linkcheck

.github/workflows/docs.yml

@@ -1,46 +0,0 @@
-name: Test Documentation Build
-on:
-  pull_request:
-    paths:
-      - telegram/**
-      - docs/**
-  push:
-    branches:
-      - master
-
-jobs:
-  test-sphinx-build:
-    name: test-sphinx-build
-    runs-on: ${{matrix.os}}
-    strategy:
-      matrix:
-        python-version: [3.9]
-        os: [ubuntu-latest]
-      fail-fast: False
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v5
-        with:
-          python-version: ${{ matrix.python-version }}
-          cache: 'pip'
-          cache-dependency-path: '**/requirements*.txt'
-      - name: Install dependencies
-        run: |
-          python -W ignore -m pip install --upgrade pip
-          python -W ignore -m pip install -r requirements-dev-all.txt
-      - name: Test autogeneration of admonitions
-        run: pytest -v --tb=short tests/docs/admonition_inserter.py
-      - name: Build docs
-        run: sphinx-build docs/source docs/build/html -W --keep-going -j auto
-      - name: Upload docs
-        uses: actions/upload-artifact@v4
-        with:
-          name: HTML Docs
-          retention-days: 7
-          path: |
-            # Exclude the .doctrees folder and .buildinfo file from the artifact
-            # since they are not needed and add to the size
-            docs/build/html/*
-            !docs/build/html/.doctrees
-            !docs/build/html/.buildinfo

.github/workflows/labelling.yml

@@ -1,17 +0,0 @@
-name: PR Labeler
-
-on:
-  pull_request:
-    types: [opened]
-
-jobs:
-  pre-commit-ci:
-    permissions:
-      contents: read # for srvaroa/labeler to read config file
-      pull-requests: write # for srvaroa/labeler to add labels in PR
-    runs-on: ubuntu-latest
-    steps:
-    - uses: srvaroa/labeler@v1.10.1
-      # Config file at .github/labeler.yml
-      env:
-        GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/lock.yml

@@ -1,19 +0,0 @@
-name: 'Lock Closed Threads'
-
-on:
-  schedule:
-    - cron: '8 4 * * *'
-
-jobs:
-  lock:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: dessant/lock-threads@v5.0.1
-        with:
-          github-token: ${{ github.token }}
-          issue-inactive-days: '7'
-          issue-lock-reason: ''
-          pr-inactive-days: '7'
-          pr-lock-reason: ''
-          # Don't lock Discussions
-          process-only: 'issues, prs'

.github/workflows/release_pypi.yml

@@ -1,204 +0,0 @@
-name: Publish to PyPI
-
-on:
-  # Run on any tag
-  push:
-    tags:
-      - '**'
-  # manually trigger the workflow - for testing only
-  workflow_dispatch:
-
-jobs:
-  build:
-    name: Build Distribution
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: "3.x"
-      - name: Install pypa/build
-        run: >-
-          python3 -m pip install build --user
-      - name: Build a binary wheel and a source tarball
-        run: python3 -m build
-      - name: Store the distribution packages
-        uses: actions/upload-artifact@v4
-        with:
-          name: python-package-distributions
-          path: dist/
-
-  publish-to-pypi:
-    name: Publish to PyPI
-    # only publish to PyPI on tag pushes
-    if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags')
-    needs:
-      - build
-    runs-on: ubuntu-latest
-    environment:
-      name: release_pypi
-      url: https://pypi.org/p/python-telegram-bot
-    permissions:
-      id-token: write  # IMPORTANT: mandatory for trusted publishing
-
-    steps:
-      - name: Download all the dists
-        uses: actions/download-artifact@v4
-        with:
-          name: python-package-distributions
-          path: dist/
-      - name: Publish to PyPI
-        uses: pypa/gh-action-pypi-publish@release/v1
-
-  publish-to-test-pypi:
-    name: Publish to Test PyPI
-    needs:
-      - build
-    runs-on: ubuntu-latest
-    environment:
-      name: release_test_pypi
-      url: https://test.pypi.org/p/python-telegram-bot
-    permissions:
-      id-token: write  # IMPORTANT: mandatory for trusted publishing
-
-    steps:
-      - name: Download all the dists
-        uses: actions/download-artifact@v4
-        with:
-          name: python-package-distributions
-          path: dist/
-      - name: Publish to Test PyPI
-        uses: pypa/gh-action-pypi-publish@release/v1
-        with:
-          repository-url: https://test.pypi.org/legacy/
-
-  compute-signatures:
-    name: Compute SHA1 Sums and Sign with Sigstore
-    runs-on: ubuntu-latest
-    needs:
-      - publish-to-pypi
-      - publish-to-test-pypi
-    # run if either of the publishing jobs ran successfully
-    # see also:
-    # https://github.com/actions/runner/issues/491#issuecomment-850884422
-    if: |
-      always() && (
-        (needs.publish-to-pypi.result == 'success') ||
-        (needs.publish-to-test-pypi.result == 'success')
-      )
-
-    permissions:
-      id-token: write  # IMPORTANT: mandatory for sigstore
-
-    steps:
-      - name: Download all the dists
-        uses: actions/download-artifact@v4
-        with:
-          name: python-package-distributions
-          path: dist/
-      - name: Compute SHA1 Sums
-        run: |
-          # Compute SHA1 sum of the distribution packages and save it to a file with the same name,
-          # but with .sha1 extension
-          for file in dist/*; do
-              sha1sum $file > $file.sha1
-          done
-      - name: Sign the dists with Sigstore
-        uses: sigstore/gh-action-sigstore-python@v2.1.1
-        with:
-          inputs: >-
-            ./dist/*.tar.gz
-            ./dist/*.whl
-      - name: Store the distribution packages and signatures
-        uses: actions/upload-artifact@v4
-        with:
-          name: python-package-distributions-and-signatures
-          path: dist/
-
-  github-release:
-    name: Upload to GitHub Release
-    needs:
-      - publish-to-pypi
-      - compute-signatures
-    if: |
-      always() && (
-        (needs.publish-to-pypi.result == 'success') &&
-        (needs.compute-signatures.result == 'success')
-      )
-
-    runs-on: ubuntu-latest
-
-    permissions:
-      contents: write  # IMPORTANT: mandatory for making GitHub Releases
-
-    steps:
-      - name: Download all the dists
-        uses: actions/download-artifact@v4
-        with:
-          name: python-package-distributions-and-signatures
-          path: dist/
-      - name: Create GitHub Release
-        env:
-          GITHUB_TOKEN: ${{ github.token }}
-        # Create a GitHub Release for this tag. The description can be changed later, as for now
-        # we don't define it through this workflow.
-        run: >-
-          gh release create
-          '${{ github.ref_name }}'
-          --repo '${{ github.repository }}'
-          --generate-notes
-      - name: Upload artifact signatures to GitHub Release
-        env:
-          GITHUB_TOKEN: ${{ github.token }}
-        # Upload to GitHub Release using the `gh` CLI.
-        # `dist/` contains the built packages, and the
-        # sigstore-produced signatures and certificates.
-        run: >-
-          gh release upload
-          '${{ github.ref_name }}' dist/**
-          --repo '${{ github.repository }}'
-
-  github-test-release:
-    name: Upload to GitHub Release Draft
-    needs:
-      - publish-to-test-pypi
-      - compute-signatures
-    if: |
-      always() && (
-        (needs.publish-to-test-pypi.result == 'success') &&
-        (needs.compute-signatures.result == 'success')
-      )
-    runs-on: ubuntu-latest
-
-    permissions:
-      contents: write  # IMPORTANT: mandatory for making GitHub Releases
-
-    steps:
-      - name: Download all the dists
-        uses: actions/download-artifact@v4
-        with:
-          name: python-package-distributions-and-signatures
-          path: dist/
-      - name: Create GitHub Release
-        env:
-          GITHUB_TOKEN: ${{ github.token }}
-        # Create a GitHub Release *draft*. The description can be changed later, as for now
-        # we don't define it through this workflow.
-        run: >-
-          gh release create
-          '${{ github.ref_name }}'
-          --repo '${{ github.repository }}'
-          --generate-notes
-          --draft
-      - name: Upload artifact signatures to GitHub Release
-        env:
-          GITHUB_TOKEN: ${{ github.token }}
-        # Upload to GitHub Release using the `gh` CLI.
-        # `dist/` contains the built packages, and the
-        # sigstore-produced signatures and certificates.
-        run: >-
-          gh release upload
-          '${{ github.ref_name }}' dist/**
-          --repo '${{ github.repository }}'

.github/workflows/stale.yml

@@ -1,19 +0,0 @@
-name: 'Mark & close stale questions'
-on:
-  schedule:
-    - cron: '42 2 * * *'
-
-jobs:
-  stale:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/stale@v9
-        with:
-          # PRs never get stale
-          days-before-stale: 3
-          days-before-close: 2
-          days-before-pr-stale: -1
-          stale-issue-label: 'stale'
-          only-labels: 'question'
-          stale-issue-message: ''
-          close-issue-message: 'This issue has been automatically closed due to inactivity. Feel free to comment in order to reopen or ask again in our Telegram support group at https://t.me/pythontelegrambotgroup.'

.github/workflows/test_official.yml

@@ -1,47 +0,0 @@
-name: Bot API Tests
-on:
-  pull_request:
-    paths:
-      - telegram/**
-      - tests/**
-  push:
-    branches:
-      - master
-  schedule:
-    # Run monday and friday morning at 03:07 - odd time to spread load on GitHub Actions
-    - cron: '7 3 * * 1,5'
-
-jobs:
-  check-conformity:
-    name: check-conformity
-    runs-on: ${{matrix.os}}
-    strategy:
-      matrix:
-        python-version: [3.11]
-        os: [ubuntu-latest]
-      fail-fast: False
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Python ${{ matrix.python-version }}
-        uses: actions/setup-python@v5
-        with:
-          python-version: ${{ matrix.python-version }}
-      - name: Install dependencies
-        run: |
-          python -W ignore -m pip install --upgrade pip
-          python -W ignore -m pip install .[all]
-          python -W ignore -m pip install -r requirements-unit-tests.txt
-      - name: Compare to official api
-        run: |
-          pytest -v tests/test_official/test_official.py --junit-xml=.test_report_official.xml
-          exit $?
-        env:
-          TEST_OFFICIAL: "true"
-        shell: bash --noprofile --norc {0}
-
-      - name: Test Summary
-        id: test_summary
-        uses: test-summary/action@v2.3
-        if: always()  # always run, even if tests fail
-        with:
-          paths: .test_report_official.xml

.github/workflows/type_completeness.yml

@@ -1,21 +0,0 @@
-name: Check Type Completeness
-on:
-  pull_request:
-    paths:
-      - telegram/**
-      - pyproject.toml
-      - .github/workflows/type_completeness.yml
-  push:
-    branches:
-      - master
-
-jobs:
-  test-type-completeness:
-    name:   test-type-completeness
-    runs-on: ubuntu-latest
-    steps:
-      - uses: Bibo-Joshi/pyright-type-completeness@1.0.0
-        with:
-          package-name: telegram
-          python-version: 3.12
-          pyright-version: ~=1.1.367

.gitignore

@@ -23,11 +23,6 @@ var/
 .installed.cfg
 *.egg
 .env
-.pybuild
-debian/tmp
-debian/python3-telegram
-debian/python3-telegram-doc
-debian/.debhelper
 
 # PyInstaller
 #  Usually these files are written by a python script from a template
@@ -45,14 +40,10 @@ htmlcov/
 .coverage
 .coverage.*
 .cache
-.pytest_cache
-.mypy_cache
 nosetests.xml
 coverage.xml
 *,cover
 .coveralls.yml
-.testmondata
-.testmondata-journal
 
 # Translations
 *.mo
@@ -71,27 +62,9 @@ target/
 # Sublime Text 2
 *.sublime*
 
-# VS Code
-.vscode
-
 # unitests files
-game.gif
 telegram.mp3
 telegram.mp4
-telegram2.mp4
 telegram.ogg
 telegram.png
 telegram.webp
-telegram.jpg
-
-# original files from merges
-*.orig
-
-# Exclude .exrc file for Vim
-.exrc
-
-# virtual env
-venv*
-
-# environment manager:
-.mise.toml

.pre-commit-config.yaml

@@ -1,83 +1,18 @@
-# Make sure that the additional_dependencies here match pyproject.toml
-
-ci:
-    autofix_prs: false
-    autoupdate_schedule: quarterly
-    autoupdate_commit_msg: 'Bump `pre-commit` Hooks to Latest Versions'
-
-repos:
--   repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: 'v0.5.0'
+-   repo: git://github.com/pre-commit/mirrors-yapf
+    sha: 316b795b2f32cbe80047aff7e842b72368d5a2c1
     hooks:
-    -   id: ruff
-        name: ruff
-        additional_dependencies:
-          - httpx~=0.27
-          - tornado~=6.4
-          - APScheduler~=3.10.4
-          - cachetools~=5.3.3
-          - aiolimiter~=1.1.0
--   repo: https://github.com/psf/black-pre-commit-mirror
-    rev: 24.4.2
-    hooks:
-    -   id: black
-        args:
-        - --diff
-        - --check
--   repo: https://github.com/PyCQA/flake8
-    rev: 7.1.0
+    -   id: yapf
+        files: ^(telegram|tests)/.*\.py$
+-   repo: git://github.com/pre-commit/pre-commit-hooks
+    sha: 6dfcb89af3c9b4d172cc2e5a8a2fa0f54615a338
     hooks:
     -   id: flake8
--   repo: https://github.com/PyCQA/pylint
-    rev: v3.2.4
+        files: ^telegram/.*\.py$
+-   repo: git://github.com/pre-commit/mirrors-pylint
+    sha: 4de6c8dfadef1a271a814561ce05b8bc1c446d22
     hooks:
     -   id: pylint
-        files: ^(?!(tests|docs)).*\.py$
-        additional_dependencies:
-          - httpx~=0.27
-          - tornado~=6.4
-          - APScheduler~=3.10.4
-          - cachetools~=5.3.3
-          - aiolimiter~=1.1.0
-          - . # this basically does `pip install -e .`
--   repo: https://github.com/pre-commit/mirrors-mypy
-    rev: v1.10.1
-    hooks:
-    -   id: mypy
-        name: mypy-ptb
-        files: ^(?!(tests|examples|docs)).*\.py$
-        additional_dependencies:
-          - types-pytz
-          - types-cryptography
-          - types-cachetools
-          - httpx~=0.27
-          - tornado~=6.4
-          - APScheduler~=3.10.4
-          - cachetools~=5.3.3
-          - aiolimiter~=1.1.0
-          - . # this basically does `pip install -e .`
-    - id: mypy
-      name: mypy-examples
-      files: ^examples/.*\.py$
-      args:
-        - --no-strict-optional
-        - --follow-imports=silent
-      additional_dependencies:
-        - tornado~=6.4
-        - APScheduler~=3.10.4
-        - cachetools~=5.3.3
-        - . # this basically does `pip install -e .`
--   repo: https://github.com/asottile/pyupgrade
-    rev: v3.16.0
-    hooks:
-    -   id: pyupgrade
+        files: ^telegram/.*\.py$
         args:
-          - --py38-plus
--   repo: https://github.com/pycqa/isort
-    rev: 5.13.2
-    hooks:
-    -   id: isort
-        name: isort
-        args:
-        - --diff
-        - --check
+        - --errors-only
+        - --disable=no-name-in-module,import-error

.readthedocs.yml

@@ -1,62 +0,0 @@
-# .readthedocs.yaml
-# Read the Docs configuration file
-# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
-
-# Required
-version: 2
-
-# Build documentation in the docs/ directory with Sphinx
-sphinx:
-  configuration: docs/source/conf.py
-
-# Optionally build your docs in additional formats such as PDF
-formats:
-  - pdf
-
-# Optionally set the version of Python and requirements required to build your docs
-python:
-  install:
-    - method: pip
-      path: .
-    - requirements: docs/requirements-docs.txt
-
-build:
-  os: ubuntu-22.04
-  tools:
-    python: "3"  # latest stable cpython version
-  jobs:
-    post_build:
-      # Based on https://github.com/readthedocs/readthedocs.org/issues/3242#issuecomment-1410321534
-      # This provides a HTML zip file for download, with the same structure as the hosted website
-      - mkdir --parents $READTHEDOCS_OUTPUT/htmlzip
-      - cp --recursive $READTHEDOCS_OUTPUT/html $READTHEDOCS_OUTPUT/$READTHEDOCS_PROJECT
-      # Hide the "other versions" dropdown. This is a workaround for those versions being shown,
-      # but not being accessible, as they are not built. Also, they hide the actual sidebar menu
-      # that is relevant only on ReadTheDocs.
-      - echo "#furo-readthedocs-versions{display:none}" >> $READTHEDOCS_OUTPUT/$READTHEDOCS_PROJECT/_static/styles/furo-extensions.css
-      - cd $READTHEDOCS_OUTPUT ; zip --recurse-path --symlinks htmlzip/$READTHEDOCS_PROJECT.zip $READTHEDOCS_PROJECT
-
-search:
-  ranking: # bump up rank of commonly searched pages: (default: 0, values range from -10 to 10)
-    telegram.bot.html: 7
-    telegram.message.html: 3
-    telegram.update.html: 3
-    telegram.user.html: 2
-    telegram.chat.html: 2
-    telegram.ext.application.html: 3
-    telegram.ext.filters.html: 3
-    telegram.ext.callbackcontext.html: 2
-    telegram.ext.inlinekeyboardbutton.html: 1
-
-    telegram.passport*.html: -7
-
-  ignore:
-    - changelog.html
-    - coc.html
-    - bot_methods.html#
-    - bot_methods.html
-    # Defaults
-    - search.html
-    - search/index.html
-    - 404.html
-    - 404/index.html'

.travis.yml

@@ -0,0 +1,18 @@
+language: python
+python:
+  - "2.6"
+  - "2.7"
+  - "3.3"
+  - "3.4"
+  - "3.5"
+  - "pypy"
+  - "pypy3"
+install:
+  - pip install coveralls
+  - pip install -r requirements.txt
+  - pip install -r requirements-dev.txt
+script:
+  - nosetests -v --with-flaky --no-flaky-report --with-coverage --cover-package=telegram/
+  - 'if [ $TRAVIS_PYTHON_VERSION != 2.6 ] && [ $TRAVIS_PYTHON_VERSION != 3.3 ] && [ $TRAVIS_PYTHON_VERSION != pypy3 ]; then pre-commit run --all-files; fi'
+after_success:
+  coveralls

AUTHORS.rst

@@ -1,134 +1,30 @@
 Credits
 =======
 
-``python-telegram-bot`` was originally created by
-`Leandro Toledo <https://github.com/leandrotoledo>`_.
-The current development team includes
-
-- `Hinrich Mahler <https://github.com/Bibo-Joshi>`_ (maintainer)
-- `Poolitzer <https://github.com/Poolitzer>`_ (community liaison)
-- `Shivam <https://github.com/Starry69>`_
-- `Harshil <https://github.com/harshil21>`_
-- `Dmitry Kolomatskiy <https://github.com/lemontree210>`_
-- `Aditya <https://github.com/clot27>`_
-
-Emeritus maintainers include
-`Jannes Höke <https://github.com/jh0ker>`_ (`@jh0ker <https://t.me/jh0ker>`_ on Telegram),
-`Noam Meltzer <https://github.com/tsnoam>`_, `Pieter Schutz <https://github.com/eldinnie>`_ and `Jasmin Bom <https://github.com/jsmnbom>`_.
+``python-telegram-bot`` is written and maintained by `Leandro Toledo <https://github.com/leandrotoledo>`_.
 
 Contributors
 ------------
 
 The following wonderful people contributed directly or indirectly to this project:
 
-- `Abdelrahman <https://github.com/aelkheir>`_
-- `Abshar <https://github.com/abxhr>`_
-- `Alateas <https://github.com/alateas>`_
-- `Ales Dokshanin <https://github.com/alesdokshanin>`_
-- `Alexandre <https://github.com/xTudoS>`_
-- `Alizia <https://github.com/thefunkycat>`_
-- `Ambro17 <https://github.com/Ambro17>`_
-- `Andrej Zhilenkov <https://github.com/Andrej730>`_
-- `Anton Tagunov <https://github.com/anton-tagunov>`_
 - `Avanatiker <https://github.com/Avanatiker>`_
 - `Balduro <https://github.com/Balduro>`_
-- `Bibo-Joshi <https://github.com/Bibo-Joshi>`_
-- `Biruk Alamirew <https://github.com/BAcode-X>`_
 - `bimmlerd <https://github.com/bimmlerd>`_
-- `cyc8 <https://github.com/cyc8>`_ 
-- `d-qoi <https://github.com/d-qoi>`_
-- `daimajia <https://github.com/daimajia>`_
-- `Daniel Reed <https://github.com/nmlorg>`_
-- `D David Livingston <https://github.com/daviddl9>`_
-- `DonalDuck004 <https://github.com/DonalDuck004>`_
-- `Eana Hufwe <https://github.com/blueset>`_
-- `Ehsan Online <https://github.com/ehsanonline>`_
-- `Eldad Carin <https://github.com/eldbud>`_
-- `Eli Gao <https://github.com/eligao>`_
-- `Emilio Molinari <https://github.com/xates>`_
 - `ErgoZ Riftbit Vaper <https://github.com/ergoz>`_
-- `Eugene Lisitsky <https://github.com/lisitsky>`_
-- `Eugenio Panadero <https://github.com/azogue>`_
-- `Evan Haberecht <https://github.com/habereet>`_
-- `Evgeny Denisov <https://github.com/eIGato>`_
-- `evgfilim1 <https://github.com/evgfilim1>`_
-- `ExalFabu <https://github.com/ExalFabu>`_
 - `franciscod <https://github.com/franciscod>`_
-- `gamgi <https://github.com/gamgi>`_
-- `Gauthamram Ravichandran <https://github.com/GauthamramRavichandran>`_
-- `Harshil <https://github.com/harshil21>`_
-- `Hugo Damer <https://github.com/HakimusGIT>`_
-- `ihoru <https://github.com/ihoru>`_
-- `Iulian Onofrei <https://github.com/revolter>`_
-- `Jasmin Bom <https://github.com/jsmnbom>`_
 - `JASON0916 <https://github.com/JASON0916>`_
-- `jeffffc <https://github.com/jeffffc>`_
-- `Jelle Besseling <https://github.com/pingiun>`_
 - `jh0ker <https://github.com/jh0ker>`_
-- `jlmadurga <https://github.com/jlmadurga>`_
-- `John Yong <https://github.com/whipermr5>`_
-- `Joscha Götzer <https://github.com/Rostgnom>`_
-- `jossalgon <https://github.com/jossalgon>`_
 - `JRoot3D <https://github.com/JRoot3D>`_
-- `kenjitagawa <https://github.com/kenjitagawa>`_
-- `kennethcheo <https://github.com/kennethcheo>`_
-- `Kirill Vasin <https://github.com/vasinkd>`_
-- `Kjwon15 <https://github.com/kjwon15>`_
-- `Li-aung Yip <https://github.com/LiaungYip>`_
-- `Loo Zheng Yuan <https://github.com/loozhengyuan>`_
-- `LRezende <https://github.com/lrezende>`_
-- `Luca Bellanti <https://github.com/Trifase>`_
-- `Lucas Molinari <https://github.com/lucasmolinari>`_
+- `jlmadurga <https://github.com/jlmadurga>`_
 - `macrojames <https://github.com/macrojames>`_
-- `Matheus Lemos <https://github.com/mlemosf>`_
-- `Michael Dix <https://github.com/Eisberge>`_
-- `Michael Elovskikh <https://github.com/wronglink>`_
-- `Miguel C. R. <https://github.com/MiguelX413>`_
-- `miles <https://github.com/miles170>`_
-- `Mischa Krüger <https://github.com/Makman2>`_
 - `naveenvhegde <https://github.com/naveenvhegde>`_
-- `neurrone <https://github.com/neurrone>`_
-- `NikitaPirate <https://github.com/NikitaPirate>`_
-- `Nikolai Krivenko <https://github.com/nkrivenko>`_
 - `njittam <https://github.com/njittam>`_
 - `Noam Meltzer <https://github.com/tsnoam>`_
 - `Oleg Shlyazhko <https://github.com/ollmer>`_
-- `Oleg Sushchenko <https://github.com/feuillemorte>`_
-- `Or Bin <https://github.com/OrBin>`_
-- `overquota <https://github.com/overquota>`_
-- `Paradox <https://github.com/paradox70>`_
-- `Patrick Hofmann <https://github.com/PH89>`_
-- `Paul Larsen <https://github.com/PaulSonOfLars>`_
-- `Pawan <https://github.com/pawanrai9999>`_
-- `Pieter Schutz <https://github.com/eldinnie>`_
-- `Piraty <https://github.com/piraty>`_
-- `Poolitzer <https://github.com/Poolitzer>`_
-- `Pranjalya Tiwari <https://github.com/Pranjalya>`_
 - `Rahiel Kasim <https://github.com/rahiel>`_
-- `Riko Naka <https://github.com/rikonaka>`_
-- `Rizlas <https://github.com/rizlas>`_
-- `Sahil Sharma <https://github.com/sahilsharma811>`_
-- `Sam Mosleh <https://github.com/sam-mosleh>`_
-- `Sascha <https://github.com/saschalalala>`_
 - `Shelomentsev D <https://github.com/shelomentsevd>`_
-- `Shivam Saini <https://github.com/shivamsn97>`_
-- `Simon Schürrle <https://github.com/SitiSchu>`_
 - `sooyhwang <https://github.com/sooyhwang>`_
-- `syntx <https://github.com/syntx>`_
-- `thodnev <https://github.com/thodnev>`_
-- `Timur Kushukov <https://github.com/timqsh>`_
-- `Trainer Jono <https://github.com/Tr-Jono>`_
-- `Valentijn <https://github.com/Faalentijn>`_
-- `voider1 <https://github.com/voider1>`_
-- `Vorobjev Simon <https://github.com/simonvorobjev>`_
-- `Wagner Macedo <https://github.com/wagnerluis1982>`_
 - `wjt <https://github.com/wjt>`_
-- `Wonseok Oh <https://github.com/marinelay>`_
-- `Yaw Danso <https://github.com/dglitxh>`_
-- `Yao Kuan <https://github.com/thatguylah>`_
-- `zeroone2numeral2 <https://github.com/zeroone2numeral2>`_
-- `zeshuaro <https://github.com/zeshuaro>`_
-- `zpavloudis <https://github.com/zpavloudis>`_
-
 
 Please add yourself here alphabetically when you submit your first pull request.

CODE_OF_CONDUCT.rst

@@ -1,52 +0,0 @@
-====================================
-Contributor Covenant Code of Conduct
-====================================
-
-Our Pledge
-==========
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-Our Standards
-=============
-
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Publication of any content supporting, justifying or otherwise affiliating with terror and/or hate towards others
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-Our Responsibilities
-====================
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-Scope
-=====
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
-Enforcement
-===========
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at devs@python-telegram-bot.org. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-Attribution
-===========
-
-This Code of Conduct is adapted from the `Contributor Covenant <https://www.contributor-covenant.org>`_, version 1.4, available at `https://www.contributor-covenant.org/version/1/4 <https://www.contributor-covenant.org/version/1/4/>`_.

LICENSE.dual

@@ -1,792 +0,0 @@
-  NOTICE: You can find here the GPLv3 license and after the Lesser GPLv3 license.
-You may choose either license.
-
-
-                   GNU LESSER GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. [http://fsf.org/]
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-
-  This version of the GNU Lesser General Public License incorporates
-the terms and conditions of version 3 of the GNU General Public
-License, supplemented by the additional permissions listed below.
-
-  0. Additional Definitions.
-
-  As used herein, "this License" refers to version 3 of the GNU Lesser
-General Public License, and the "GNU GPL" refers to version 3 of the GNU
-General Public License.
-
-  "The Library" refers to a covered work governed by this License,
-other than an Application or a Combined Work as defined below.
-
-  An "Application" is any work that makes use of an interface provided
-by the Library, but which is not otherwise based on the Library.
-Defining a subclass of a class defined by the Library is deemed a mode
-of using an interface provided by the Library.
-
-  A "Combined Work" is a work produced by combining or linking an
-Application with the Library.  The particular version of the Library
-with which the Combined Work was made is also called the "Linked
-Version".
-
-  The "Minimal Corresponding Source" for a Combined Work means the
-Corresponding Source for the Combined Work, excluding any source code
-for portions of the Combined Work that, considered in isolation, are
-based on the Application, and not on the Linked Version.
-
-  The "Corresponding Application Code" for a Combined Work means the
-object code and/or source code for the Application, including any data
-and utility programs needed for reproducing the Combined Work from the
-Application, but excluding the System Libraries of the Combined Work.
-
-  1. Exception to Section 3 of the GNU GPL.
-
-  You may convey a covered work under sections 3 and 4 of this License
-without being bound by section 3 of the GNU GPL.
-
-  2. Conveying Modified Versions.
-
-  If you modify a copy of the Library, and, in your modifications, a
-facility refers to a function or data to be supplied by an Application
-that uses the facility (other than as an argument passed when the
-facility is invoked), then you may convey a copy of the modified
-version:
-
-   a) under this License, provided that you make a good faith effort to
-   ensure that, in the event an Application does not supply the
-   function or data, the facility still operates, and performs
-   whatever part of its purpose remains meaningful, or
-
-   b) under the GNU GPL, with none of the additional permissions of
-   this License applicable to that copy.
-
-  3. Object Code Incorporating Material from Library Header Files.
-
-  The object code form of an Application may incorporate material from
-a header file that is part of the Library.  You may convey such object
-code under terms of your choice, provided that, if the incorporated
-material is not limited to numerical parameters, data structure
-layouts and accessors, or small macros, inline functions and templates
-(ten or fewer lines in length), you do both of the following:
-
-   a) Give prominent notice with each copy of the object code that the
-   Library is used in it and that the Library and its use are
-   covered by this License.
-
-   b) Accompany the object code with a copy of the GNU GPL and this license
-   document.
-
-  4. Combined Works.
-
-  You may convey a Combined Work under terms of your choice that,
-taken together, effectively do not restrict modification of the
-portions of the Library contained in the Combined Work and reverse
-engineering for debugging such modifications, if you also do each of
-the following:
-
-   a) Give prominent notice with each copy of the Combined Work that
-   the Library is used in it and that the Library and its use are
-   covered by this License.
-
-   b) Accompany the Combined Work with a copy of the GNU GPL and this license
-   document.
-
-   c) For a Combined Work that displays copyright notices during
-   execution, include the copyright notice for the Library among
-   these notices, as well as a reference directing the user to the
-   copies of the GNU GPL and this license document.
-
-   d) Do one of the following:
-
-       0) Convey the Minimal Corresponding Source under the terms of this
-       License, and the Corresponding Application Code in a form
-       suitable for, and under terms that permit, the user to
-       recombine or relink the Application with a modified version of
-       the Linked Version to produce a modified Combined Work, in the
-       manner specified by section 6 of the GNU GPL for conveying
-       Corresponding Source.
-
-       1) Use a suitable shared library mechanism for linking with the
-       Library.  A suitable mechanism is one that (a) uses at run time
-       a copy of the Library already present on the user's computer
-       system, and (b) will operate properly with a modified version
-       of the Library that is interface-compatible with the Linked
-       Version.
-
-   e) Provide Installation Information, but only if you would otherwise
-   be required to provide such information under section 6 of the
-   GNU GPL, and only to the extent that such information is
-   necessary to install and execute a modified version of the
-   Combined Work produced by recombining or relinking the
-   Application with a modified version of the Linked Version. (If
-   you use option 4d0, the Installation Information must accompany
-   the Minimal Corresponding Source and Corresponding Application
-   Code. If you use option 4d1, you must provide the Installation
-   Information in the manner specified by section 6 of the GNU GPL
-   for conveying Corresponding Source.)
-
-  5. Combined Libraries.
-
-  You may place library facilities that are a work based on the
-Library side by side in a single library together with other library
-facilities that are not Applications and are not covered by this
-License, and convey such a combined library under terms of your
-choice, if you do both of the following:
-
-   a) Accompany the combined library with a copy of the same work based
-   on the Library, uncombined with any other library facilities,
-   conveyed under the terms of this License.
-
-   b) Give prominent notice with the combined library that part of it
-   is a work based on the Library, and explaining where to find the
-   accompanying uncombined form of the same work.
-
-  6. Revised Versions of the GNU Lesser General Public License.
-
-  The Free Software Foundation may publish revised and/or new versions
-of the GNU Lesser General Public License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns.
-
-  Each version is given a distinguishing version number. If the
-Library as you received it specifies that a certain numbered version
-of the GNU Lesser General Public License "or any later version"
-applies to it, you have the option of following the terms and
-conditions either of that published version or of any later version
-published by the Free Software Foundation. If the Library as you
-received it does not specify a version number of the GNU Lesser
-General Public License, you may choose any version of the GNU Lesser
-General Public License ever published by the Free Software Foundation.
-
-  If the Library as you received it specifies that a proxy can decide
-whether future versions of the GNU Lesser General Public License shall
-apply, that proxy's public statement of acceptance of any version is
-permanent authorization for you to choose that version for the
-Library.
-
-
-
-
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. [http://fsf.org/]
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-the GNU General Public License is intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.  We, the Free Software Foundation, use the
-GNU General Public License for most of our software; it applies also to
-any other work released this way by its authors.  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights.  Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received.  You must make sure that they, too, receive
-or can get the source code.  And you must show them these terms so they
-know their rights.
-
-  Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
-  For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software.  For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
-  Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so.  This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software.  The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable.  Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products.  If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
-
-  Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish to
-avoid the special danger that patents applied to a free program could
-make it effectively proprietary.  To prevent this, the GPL assures that
-patents cannot be used to render the program non-free.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Use with the GNU Affero General Public License.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.

MANIFEST.in

@@ -0,0 +1 @@
+include LICENSE LICENSE.lesser Makefile requirements.txt

Makefile

@@ -0,0 +1,52 @@
+.DEFAULT_GOAL := help
+.PHONY: clean pep257 pep8 yapf lint test install
+
+PYLINT          := pylint
+NOSETESTS       := nosetests
+PEP257          := pep257
+PEP8            := flake8
+YAPF            := yapf
+PIP             := pip
+
+clean:
+	rm -fr build
+	rm -fr dist
+	find . -name '*.pyc' -exec rm -f {} \;
+	find . -name '*.pyo' -exec rm -f {} \;
+	find . -name '*~' -exec rm -f {} \;
+	find . -regex "./telegram.\(mp3\|mp4\|ogg\|png\|webp\)" -exec rm {} \;
+
+pep257:
+	$(PEP257) telegram
+
+pep8:
+	$(PEP8) telegram
+
+yapf:
+	$(YAPF) -r telegram
+
+lint:
+	$(PYLINT) -E telegram --disable=no-name-in-module,import-error
+
+test:
+	$(NOSETESTS) -v
+
+install:
+	$(PIP)  install -r requirements.txt -r requirements-dev.txt
+
+help:
+	@echo "Available targets:"
+	@echo "- clean       Clean up the source directory"
+	@echo "- pep257      Check docstring style with pep257"
+	@echo "- pep8        Check style with flake8"
+	@echo "- lint        Check style with pylint"
+	@echo "- yapf        Check style with yapf"
+	@echo "- test        Run tests"
+	@echo
+	@echo "Available variables:"
+	@echo "- PYLINT      default: $(PYLINT)"
+	@echo "- NOSETESTS   default: $(NOSETESTS)"
+	@echo "- PEP257      default: $(PEP257)"
+	@echo "- PEP8        default: $(PEP8)"
+	@echo "- YAPF        default: $(YAPF)"
+	@echo "- PIP         default: $(PIP)"

README.rst

@@ -1,235 +1,195 @@
-.. image:: https://raw.githubusercontent.com/python-telegram-bot/logos/master/logo-text/png/ptb-logo-text_768.png
+.. image:: https://github.com/python-telegram-bot/logos/blob/master/logo-text/png/ptb-logo-text_768.png?raw=true
    :align: center
-   :target: https://python-telegram-bot.org
+   :target: https://github.com/python-telegram-bot/logos
    :alt: python-telegram-bot Logo
 
+Not **just** a Python wrapper around the Telegram Bot API
+
+*Stay tuned for library updates and new releases on our* `Telegram Channel <https://telegram.me/pythontelegrambotchannel>`_.
+
 .. image:: https://img.shields.io/pypi/v/python-telegram-bot.svg
-   :target: https://pypi.org/project/python-telegram-bot/
+   :target: https://pypi.python.org/pypi/python-telegram-bot
    :alt: PyPi Package Version
 
 .. image:: https://img.shields.io/pypi/pyversions/python-telegram-bot.svg
-   :target: https://pypi.org/project/python-telegram-bot/
-   :alt: Supported Python versions
+   :target: https://pypi.python.org/pypi/python-telegram-bot
+   :alt: Supported python versions
 
-.. image:: https://img.shields.io/badge/Bot%20API-7.7-blue?logo=telegram
-   :target: https://core.telegram.org/bots/api-changelog
-   :alt: Supported Bot API version
-
-.. image:: https://img.shields.io/pypi/dm/python-telegram-bot
-   :target: https://pypistats.org/packages/python-telegram-bot
-   :alt: PyPi Package Monthly Download
-
-.. image:: https://readthedocs.org/projects/python-telegram-bot/badge/?version=stable
-   :target: https://docs.python-telegram-bot.org/en/stable/
+.. image:: https://img.shields.io/badge/docs-latest-af1a97.svg
+   :target: https://pythonhosted.org/python-telegram-bot/
    :alt: Documentation Status
 
 .. image:: https://img.shields.io/pypi/l/python-telegram-bot.svg
    :target: https://www.gnu.org/licenses/lgpl-3.0.html
    :alt: LGPLv3 License
 
-.. image:: https://github.com/python-telegram-bot/python-telegram-bot/actions/workflows/unit_tests.yml/badge.svg?branch=master
-   :target: https://github.com/python-telegram-bot/python-telegram-bot/
-   :alt: Github Actions workflow
+.. image:: https://travis-ci.org/python-telegram-bot/python-telegram-bot.svg?branch=master
+   :target: https://travis-ci.org/python-telegram-bot/python-telegram-bot
+   :alt: Travis CI Status
 
-.. image:: https://codecov.io/gh/python-telegram-bot/python-telegram-bot/branch/master/graph/badge.svg
-   :target: https://app.codecov.io/gh/python-telegram-bot/python-telegram-bot
-   :alt: Code coverage
+.. image:: https://codeclimate.com/github/python-telegram-bot/python-telegram-bot/badges/gpa.svg
+   :target: https://codeclimate.com/github/python-telegram-bot/python-telegram-bot
+   :alt: Code Climate
 
-.. image:: https://isitmaintained.com/badge/resolution/python-telegram-bot/python-telegram-bot.svg
-   :target: https://isitmaintained.com/project/python-telegram-bot/python-telegram-bot
-   :alt: Median time to resolve an issue
+.. image:: https://coveralls.io/repos/python-telegram-bot/python-telegram-bot/badge.svg?branch=master&service=github
+   :target: https://coveralls.io/github/python-telegram-bot/python-telegram-bot?branch=master
+   :alt: Coveralls
+   
+.. image:: http://isitmaintained.com/badge/resolution/python-telegram-bot/python-telegram-bot.svg
+   :target: http://isitmaintained.com/project/python-telegram-bot/python-telegram-bot
+   :alt: Average time to resolve an issue
 
-.. image:: https://api.codacy.com/project/badge/Grade/99d901eaa09b44b4819aec05c330c968
-   :target: https://app.codacy.com/gh/python-telegram-bot/python-telegram-bot/dashboard
-   :alt: Code quality: Codacy
-
-.. image:: https://results.pre-commit.ci/badge/github/python-telegram-bot/python-telegram-bot/master.svg
-   :target: https://results.pre-commit.ci/latest/github/python-telegram-bot/python-telegram-bot/master
-   :alt: pre-commit.ci status
-
-.. image:: https://img.shields.io/badge/code%20style-black-000000.svg
-   :target: https://github.com/psf/black
-   :alt: Code Style: Black
-
-.. image:: https://img.shields.io/badge/Telegram-Channel-blue.svg?logo=telegram
-   :target: https://t.me/pythontelegrambotchannel
-   :alt: Telegram Channel
-
-.. image:: https://img.shields.io/badge/Telegram-Group-blue.svg?logo=telegram
+.. image:: https://img.shields.io/badge/Telegram-Group-blue.svg
    :target: https://telegram.me/pythontelegrambotgroup
    :alt: Telegram Group
 
-We have made you a wrapper you can't refuse
+=================
+Table of contents
+=================
 
-We have a vibrant community of developers helping each other in our `Telegram group <https://telegram.me/pythontelegrambotgroup>`_. Join us!
+- `Introduction`_
 
-*Stay tuned for library updates and new releases on our* `Telegram Channel <https://telegram.me/pythontelegrambotchannel>`_.
+- `Telegram API support`_
 
+- `Installing`_
+
+- `Getting started`_
+
+  #. `Learning by example`_
+
+  #. `Logging`_
+
+  #. `Documentation`_
+
+- `Getting help`_
+
+- `Contributing`_
+
+- `License`_
+
+============
 Introduction
-------------
+============
 
-This library provides a pure Python, asynchronous interface for the
+This library provides a pure Python interface for the
 `Telegram Bot API <https://core.telegram.org/bots/api>`_.
-It's compatible with Python versions **3.8+**.
+It works with Python versions from 2.6+ (**Note:** Support for 2.6 will be dropped at some point
+this year. 2.7 will still be supported).
+It also works with `Google App Engine <https://cloud.google.com/appengine>`_.
 
-In addition to the pure API implementation, this library features several convenience methods and shortcuts as well as a number of high-level classes to
+In addition to the pure API implementation, this library features a number of high-level classes to
 make the development of bots easy and straightforward. These classes are contained in the
 ``telegram.ext`` submodule.
 
-After installing_ the library, be sure to check out the section on `working with PTB`_.
-
+====================
 Telegram API support
-~~~~~~~~~~~~~~~~~~~~
+====================
 
-All types and methods of the Telegram Bot API **7.7** are natively supported by this library.
-In addition, Bot API functionality not yet natively included can still be used as described `in our wiki <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Bot-API-Forward-Compatibility>`_.
-
-Notable Features
-~~~~~~~~~~~~~~~~
-
-- `Fully asynchronous <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Concurrency>`_
-- Convenient shortcut methods, e.g. `Message.reply_text <https://docs.python-telegram-bot.org/en/stable/telegram.message.html#telegram.Message.reply_text>`_
-- `Fully annotated with static type hints <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Type-Checking>`_
-- `Customizable and extendable interface <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Architecture>`_
-- Seamless integration with `webhooks <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Webhooks>`_ and `polling <https://docs.python-telegram-bot.org/en/stable/telegram.ext.application.html#telegram.ext.Application.run_polling>`_
-- `Comprehensive documentation and examples <#working-with-ptb>`_
+As of **28. May 2016**, all types and methods of the Telegram Bot API are supported.
 
+==========
 Installing
-----------
+==========
 
-You can install or upgrade ``python-telegram-bot`` via
+You can install or upgrade python-telegram-bot with:
 
 .. code:: shell
 
     $ pip install python-telegram-bot --upgrade
 
-To install a pre-release, use the ``--pre`` `flag <https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-pre>`_ in addition.
+===============
+Getting started
+===============
 
-You can also install ``python-telegram-bot`` from source, though this is usually not necessary.
+Our Wiki contains a lot of resources to get you started with ``python-telegram-bot``:
 
-.. code:: shell
+- `Introduction to the API <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Introduction-to-the-API>`_
+- Tutorial: `Your first Bot <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Extensions-%E2%80%93-Your-first-Bot>`_
 
-    $ git clone https://github.com/python-telegram-bot/python-telegram-bot
-    $ cd python-telegram-bot
-    $ pip install build
-    $ python -m build
+Other references:
 
-Verifying Releases
-~~~~~~~~~~~~~~~~~~
+- `Telegram API documentation <https://core.telegram.org/bots/api>`_
+- `python-telegram-bot documentation <https://pythonhosted.org/python-telegram-bot/>`_
 
-To enable you to verify that a release file that you downloaded was indeed provided by the ``python-telegram-bot`` team, we have taken the following measures.
+-------------------
+Learning by example
+-------------------
 
-Starting with v21.4, all releases are signed via `sigstore <https://sigstore.dev>`_.
-The corresponding signature files are uploaded to the `GitHub releases page`_.
-To verify the signature, please install the `sigstore Python client <https://pypi.org/project/sigstore/>`_ and follow the instructions for `verifying signatures from GitHub Actions <https://github.com/sigstore/sigstore-python#signatures-from-github-actions>`_. As input for the ``--repository`` parameter, please use the value ``python-telegram-bot/python-telegram-bot``.
+We believe that the best way to learn and understand this simple package is by example. So here
+are some examples for you to review. Even if it's not your approach for learning, please take a
+look at ``echobot2`` (below), it is de facto the base for most of the bots out there. Best of all,
+the code for these examples are released to the public domain, so you can start by grabbing the
+code and building on top of it.
 
-Earlier releases are signed with a GPG key.
-The signatures are uploaded to both the `GitHub releases page`_ and the `PyPI project <https://pypi.org/project/python-telegram-bot/>`_ and end with a suffix ``.asc``.
-Please find the public keys `here <https://github.com/python-telegram-bot/python-telegram-bot/tree/master/public_keys>`_.
-The keys are named in the format ``<first_version>-<last_version>.gpg``.
+- `echobot2 <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/echobot2.py>`_ replies back messages.
 
-In addition, the GitHub release page also contains the sha1 hashes of the release files in the files with the suffix ``.sha1``.
+- `inlinebot <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/inlinebot.py>`_ basic example of an `inline bot <https://core.telegram.org/bots/inline>`_.
 
-Dependencies & Their Versions
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+- `state machine bot <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/state_machine_bot.py>`_ keeps the state for individual users, useful for multipart conversations.
 
-``python-telegram-bot`` tries to use as few 3rd party dependencies as possible.
-However, for some features using a 3rd party library is more sane than implementing the functionality again.
-As these features are *optional*, the corresponding 3rd party dependencies are not installed by default.
-Instead, they are listed as optional dependencies.
-This allows to avoid unnecessary dependency conflicts for users who don't need the optional features.
+- `timerbot <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/timerbot.py>`_ uses the ``JobQueue`` to send timed messages.
 
-The only required dependency is `httpx ~= 0.27 <https://www.python-httpx.org>`_ for
-``telegram.request.HTTPXRequest``, the default networking backend.
+- `echobot <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/legacy/echobot.py>`_ uses only the pure API to echo messages.
 
-``python-telegram-bot`` is most useful when used along with additional libraries.
-To minimize dependency conflicts, we try to be liberal in terms of version requirements on the (optional) dependencies.
-On the other hand, we have to ensure stability of ``python-telegram-bot``, which is why we do apply version bounds.
-If you encounter dependency conflicts due to these bounds, feel free to reach out.
+Look at the examples on the `wiki <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Examples>`_ to see other bots the community has built.
 
-Optional Dependencies
-#####################
-
-PTB can be installed with optional dependencies:
-
-* ``pip install "python-telegram-bot[passport]"`` installs the `cryptography>=39.0.1 <https://cryptography.io/en/stable>`_ library. Use this, if you want to use Telegram Passport related functionality.
-* ``pip install "python-telegram-bot[socks]"`` installs `httpx[socks] <https://www.python-httpx.org/#dependencies>`_. Use this, if you want to work behind a Socks5 server.
-* ``pip install "python-telegram-bot[http2]"`` installs `httpx[http2] <https://www.python-httpx.org/#dependencies>`_. Use this, if you want to use HTTP/2.
-* ``pip install "python-telegram-bot[rate-limiter]"`` installs `aiolimiter~=1.1.0 <https://aiolimiter.readthedocs.io/en/stable/>`_. Use this, if you want to use ``telegram.ext.AIORateLimiter``.
-* ``pip install "python-telegram-bot[webhooks]"`` installs the `tornado~=6.4 <https://www.tornadoweb.org/en/stable/>`_ library. Use this, if you want to use ``telegram.ext.Updater.start_webhook``/``telegram.ext.Application.run_webhook``.
-* ``pip install "python-telegram-bot[callback-data]"`` installs the `cachetools~=5.3.3 <https://cachetools.readthedocs.io/en/latest/>`_ library. Use this, if you want to use `arbitrary callback_data <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Arbitrary-callback_data>`_.
-* ``pip install "python-telegram-bot[job-queue]"`` installs the `APScheduler~=3.10.4 <https://apscheduler.readthedocs.io/en/3.x/>`_ library and enforces `pytz>=2018.6 <https://pypi.org/project/pytz/>`_, where ``pytz`` is a dependency of ``APScheduler``. Use this, if you want to use the ``telegram.ext.JobQueue``.
-
-To install multiple optional dependencies, separate them by commas, e.g. ``pip install "python-telegram-bot[socks,webhooks]"``.
-
-Additionally, two shortcuts are provided:
-
-* ``pip install "python-telegram-bot[all]"`` installs all optional dependencies.
-* ``pip install "python-telegram-bot[ext]"`` installs all optional dependencies that are related to ``telegram.ext``, i.e. ``[rate-limiter, webhooks, callback-data, job-queue]``.
-
-Working with PTB
-----------------
-
-Once you have installed the library, you can begin working with it - so let's get started!
-
-Quick Start
-~~~~~~~~~~~
-
-Our Wiki contains an `Introduction to the API <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Introduction-to-the-API>`_ explaining how the pure Bot API can be accessed via ``python-telegram-bot``.
-Moreover, the `Tutorial: Your first Bot <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Extensions---Your-first-Bot>`_ gives an introduction on how chatbots can be easily programmed with the help of the ``telegram.ext`` module.
-
-Resources
-~~~~~~~~~
-
-- The `package documentation <https://docs.python-telegram-bot.org/>`_ is the technical reference for ``python-telegram-bot``.
-  It contains descriptions of all available classes, modules, methods and arguments as well as the `changelog <https://docs.python-telegram-bot.org/changelog.html>`_.
-- The `wiki <https://github.com/python-telegram-bot/python-telegram-bot/wiki/>`_ is home to number of more elaborate introductions of the different features of ``python-telegram-bot`` and other useful resources that go beyond the technical documentation.
-- Our `examples section <https://docs.python-telegram-bot.org/examples.html>`_ contains several examples that showcase the different features of both the Bot API and ``python-telegram-bot``.
-  Even if it is not your approach for learning, please take a look at ``echobot.py``. It is the de facto base for most of the bots out there.
-  The code for these examples is released to the public domain, so you can start by grabbing the code and building on top of it.
-- The `official Telegram Bot API documentation <https://core.telegram.org/bots/api>`_ is of course always worth a read.
-
-Getting help
-~~~~~~~~~~~~
-
-If the resources mentioned above don't answer your questions or simply overwhelm you, there are several ways of getting help.
-
-1. We have a vibrant community of developers helping each other in our `Telegram group <https://telegram.me/pythontelegrambotgroup>`_. Join us! Asking a question here is often the quickest way to get a pointer in the right direction.
-
-2. Ask questions by opening `a discussion <https://github.com/python-telegram-bot/python-telegram-bot/discussions/new>`_.
-
-3. You can even ask for help on Stack Overflow using the `python-telegram-bot tag <https://stackoverflow.com/questions/tagged/python-telegram-bot>`_.
-
-Concurrency
-~~~~~~~~~~~
-
-Since v20.0, ``python-telegram-bot`` is built on top of Pythons ``asyncio`` module.
-Because ``asyncio`` is in general single-threaded, ``python-telegram-bot`` does currently not aim to be thread-safe.
-Noteworthy parts of ``python-telegram-bots`` API that are likely to cause issues (e.g. race conditions) when used in a multi-threaded setting include:
-
-* ``telegram.ext.Application/Updater.update_queue``
-* ``telegram.ext.ConversationHandler.check/handle_update``
-* ``telegram.ext.CallbackDataCache``
-* ``telegram.ext.BasePersistence``
-* all classes in the ``telegram.ext.filters`` module that allow to add/remove allowed users/chats at runtime
-
-Contributing
-------------
-
-Contributions of all sizes are welcome.
-Please review our `contribution guidelines <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/.github/CONTRIBUTING.rst>`_ to get started.
-You can also help by `reporting bugs or feature requests <https://github.com/python-telegram-bot/python-telegram-bot/issues/new/choose>`_.
-
-Donating
---------
-Occasionally we are asked if we accept donations to support the development.
-While we appreciate the thought, maintaining PTB is our hobby, and we have almost no running costs for it. We therefore have nothing set up to accept donations.
-If you still want to donate, we kindly ask you to donate to another open source project/initiative of your choice instead.
-
-License
+-------
+Logging
 -------
 
-You may copy, distribute and modify the software provided that modifications are described and licensed for free under `LGPL-3 <https://www.gnu.org/licenses/lgpl-3.0.html>`_.
-Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL-3, but applications that use the library don't have to be.
+This library uses the ``logging`` module. To set up logging to standard output, put:
 
-.. _`GitHub releases page`: https://github.com/python-telegram-bot/python-telegram-bot/releases>
+.. code:: python
+
+    import logging
+    logging.basicConfig(level=logging.DEBUG,
+                        format='%(asctime)s - %(name)s - %(levelname)s - %(message)s')
+
+at the beginning of your script.
+
+You can also use logs in your application by calling ``logging.getLogger()`` and setting the log level you want:
+
+.. code:: python
+
+    logger = logging.getLogger()
+    logger.setLevel(logging.INFO)
+
+If you want DEBUG logs instead:
+
+.. code:: python
+
+    logger.setLevel(logging.DEBUG)
+
+
+=============
+Documentation
+=============
+
+``python-telegram-bot``'s documentation lives at `pythonhosted.org <https://pythonhosted.org/python-telegram-bot/>`_.
+
+============
+Getting help
+============
+
+You can get help in several ways:
+
+1. We have a vibrant community of developers helping each other in our `Telegram group <https://telegram.me/pythontelegrambotgroup>`_. Join us!
+
+2. Our `Wiki pages <https://github.com/python-telegram-bot/python-telegram-bot/wiki/>`_ offer a growing amount of resources.
+
+3. You can ask for help on Stack Overflow using the `python-telegram-bot tag <https://stackoverflow.com/questions/tagged/python-telegram-bot>`_.
+
+4. As last resort, the developers are ready to help you with `serious issues <https://github.com/python-telegram-bot/python-telegram-bot/issues/new>`_.
+
+
+============
+Contributing
+============
+
+Contributions of all sizes are welcome. Please review our `contribution guidelines <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/.github/CONTRIBUTING.rst>`_ to get started. You can also help by `reporting bugs <https://github.com/python-telegram-bot/python-telegram-bot/issues/new>`_.
+
+=======
+License
+=======
+
+You may copy, distribute and modify the software provided that modifications are described and licensed for free under `LGPL-3 <https://www.gnu.org/licenses/lgpl-3.0.html>`_. Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL-3, but applications that use the library don't have to be.

codecov.yml

@@ -1,10 +0,0 @@
-comment: false
-
-coverage:
-  status:
-    project:
-      default:
-        # We allow small coverage decreases in the project because we don't retry
-        # on hitting flood limits, which adds noise to the coverage
-        target: auto
-        threshold: 0.1%

contrib/build-debian.sh

@@ -1,7 +0,0 @@
-#!/bin/bash
-
-cp -R contrib/debian .
-debuild -us -uc
-debian/rules clean
-rm -rf debian
-

contrib/debian/changelog

@@ -1,6 +0,0 @@
-telegram (12.0.0b1) unstable; urgency=medium
-
-  * Debian packaging;
-  * Initial Release.
-
- -- Marco Marinello <me@marcomarinello.it>  Thu, 22 Aug 2019 20:36:47 +0200

contrib/debian/compat

@@ -1 +0,0 @@
-11

contrib/debian/control

@@ -1,25 +0,0 @@
-Source: telegram
-Section: utils
-Priority: optional
-Maintainer: Marco Marinello <me@marcomarinello.it>
-Build-Depends: debhelper (>= 11), dh-python, python3-all, python3-setuptools
-Standards-Version: 4.1.3
-Homepage: https://python-telegram-bot.org
-X-Python-Version: >= 3.2
-Vcs-Browser: https://github.com/python-telegram-bot/python-telegram-bot
-Vcs-Git: https://github.com/python-telegram-bot/python-telegram-bot.git
-
-Package: python3-telegram-bot
-Architecture: any
-Depends: ${python3:Depends}, ${misc:Depends}
-Description: We have made you a wrapper you can't refuse!
- The Python Telegram bot (Python 3)
- This library provides a pure Python interface for the Telegram Bot API.
- It's compatible with Python versions 3.5+ and PyPy.
- .
- In addition to the pure API implementation, this library features
- a number of high-level
- classes to make the development of bots easy and straightforward.
- These classes are contained in the telegram.ext submodule.
- .
- This package installs the library for Python 3.

contrib/debian/copyright

@@ -1,30 +0,0 @@
-Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
-Upstream-Name: telegram
-Source: https://github.com/python-telegram-bot/python-telegram-bot
-
-Files: *
-Copyright: 2019 Leandro Toledo
-           2019 see AUTHORS file
-License: LGPLv3
-
-Files: debian/*
-Copyright: 2019 Marco Marinello <me@marcomarinello.it>
-License: GPL-3.0+
-
-License: GPL-3.0+
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
- .
- This package is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- GNU General Public License for more details.
- .
- You should have received a copy of the GNU General Public License
- along with this program. If not, see <https://www.gnu.org/licenses/>.
- .
- On Debian systems, the complete text of the GNU General
- Public License version 3 can be found in "/usr/share/common-licenses/GPL-3".
-

contrib/debian/install

@@ -1 +0,0 @@
-AUTHORS.rst	/usr/share/doc/python3-telegram-bot

contrib/debian/rules

@@ -1,18 +0,0 @@
-#!/usr/bin/make -f
-# See debhelper(7) (uncomment to enable)
-# output every command that modifies files on the build system.
-#export DH_VERBOSE = 1
-
-export PYBUILD_NAME=telegram
-
-%:
-	DEB_BUILD_OPTIONS=nocheck dh $@ --with python3 --buildsystem=pybuild
-
-
-# If you need to rebuild the Sphinx documentation
-# Add spinxdoc to the dh --with line
-#override_dh_auto_build:
-#	dh_auto_build
-#	PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml        docs/ build/html # HTML generator
-#	PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bman        docs/ build/man # Manpage generator
-

contrib/debian/source/format

@@ -1 +0,0 @@
-3.0 (native)

contrib/debian/source/options

@@ -1 +0,0 @@
-extend-diff-ignore = "^[^/]*[.]egg-info/"

docs/Makefile

@@ -15,7 +15,7 @@ endif
 # Internal variables.
 PAPEROPT_a4     = -D latex_paper_size=a4
 PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source -j auto
+ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
 # the i18n builder cannot share the environment and doctrees with the others
 I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) source
 
@@ -56,8 +56,6 @@ html:
 	@echo
 	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
 
-rebuild: clean html
-
 dirhtml:
 	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
 	@echo
@@ -191,4 +189,4 @@ xml:
 pseudoxml:
 	$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
 	@echo
-	@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."
+	@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."

docs/auxil/admonition_inserter.py

@@ -1,597 +0,0 @@
-#
-#  A library that provides a Python interface to the Telegram Bot API
-#  Copyright (C) 2015-2024
-#  Leandro Toledo de Souza <devs@python-telegram-bot.org>
-#
-#  This program is free software: you can redistribute it and/or modify
-#  it under the terms of the GNU Lesser Public License as published by
-#  the Free Software Foundation, either version 3 of the License, or
-#  (at your option) any later version.
-#
-#  This program is distributed in the hope that it will be useful,
-#  but WITHOUT ANY WARRANTY; without even the implied warranty of
-#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-#  GNU Lesser Public License for more details.
-#
-#  You should have received a copy of the GNU Lesser Public License
-#  along with this program.  If not, see [http://www.gnu.org/licenses/].
-import collections.abc
-import inspect
-import re
-import typing
-from collections import defaultdict
-from typing import Any, Iterator, Union
-
-import telegram
-import telegram.ext
-
-
-def _iter_own_public_methods(cls: type) -> Iterator[tuple[str, type]]:
-    """Iterates over methods of a class that are not protected/private,
-    not camelCase and not inherited from the parent class.
-
-    Returns pairs of method names and methods.
-
-    This function is defined outside the class because it is used to create class constants.
-    """
-    return (
-        m
-        for m in inspect.getmembers(cls, predicate=inspect.isfunction)  # not .ismethod
-        if not m[0].startswith("_")
-        and m[0].islower()  # to avoid camelCase methods
-        and m[0] in cls.__dict__  # method is not inherited from parent class
-    )
-
-
-class AdmonitionInserter:
-    """Class for inserting admonitions into docs of Telegram classes."""
-
-    CLASS_ADMONITION_TYPES = ("use_in", "available_in", "returned_in")
-    METHOD_ADMONITION_TYPES = ("shortcuts",)
-    ALL_ADMONITION_TYPES = CLASS_ADMONITION_TYPES + METHOD_ADMONITION_TYPES
-
-    FORWARD_REF_PATTERN = re.compile(r"^ForwardRef\('(?P<class_name>\w+)'\)$")
-    """ A pattern to find a class name in a ForwardRef typing annotation.
-    Class name (in a named group) is surrounded by parentheses and single quotes.
-    Note that since we're analyzing argument by argument, the pattern can be strict, with
-    start and end markers.
-    """
-
-    FORWARD_REF_SKIP_PATTERN = re.compile(r"^ForwardRef\('DefaultValue\[\w+]'\)$")
-    """A pattern that will be used to skip known ForwardRef's that need not be resolved
-    to a Telegram class, e.g.:
-    ForwardRef('DefaultValue[None]')
-    ForwardRef('DefaultValue[DVValueType]')
-    """
-
-    METHOD_NAMES_FOR_BOT_AND_APPBUILDER: typing.ClassVar[dict[type, str]] = {
-        cls: tuple(m[0] for m in _iter_own_public_methods(cls))  # m[0] means we take only names
-        for cls in (telegram.Bot, telegram.ext.ApplicationBuilder)
-    }
-    """A dictionary mapping Bot and ApplicationBuilder classes to their relevant methods that will
-    be mentioned in 'Returned in' and 'Use in' admonitions in other classes' docstrings.
-    Methods must be public, not aliases, not inherited from TelegramObject.
-    """
-
-    def __init__(self):
-        self.admonitions: dict[str, dict[Union[type, collections.abc.Callable], str]] = {
-            # dynamically determine which method to use to create a sub-dictionary
-            admonition_type: getattr(self, f"_create_{admonition_type}")()
-            for admonition_type in self.ALL_ADMONITION_TYPES
-        }
-        """Dictionary with admonitions. Contains sub-dictionaries, one per admonition type.
-        Each sub-dictionary matches bot methods (for "Shortcuts") or telegram classes (for other
-        admonition types) to texts of admonitions, e.g.:
-        ```
-        {
-        "use_in": {<class 'telegram._chatinvitelink.ChatInviteLink'>:
-        <"Use in" admonition for ChatInviteLink>, ...},
-        "available_in": {<class 'telegram._chatinvitelink.ChatInviteLink'>:
-        <"Available in" admonition">, ...},
-        "returned_in": {...}
-        }
-        ```
-        """
-
-    def insert_admonitions(
-        self,
-        obj: Union[type, collections.abc.Callable],
-        docstring_lines: list[str],
-    ):
-        """Inserts admonitions into docstring lines for a given class or method.
-
-        **Modifies lines in place**.
-        """
-        # A better way would be to copy the lines and return them, but that will not work with
-        # docs.auxil.sphinx_hooks.autodoc_process_docstring()
-
-        for admonition_type in self.ALL_ADMONITION_TYPES:
-            # If there is no admonition of the given type for the given class or method,
-            # continue to the next admonition type, maybe the class/method is listed there.
-            if obj not in self.admonitions[admonition_type]:
-                continue
-
-            insert_idx = self._find_insert_pos_for_admonition(docstring_lines)
-            admonition_lines = self.admonitions[admonition_type][obj].splitlines()
-
-            for idx in range(insert_idx, insert_idx + len(admonition_lines)):
-                docstring_lines.insert(idx, admonition_lines[idx - insert_idx])
-
-    def _create_available_in(self) -> dict[type, str]:
-        """Creates a dictionary with 'Available in' admonitions for classes that are available
-        in attributes of other classes.
-        """
-
-        # Generate a mapping of classes to ReST links to attributes in other classes that
-        # correspond to instances of a given class
-        # i.e. {telegram._files.sticker.Sticker: {":attr:`telegram.Message.sticker`", ...}}
-        attrs_for_class = defaultdict(set)
-
-        # The following regex is supposed to capture a class name in a line like this:
-        # media (:obj:`str` | :class:`telegram.InputFile`): Audio file to send.
-        #
-        # Note that even if such typing description spans over multiple lines but each line ends
-        # with a backslash (otherwise Sphinx will throw an error)
-        # (e.g. EncryptedPassportElement.data), then Sphinx will combine these lines into a single
-        # line automatically, and it will contain no backslash (only some extra many whitespaces
-        # from the indentation).
-
-        attr_docstr_pattern = re.compile(
-            r"^\s*(?P<attr_name>[a-z_]+)"  # Any number of spaces, named group for attribute
-            r"\s?\("  # Optional whitespace, opening parenthesis
-            r".*"  # Any number of characters (that could denote a built-in type)
-            r":class:`.+`"  # Marker of a classref, class name in backticks
-            r".*\):"  # Any number of characters, closing parenthesis, colon.
-            # The ^ colon above along with parenthesis is important because it makes sure that
-            # the class is mentioned in the attribute description, not in free text.
-            r".*$",  # Any number of characters, end of string (end of line)
-            re.VERBOSE,
-        )
-
-        # for properties: there is no attr name in docstring.  Just check if there's a class name.
-        prop_docstring_pattern = re.compile(r":class:`.+`.*:")
-
-        # pattern for iterating over potentially many class names in docstring for one attribute.
-        # Tilde is optional (sometimes it is in the docstring, sometimes not).
-        single_class_name_pattern = re.compile(r":class:`~?(?P<class_name>[\w.]*)`")
-
-        classes_to_inspect = inspect.getmembers(telegram, inspect.isclass) + inspect.getmembers(
-            telegram.ext, inspect.isclass
-        )
-
-        for _class_name, inspected_class in classes_to_inspect:
-            # We need to make "<class 'telegram._files.sticker.StickerSet'>" into
-            # "telegram.StickerSet" because that's the way the classes are mentioned in
-            # docstrings.
-            name_of_inspected_class_in_docstr = self._generate_class_name_for_link(inspected_class)
-
-            # Parsing part of the docstring with attributes (parsing of properties follows later)
-            docstring_lines = inspect.getdoc(inspected_class).splitlines()
-            lines_with_attrs = []
-            for idx, line in enumerate(docstring_lines):
-                if line.strip() == "Attributes:":
-                    lines_with_attrs = docstring_lines[idx + 1 :]
-                    break
-
-            for line in lines_with_attrs:
-                if not (line_match := attr_docstr_pattern.match(line)):
-                    continue
-
-                target_attr = line_match.group("attr_name")
-                # a typing description of one attribute can contain multiple classes
-                for match in single_class_name_pattern.finditer(line):
-                    name_of_class_in_attr = match.group("class_name")
-
-                    # Writing to dictionary: matching the class found in the docstring
-                    # and its subclasses to the attribute of the class being inspected.
-                    # The class in the attribute docstring (or its subclass) is the key,
-                    # ReST link to attribute of the class currently being inspected is the value.
-                    try:
-                        self._resolve_arg_and_add_link(
-                            arg=name_of_class_in_attr,
-                            dict_of_methods_for_class=attrs_for_class,
-                            link=f":attr:`{name_of_inspected_class_in_docstr}.{target_attr}`",
-                        )
-                    except NotImplementedError as e:
-                        raise NotImplementedError(
-                            "Error generating Sphinx 'Available in' admonition "
-                            f"(admonition_inserter.py). Class {name_of_class_in_attr} present in "
-                            f"attribute {target_attr} of class {name_of_inspected_class_in_docstr}"
-                            f" could not be resolved. {e!s}"
-                        ) from e
-
-            # Properties need to be parsed separately because they act like attributes but not
-            # listed as attributes.
-            properties = inspect.getmembers(inspected_class, lambda o: isinstance(o, property))
-            for prop_name, _ in properties:
-                # Make sure this property is really defined in the class being inspected.
-                # A property can be inherited from a parent class, then a link to it will not work.
-                if prop_name not in inspected_class.__dict__:
-                    continue
-
-                # 1. Can't use typing.get_type_hints because double-quoted type hints
-                #    (like "Application") will throw a NameError
-                # 2. Can't use inspect.signature because return annotations of properties can be
-                #    hard to parse (like "(self) -> BD").
-                # 3. fget is used to access the actual function under the property wrapper
-                docstring = inspect.getdoc(getattr(inspected_class, prop_name).fget)
-                if docstring is None:
-                    continue
-
-                first_line = docstring.splitlines()[0]
-                if not prop_docstring_pattern.match(first_line):
-                    continue
-
-                for match in single_class_name_pattern.finditer(first_line):
-                    name_of_class_in_prop = match.group("class_name")
-
-                    # Writing to dictionary: matching the class found in the docstring and its
-                    # subclasses to the property of the class being inspected.
-                    # The class in the property docstring (or its subclass) is the key,
-                    # ReST link to property of the class currently being inspected is the value.
-                    try:
-                        self._resolve_arg_and_add_link(
-                            arg=name_of_class_in_prop,
-                            dict_of_methods_for_class=attrs_for_class,
-                            link=f":attr:`{name_of_inspected_class_in_docstr}.{prop_name}`",
-                        )
-                    except NotImplementedError as e:
-                        raise NotImplementedError(
-                            "Error generating Sphinx 'Available in' admonition "
-                            f"(admonition_inserter.py). Class {name_of_class_in_prop} present in "
-                            f"property {prop_name} of class {name_of_inspected_class_in_docstr}"
-                            f" could not be resolved. {e!s}"
-                        ) from e
-
-        return self._generate_admonitions(attrs_for_class, admonition_type="available_in")
-
-    def _create_returned_in(self) -> dict[type, str]:
-        """Creates a dictionary with 'Returned in' admonitions for classes that are returned
-        in Bot's and ApplicationBuilder's methods.
-        """
-
-        # Generate a mapping of classes to ReST links to Bot methods which return it,
-        # i.e. {<class 'telegram._message.Message'>: {:meth:`telegram.Bot.send_message`, ...}}
-        methods_for_class = defaultdict(set)
-
-        for cls, method_names in self.METHOD_NAMES_FOR_BOT_AND_APPBUILDER.items():
-            for method_name in method_names:
-                sig = inspect.signature(getattr(cls, method_name))
-                ret_annot = sig.return_annotation
-
-                method_link = self._generate_link_to_method(method_name, cls)
-
-                try:
-                    self._resolve_arg_and_add_link(
-                        arg=ret_annot,
-                        dict_of_methods_for_class=methods_for_class,
-                        link=method_link,
-                    )
-                except NotImplementedError as e:
-                    raise NotImplementedError(
-                        "Error generating Sphinx 'Returned in' admonition "
-                        f"(admonition_inserter.py). {cls}, method {method_name}. "
-                        f"Couldn't resolve type hint in return annotation {ret_annot}. {e!s}"
-                    ) from e
-
-        return self._generate_admonitions(methods_for_class, admonition_type="returned_in")
-
-    def _create_shortcuts(self) -> dict[collections.abc.Callable, str]:
-        """Creates a dictionary with 'Shortcuts' admonitions for Bot methods that
-        have shortcuts in other classes.
-        """
-
-        # pattern for looking for calls to Bot methods only
-        bot_method_pattern = re.compile(
-            r"""\s*  # any number of whitespaces
-            (?<=return\sawait\sself\.get_bot\(\)\.)  # lookbehind
-            \w+  # the method name we are looking for, letters/underscores
-            (?=\() # lookahead: opening bracket before the args of the method start
-            """,
-            re.VERBOSE,
-        )
-
-        # Generate a mapping of methods of classes to links to Bot methods which they are shortcuts
-        # for, i.e. {<function Bot.send_voice at ...>: {:meth:`telegram.User.send_voice`, ...}
-        shortcuts_for_bot_method = defaultdict(set)
-
-        # inspect methods of all telegram classes for return statements that indicate
-        # that this given method is a shortcut for a Bot method
-        for _class_name, cls in inspect.getmembers(telegram, predicate=inspect.isclass):
-            # no need to inspect Bot's own methods, as Bot can't have shortcuts in Bot
-            if cls is telegram.Bot:
-                continue
-
-            for method_name, method in _iter_own_public_methods(cls):
-                # .getsourcelines() returns a tuple. Item [1] is an int
-                for line in inspect.getsourcelines(method)[0]:
-                    if not (bot_method_match := bot_method_pattern.search(line)):
-                        continue
-
-                    bot_method = getattr(telegram.Bot, bot_method_match.group())
-
-                    link_to_shortcut_method = self._generate_link_to_method(method_name, cls)
-
-                    shortcuts_for_bot_method[bot_method].add(link_to_shortcut_method)
-
-        return self._generate_admonitions(shortcuts_for_bot_method, admonition_type="shortcuts")
-
-    def _create_use_in(self) -> dict[type, str]:
-        """Creates a dictionary with 'Use in' admonitions for classes whose instances are
-        accepted as arguments for Bot's and ApplicationBuilder's methods.
-        """
-
-        # Generate a mapping of classes to links to Bot methods which accept them as arguments,
-        # i.e. {<class 'telegram._inline.inlinequeryresult.InlineQueryResult'>:
-        # {:meth:`telegram.Bot.answer_inline_query`, ...}}
-        methods_for_class = defaultdict(set)
-
-        for cls, method_names in self.METHOD_NAMES_FOR_BOT_AND_APPBUILDER.items():
-            for method_name in method_names:
-                method_link = self._generate_link_to_method(method_name, cls)
-
-                sig = inspect.signature(getattr(cls, method_name))
-                parameters = sig.parameters
-
-                for param in parameters.values():
-                    try:
-                        self._resolve_arg_and_add_link(
-                            arg=param.annotation,
-                            dict_of_methods_for_class=methods_for_class,
-                            link=method_link,
-                        )
-                    except NotImplementedError as e:
-                        raise NotImplementedError(
-                            "Error generating Sphinx 'Use in' admonition "
-                            f"(admonition_inserter.py). {cls}, method {method_name}, parameter "
-                            f"{param}: Couldn't resolve type hint {param.annotation}. {e!s}"
-                        ) from e
-
-        return self._generate_admonitions(methods_for_class, admonition_type="use_in")
-
-    @staticmethod
-    def _find_insert_pos_for_admonition(lines: list[str]) -> int:
-        """Finds the correct position to insert the class admonition and returns the index.
-
-        The admonition will be insert above "See also", "Examples:", version added/changed notes
-        and args, whatever comes first.
-
-        If no key phrases are found, the admonition will be inserted at the very end.
-        """
-        for idx, value in list(enumerate(lines)):
-            if value.startswith(
-                (
-                    ".. seealso:",
-                    # The docstring contains heading "Examples:", but Sphinx will have it converted
-                    # to ".. admonition: Examples":
-                    ".. admonition:: Examples",
-                    ".. version",
-                    # The space after ":param" is important because docstring can contain
-                    # ":paramref:" in its plain text in the beginning of a line (e.g. ExtBot):
-                    ":param ",
-                    # some classes (like "Credentials") have no params, so insert before attrs:
-                    ".. attribute::",
-                )
-            ):
-                return idx
-        return len(lines) - 1
-
-    def _generate_admonitions(
-        self,
-        attrs_or_methods_for_class: dict[type, set[str]],
-        admonition_type: str,
-    ) -> dict[type, str]:
-        """Generates admonitions of a given type.
-        Takes a dictionary of classes matched to ReST links to methods or attributes, e.g.:
-
-        ```
-        {<class 'telegram._files.sticker.StickerSet'>:
-        [":meth: `telegram.Bot.get_sticker_set`", ...]}.
-        ```
-
-        Returns a dictionary of classes matched to full admonitions, e.g.
-        for `admonition_type` "returned_in" (note that title and CSS class are generated
-        automatically):
-
-        ```
-        {<class 'telegram._files.sticker.StickerSet'>:
-        ".. admonition:: Returned in:
-            :class: returned-in
-
-            :meth: `telegram.Bot.get_sticker_set`"}.
-        ```
-        """
-
-        if admonition_type not in self.ALL_ADMONITION_TYPES:
-            raise TypeError(f"Admonition type {admonition_type} not supported.")
-
-        admonition_for_class = {}
-
-        for cls, attrs in attrs_or_methods_for_class.items():
-            if cls is telegram.ext.ApplicationBuilder:
-                # ApplicationBuilder is only used in and returned from its own methods,
-                # so its page needs no admonitions.
-                continue
-
-            sorted_attrs = sorted(attrs)
-
-            # e.g. for admonition type "use_in" the title will be "Use in" and CSS class "use-in".
-            admonition = f"""
-
-.. admonition:: {admonition_type.title().replace("_", " ")}
-    :class: {admonition_type.replace("_", "-")}
-    """
-            if len(sorted_attrs) > 1:
-                for target_attr in sorted_attrs:
-                    admonition += "\n    * " + target_attr
-            else:
-                admonition += f"\n    {sorted_attrs[0]}"
-
-            admonition += "\n    "  # otherwise an unexpected unindent warning will be issued
-            admonition_for_class[cls] = admonition
-
-        return admonition_for_class
-
-    @staticmethod
-    def _generate_class_name_for_link(cls: type) -> str:
-        """Generates class name that can be used in a ReST link."""
-
-        # Check for potential presence of ".ext.", we will need to keep it.
-        ext = ".ext" if ".ext." in str(cls) else ""
-        return f"telegram{ext}.{cls.__name__}"
-
-    def _generate_link_to_method(self, method_name: str, cls: type) -> str:
-        """Generates a ReST link to a method of a telegram class."""
-
-        return f":meth:`{self._generate_class_name_for_link(cls)}.{method_name}`"
-
-    @staticmethod
-    def _iter_subclasses(cls: type) -> Iterator:
-        return (
-            # exclude private classes
-            c
-            for c in cls.__subclasses__()
-            if not str(c).split(".")[-1].startswith("_")
-        )
-
-    def _resolve_arg_and_add_link(
-        self,
-        arg: Any,
-        dict_of_methods_for_class: defaultdict,
-        link: str,
-    ) -> None:
-        """A helper method. Tries to resolve the arg into a valid class. In case of success,
-        adds the link (to a method, attribute, or property) for that class' and its subclasses'
-        sets of links in the dictionary of admonitions.
-
-        **Modifies dictionary in place.**
-        """
-        for cls in self._resolve_arg(arg):
-            # When trying to resolve an argument from args or return annotation,
-            # the method _resolve_arg returns None if nothing could be resolved.
-            # Also, if class was resolved correctly, "telegram" will definitely be in its str().
-            if cls is None or "telegram" not in str(cls):
-                continue
-
-            dict_of_methods_for_class[cls].add(link)
-
-            for subclass in self._iter_subclasses(cls):
-                dict_of_methods_for_class[subclass].add(link)
-
-    def _resolve_arg(self, arg: Any) -> Iterator[Union[type, None]]:
-        """Analyzes an argument of a method and recursively yields classes that the argument
-        or its sub-arguments (in cases like Union[...]) belong to, if they can be resolved to
-        telegram or telegram.ext classes.
-
-        Raises `NotImplementedError`.
-        """
-
-        origin = typing.get_origin(arg)
-
-        if (
-            origin in (collections.abc.Callable, typing.IO)
-            or arg is None
-            # no other check available (by type or origin) for these:
-            or str(type(arg)) in ("<class 'typing._SpecialForm'>", "<class 'ellipsis'>")
-        ):
-            pass
-
-        # RECURSIVE CALLS
-        # for cases like Union[Sequence....
-        elif origin in (
-            Union,
-            collections.abc.Coroutine,
-            collections.abc.Sequence,
-        ):
-            for sub_arg in typing.get_args(arg):
-                yield from self._resolve_arg(sub_arg)
-
-        elif isinstance(arg, typing.TypeVar):
-            # gets access to the "bound=..." parameter
-            yield from self._resolve_arg(arg.__bound__)
-        # END RECURSIVE CALLS
-
-        elif isinstance(arg, typing.ForwardRef):
-            m = self.FORWARD_REF_PATTERN.match(str(arg))
-            # We're sure it's a ForwardRef, so, unless it belongs to known exceptions,
-            # the class must be resolved.
-            # If it isn't resolved, we'll have the program throw an exception to be sure.
-            try:
-                cls = self._resolve_class(m.group("class_name"))
-            except AttributeError as exc:
-                # skip known ForwardRef's that need not be resolved to a Telegram class
-                if self.FORWARD_REF_SKIP_PATTERN.match(str(arg)):
-                    pass
-                else:
-                    raise NotImplementedError(f"Could not process ForwardRef: {arg}") from exc
-            else:
-                yield cls
-
-        # For custom generics like telegram.ext._application.Application[~BT, ~CCT, ~UD...].
-        # This must come before the check for isinstance(type) because GenericAlias can also be
-        # recognized as type if it belongs to <class 'types.GenericAlias'>.
-        elif str(type(arg)) in (
-            "<class 'typing._GenericAlias'>",
-            "<class 'types.GenericAlias'>",
-            "<class 'typing._LiteralGenericAlias'>",
-        ):
-            if "telegram" in str(arg):
-                # get_origin() of telegram.ext._application.Application[~BT, ~CCT, ~UD...]
-                # will produce <class 'telegram.ext._application.Application'>
-                yield origin
-
-        elif isinstance(arg, type):
-            if "telegram" in str(arg):
-                yield arg
-
-        # For some reason "InlineQueryResult", "InputMedia" & some others are currently not
-        # recognized as ForwardRefs and are identified as plain strings.
-        elif isinstance(arg, str):
-            # args like "ApplicationBuilder[BT, CCT, UD, CD, BD, JQ]" can be recognized as strings.
-            # Remove whatever is in the square brackets because it doesn't need to be parsed.
-            arg = re.sub(r"\[.+]", "", arg)
-
-            cls = self._resolve_class(arg)
-            # Here we don't want an exception to be thrown since we're not sure it's ForwardRef
-            if cls is not None:
-                yield cls
-
-        else:
-            raise NotImplementedError(
-                f"Cannot process argument {arg} of type {type(arg)} (origin {origin})"
-            )
-
-    @staticmethod
-    def _resolve_class(name: str) -> Union[type, None]:
-        """The keys in the admonitions dictionary are not strings like "telegram.StickerSet"
-        but classes like <class 'telegram._files.sticker.StickerSet'>.
-
-        This method attempts to resolve a PTB class from a name that does or does not
-        contain the word 'telegram', e.g.
-        <class 'telegram._files.sticker.StickerSet'> from "telegram.StickerSet" or "StickerSet".
-
-        Returns a class on success, :obj:`None` if nothing could be resolved.
-        """
-
-        for option in (
-            name,
-            f"telegram.{name}",
-            f"telegram.ext.{name}",
-            f"telegram.ext.filters.{name}",
-        ):
-            try:
-                return eval(option)
-            # NameError will be raised if trying to eval just name and it doesn't work, e.g.
-            # "Name 'ApplicationBuilder' is not defined".
-            # AttributeError will be raised if trying to e.g. eval f"telegram.{name}" when the
-            # class denoted by `name` actually belongs to `telegram.ext`:
-            # "module 'telegram' has no attribute 'ApplicationBuilder'".
-            # If neither option works, this is not a PTB class.
-            except (NameError, AttributeError):
-                continue
-        return None
-
-
-if __name__ == "__main__":
-    # just try instantiating for debugging purposes
-    AdmonitionInserter()

docs/auxil/kwargs_insertion.py

@@ -1,109 +0,0 @@
-#
-#  A library that provides a Python interface to the Telegram Bot API
-#  Copyright (C) 2015-2024
-#  Leandro Toledo de Souza <devs@python-telegram-bot.org>
-#
-#  This program is free software: you can redistribute it and/or modify
-#  it under the terms of the GNU Lesser Public License as published by
-#  the Free Software Foundation, either version 3 of the License, or
-#  (at your option) any later version.
-#
-#  This program is distributed in the hope that it will be useful,
-#  but WITHOUT ANY WARRANTY; without even the implied warranty of
-#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-#  GNU Lesser Public License for more details.
-#
-#  You should have received a copy of the GNU Lesser Public License
-#  along with this program.  If not, see [http://www.gnu.org/licenses/].
-import inspect
-from typing import List
-
-keyword_args = [
-    "Keyword Arguments:",
-    (
-        "    read_timeout (:obj:`float` | :obj:`None`, optional): Value to pass to "
-        "        :paramref:`telegram.request.BaseRequest.post.read_timeout`. Defaults to "
-        "        :attr:`~telegram.request.BaseRequest.DEFAULT_NONE`. "
-    ),
-    (
-        "    write_timeout (:obj:`float` | :obj:`None`, optional): Value to pass to "
-        "        :paramref:`telegram.request.BaseRequest.post.write_timeout`. Defaults to "
-        "        :attr:`~telegram.request.BaseRequest.DEFAULT_NONE`."
-    ),
-    (
-        "    connect_timeout (:obj:`float` | :obj:`None`, optional): Value to pass to "
-        "        :paramref:`telegram.request.BaseRequest.post.connect_timeout`. Defaults to "
-        "        :attr:`~telegram.request.BaseRequest.DEFAULT_NONE`."
-    ),
-    (
-        "    pool_timeout (:obj:`float` | :obj:`None`, optional): Value to pass to "
-        "        :paramref:`telegram.request.BaseRequest.post.pool_timeout`. Defaults to "
-        "        :attr:`~telegram.request.BaseRequest.DEFAULT_NONE`."
-    ),
-    (
-        "    api_kwargs (:obj:`dict`, optional): Arbitrary keyword arguments"
-        "        to be passed to the Telegram API. See :meth:`~telegram.Bot.do_api_request` for"
-        "        limitations."
-    ),
-    "",
-]
-
-media_write_timeout_deprecation_methods = [
-    "send_photo",
-    "send_audio",
-    "send_document",
-    "send_sticker",
-    "send_video",
-    "send_video_note",
-    "send_animation",
-    "send_voice",
-    "send_media_group",
-    "set_chat_photo",
-    "upload_sticker_file",
-    "add_sticker_to_set",
-    "create_new_sticker_set",
-]
-media_write_timeout_deprecation = [
-    "    write_timeout (:obj:`float` | :obj:`None`, optional): Value to pass to "
-    "        :paramref:`telegram.request.BaseRequest.post.write_timeout`. By default, ``20`` "
-    "        seconds are used as write timeout."
-    "",
-    "",
-    "       .. deprecated:: 20.7",
-    "           In future versions, the default value will be changed to "
-    "           :attr:`~telegram.request.BaseRequest.DEFAULT_NONE`.",
-    "",
-    "",
-]
-get_updates_read_timeout_addition = [
-    "        :paramref:`timeout` will be added to this value.",
-    "",
-    "",
-    "        .. versionchanged:: 20.7",
-    "           Defaults to :attr:`~telegram.request.BaseRequest.DEFAULT_NONE` instead of ",
-    "           ``2``.",
-]
-
-
-def find_insert_pos_for_kwargs(lines: List[str]) -> int:
-    """Finds the correct position to insert the keyword arguments and returns the index."""
-    for idx, value in reversed(list(enumerate(lines))):  # reversed since :returns: is at the end
-        if value.startswith("Returns"):
-            return idx
-    return False
-
-
-def check_timeout_and_api_kwargs_presence(obj: object) -> int:
-    """Checks if the method has timeout and api_kwargs keyword only parameters."""
-    sig = inspect.signature(obj)
-    params_to_check = (
-        "read_timeout",
-        "write_timeout",
-        "connect_timeout",
-        "pool_timeout",
-        "api_kwargs",
-    )
-    return all(
-        param in sig.parameters and sig.parameters[param].kind == inspect.Parameter.KEYWORD_ONLY
-        for param in params_to_check
-    )

docs/auxil/link_code.py

@@ -1,79 +0,0 @@
-#
-#  A library that provides a Python interface to the Telegram Bot API
-#  Copyright (C) 2015-2024
-#  Leandro Toledo de Souza <devs@python-telegram-bot.org>
-#
-#  This program is free software: you can redistribute it and/or modify
-#  it under the terms of the GNU Lesser Public License as published by
-#  the Free Software Foundation, either version 3 of the License, or
-#  (at your option) any later version.
-#
-#  This program is distributed in the hope that it will be useful,
-#  but WITHOUT ANY WARRANTY; without even the implied warranty of
-#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-#  GNU Lesser Public License for more details.
-#
-#  You should have received a copy of the GNU Lesser Public License
-#  along with this program.  If not, see [http://www.gnu.org/licenses/].
-"""Functionality in this file is used for getting the [source] links on the classes, methods etc
-to link to the correct files & lines on github. Can be simplified once
-https://github.com/sphinx-doc/sphinx/issues/1556 is closed
-"""
-import subprocess
-from pathlib import Path
-from typing import Dict, Tuple
-
-from sphinx.util import logging
-
-# get the sphinx(!) logger
-# Makes sure logs render in red and also plays nicely with e.g. the `nitpicky` option.
-sphinx_logger = logging.getLogger(__name__)
-
-
-# must be a module-level variable so that it can be written to by the `autodoc-process-docstring`
-# event handler in `sphinx_hooks.py`
-LINE_NUMBERS: Dict[str, Tuple[Path, int, int]] = {}
-
-
-def _git_branch() -> str:
-    """Get's the current git sha if available or fall back to `master`"""
-    try:
-        output = subprocess.check_output(
-            ["git", "describe", "--tags", "--always"], stderr=subprocess.STDOUT
-        )
-        return output.decode().strip()
-    except Exception as exc:
-        sphinx_logger.exception(
-            "Failed to get a description of the current commit. Falling back to `master`.",
-            exc_info=exc,
-        )
-        return "master"
-
-
-git_branch = _git_branch()
-base_url = "https://github.com/python-telegram-bot/python-telegram-bot/blob/"
-
-
-def linkcode_resolve(_, info) -> str:
-    """See www.sphinx-doc.org/en/master/usage/extensions/linkcode.html"""
-    combined = ".".join((info["module"], info["fullname"]))
-    # special casing for ExtBot which is due to the special structure of extbot.rst
-    combined = combined.replace("ExtBot.ExtBot", "ExtBot")
-
-    line_info = LINE_NUMBERS.get(combined)
-
-    if not line_info:
-        # Try the __init__
-        line_info = LINE_NUMBERS.get(f"{combined.rsplit('.', 1)[0]}.__init__")
-    if not line_info:
-        # Try the class
-        line_info = LINE_NUMBERS.get(f"{combined.rsplit('.', 1)[0]}")
-    if not line_info:
-        # Try the module
-        line_info = LINE_NUMBERS.get(info["module"])
-
-    if not line_info:
-        return None
-
-    file, start_line, end_line = line_info
-    return f"{base_url}{git_branch}/{file}#L{start_line}-L{end_line}"

docs/auxil/sphinx_hooks.py

@@ -1,216 +0,0 @@
-#
-#  A library that provides a Python interface to the Telegram Bot API
-#  Copyright (C) 2015-2024
-#  Leandro Toledo de Souza <devs@python-telegram-bot.org>
-#
-#  This program is free software: you can redistribute it and/or modify
-#  it under the terms of the GNU Lesser Public License as published by
-#  the Free Software Foundation, either version 3 of the License, or
-#  (at your option) any later version.
-#
-#  This program is distributed in the hope that it will be useful,
-#  but WITHOUT ANY WARRANTY; without even the implied warranty of
-#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-#  GNU Lesser Public License for more details.
-#
-#  You should have received a copy of the GNU Lesser Public License
-#  along with this program.  If not, see [http://www.gnu.org/licenses/].
-import collections.abc
-import inspect
-import re
-import typing
-from pathlib import Path
-
-from sphinx.application import Sphinx
-
-import telegram
-import telegram.ext
-from docs.auxil.admonition_inserter import AdmonitionInserter
-from docs.auxil.kwargs_insertion import (
-    check_timeout_and_api_kwargs_presence,
-    find_insert_pos_for_kwargs,
-    get_updates_read_timeout_addition,
-    keyword_args,
-    media_write_timeout_deprecation,
-    media_write_timeout_deprecation_methods,
-)
-from docs.auxil.link_code import LINE_NUMBERS
-
-ADMONITION_INSERTER = AdmonitionInserter()
-
-# Some base classes are implementation detail
-# We want to instead show *their* base class
-PRIVATE_BASE_CLASSES = {
-    "_ChatUserBaseFilter": "MessageFilter",
-    "_Dice": "MessageFilter",
-    "_BaseThumbedMedium": "TelegramObject",
-    "_BaseMedium": "TelegramObject",
-    "_CredentialsBase": "TelegramObject",
-    "_ChatBase": "TelegramObject",
-}
-
-
-FILE_ROOT = Path(inspect.getsourcefile(telegram)).parent.parent.resolve()
-
-
-def autodoc_skip_member(app, what, name, obj, skip, options):
-    """We use this to not document certain members like filter() or check_update() for filters.
-    See https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#skipping-members"""
-
-    included = {"MessageFilter", "UpdateFilter"}  # filter() and check_update() only for these.
-    included_in_obj = any(inc in repr(obj) for inc in included)
-
-    if included_in_obj:  # it's difficult to see if check_update is from an inherited-member or not
-        for frame in inspect.stack():  # From https://github.com/sphinx-doc/sphinx/issues/9533
-            if frame.function == "filter_members":
-                docobj = frame.frame.f_locals["self"].object
-                if not any(inc in str(docobj) for inc in included) and name == "check_update":
-                    return True
-                break
-
-    if name == "filter" and obj.__module__ == "telegram.ext.filters" and not included_in_obj:
-        return True  # return True to exclude from docs.
-    return None
-
-
-def autodoc_process_docstring(
-    app: Sphinx, what, name: str, obj: object, options, lines: list[str]
-):
-    """We do the following things:
-    1) Use this method to automatically insert the Keyword Args and "Shortcuts" admonitions
-       for the Bot methods.
-
-    2) Use this method to automatically insert "Returned in" admonition into classes
-       that are returned from the Bot methods
-
-    3) Use this method to automatically insert "Available in" admonition into classes
-       whose instances are available as attributes of other classes
-
-    4) Use this method to automatically insert "Use in" admonition into classes
-       whose instances can be used as arguments of the Bot methods
-
-    5) Misuse this autodoc hook to get the file names & line numbers because we have access
-       to the actual object here.
-    """
-
-    # 1) Insert the Keyword Args and "Shortcuts" admonitions for the Bot methods
-    method_name = name.split(".")[-1]
-    if (
-        name.startswith("telegram.Bot.")
-        and what == "method"
-        and method_name.islower()
-        and check_timeout_and_api_kwargs_presence(obj)
-    ):
-        insert_index = find_insert_pos_for_kwargs(lines)
-        if not insert_index:
-            raise ValueError(
-                f"Couldn't find the correct position to insert the keyword args for {obj}."
-            )
-
-        get_updates: bool = method_name == "get_updates"
-        # The below can be done in 1 line with itertools.chain, but this must be modified in-place
-        insert_idx = insert_index
-        for i in range(insert_index, insert_index + len(keyword_args)):
-            to_insert = keyword_args[i - insert_index]
-
-            if (
-                "post.write_timeout`. Defaults to" in to_insert
-                and method_name in media_write_timeout_deprecation_methods
-            ):
-                effective_insert: list[str] = media_write_timeout_deprecation
-            elif get_updates and to_insert.lstrip().startswith("read_timeout"):
-                effective_insert = [to_insert, *get_updates_read_timeout_addition]
-            else:
-                effective_insert = [to_insert]
-
-            lines[insert_idx:insert_idx] = effective_insert
-            insert_idx += len(effective_insert)
-
-        ADMONITION_INSERTER.insert_admonitions(
-            obj=typing.cast(collections.abc.Callable, obj),
-            docstring_lines=lines,
-        )
-
-    # 2-4) Insert "Returned in", "Available in", "Use in" admonitions into classes
-    # (where applicable)
-    if what == "class":
-        ADMONITION_INSERTER.insert_admonitions(
-            obj=typing.cast(type, obj),  # since "what" == class, we know it's not just object
-            docstring_lines=lines,
-        )
-
-    # 5) Get the file names & line numbers
-    # We can't properly handle ordinary attributes.
-    # In linkcode_resolve we'll resolve to the `__init__` or module instead
-    if what == "attribute":
-        return
-
-    # Special casing for properties
-    if hasattr(obj, "fget"):
-        obj = obj.fget
-
-    # Special casing for filters
-    if isinstance(obj, telegram.ext.filters.BaseFilter):
-        obj = obj.__class__
-
-    try:
-        source_lines, start_line = inspect.getsourcelines(obj)
-        end_line = start_line + len(source_lines)
-        file = Path(inspect.getsourcefile(obj)).relative_to(FILE_ROOT)
-        LINE_NUMBERS[name] = (file, start_line, end_line)
-    except Exception:
-        pass
-
-    # Since we don't document the `__init__`, we call this manually to have it available for
-    # attributes -- see the note above
-    if what == "class":
-        autodoc_process_docstring(app, "method", f"{name}.__init__", obj.__init__, options, lines)
-
-
-def autodoc_process_bases(app, name, obj, option, bases: list) -> None:
-    """Here we fine tune how the base class's classes are displayed."""
-    for idx, raw_base in enumerate(bases):
-        # let's use a string representation of the object
-        base = str(raw_base)
-
-        # Special case for abstract context managers which are wrongly resoled for some reason
-        if base.startswith("typing.AbstractAsyncContextManager"):
-            bases[idx] = ":class:`contextlib.AbstractAsyncContextManager`"
-            continue
-
-        # Special case because base classes are in std lib:
-        if "StringEnum" in base == "<enum 'StringEnum'>":
-            bases[idx] = ":class:`enum.Enum`"
-            bases.insert(0, ":class:`str`")
-            continue
-
-        if "IntEnum" in base:
-            bases[idx] = ":class:`enum.IntEnum`"
-            continue
-
-        # Drop generics (at least for now)
-        if base.endswith("]"):
-            base = base.split("[", maxsplit=1)[0]
-            bases[idx] = f":class:`{base}`"
-
-        # Now convert `telegram._message.Message` to `telegram.Message` etc
-        if (
-            not (match := re.search(pattern=r"(telegram(\.ext|))\.[_\w\.]+", string=base))
-            or "_utils" in base
-        ):
-            continue
-
-        parts = match.group(0).split(".")
-
-        # Remove private paths
-        for index, part in enumerate(parts):
-            if part.startswith("_"):
-                parts = parts[:index] + parts[-1:]
-                break
-
-        # Replace private base classes with their respective parent
-        parts = [PRIVATE_BASE_CLASSES.get(part, part) for part in parts]
-
-        base = ".".join(parts)
-
-        bases[idx] = f":class:`{base}`"

docs/auxil/tg_const_role.py

@@ -1,100 +0,0 @@
-#
-#  A library that provides a Python interface to the Telegram Bot API
-#  Copyright (C) 2015-2024
-#  Leandro Toledo de Souza <devs@python-telegram-bot.org>
-#
-#  This program is free software: you can redistribute it and/or modify
-#  it under the terms of the GNU Lesser Public License as published by
-#  the Free Software Foundation, either version 3 of the License, or
-#  (at your option) any later version.
-#
-#  This program is distributed in the hope that it will be useful,
-#  but WITHOUT ANY WARRANTY; without even the implied warranty of
-#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-#  GNU Lesser Public License for more details.
-#
-#  You should have received a copy of the GNU Lesser Public License
-#  along with this program.  If not, see [http://www.gnu.org/licenses/].
-import datetime
-from enum import Enum
-
-from docutils.nodes import Element
-from sphinx.domains.python import PyXRefRole
-from sphinx.environment import BuildEnvironment
-from sphinx.util import logging
-
-import telegram
-
-# get the sphinx(!) logger
-# Makes sure logs render in red and also plays nicely with e.g. the `nitpicky` option.
-sphinx_logger = logging.getLogger(__name__)
-
-CONSTANTS_ROLE = "tg-const"
-
-
-class TGConstXRefRole(PyXRefRole):
-    """This is a bit of Sphinx magic. We add a new role type called tg-const that allows us to
-    reference values from the `telegram.constants.module` while using the actual value as title
-    of the link.
-
-    Example:
-
-        :tg-const:`telegram.constants.MessageLimit.MAX_TEXT_LENGTH` renders as `4096` but links to
-        the constant.
-    """
-
-    def process_link(
-        self,
-        env: BuildEnvironment,
-        refnode: Element,
-        has_explicit_title: bool,
-        title: str,
-        target: str,
-    ) -> tuple[str, str]:
-        title, target = super().process_link(env, refnode, has_explicit_title, title, target)
-        try:
-            # We use `eval` to get the value of the expression. Maybe there are better ways to
-            # do this via importlib or so, but it does the job for now
-            value = eval(target)
-            # Maybe we need a better check if the target is actually from tg.constants
-            # for now checking if it's an Enum suffices since those are used nowhere else in PTB
-            if isinstance(value, Enum):
-                # Special casing for file size limits
-                if isinstance(value, telegram.constants.FileSizeLimit):
-                    return f"{int(value.value / 1e6)} MB", target
-                return repr(value.value), target
-            # Just for (Bot API) versions number auto add in constants:
-            if isinstance(value, str) and target in (
-                "telegram.constants.BOT_API_VERSION",
-                "telegram.__version__",
-            ):
-                return value, target
-            if isinstance(value, tuple) and target in (
-                "telegram.constants.BOT_API_VERSION_INFO",
-                "telegram.__version_info__",
-            ):
-                return str(value), target
-            if (
-                isinstance(value, datetime.datetime)
-                and value == telegram.constants.ZERO_DATE
-                and target in ("telegram.constants.ZERO_DATE",)
-            ):
-                return repr(value), target
-            sphinx_logger.warning(
-                "%s:%d: WARNING: Did not convert reference %s. :%s: is not supposed"
-                " to be used with this type of target.",
-                refnode.source,
-                refnode.line,
-                refnode.rawsource,
-                CONSTANTS_ROLE,
-            )
-            return title, target
-        except Exception as exc:
-            sphinx_logger.exception(
-                "%s:%d: WARNING: Did not convert reference %s due to an exception.",
-                refnode.source,
-                refnode.line,
-                refnode.rawsource,
-                exc_info=exc,
-            )
-            return title, target

docs/requirements-docs.txt

@@ -1,7 +1,3 @@
-sphinx==7.3.7
-furo==2024.5.6
-furo-sphinx-search @ git+https://github.com/harshil21/furo-sphinx-search@v0.2.0.1
-sphinx-paramlinks==0.6.0
-sphinxcontrib-mermaid==0.9.2
-sphinx-copybutton==0.5.2
-sphinx-inline-tabs==2023.4.21
+sphinx
+sphinx_rtd_theme
+sphinx-pypi-upload

docs/source/_static/style_admonitions.css

@@ -1,65 +0,0 @@
-:root {
-  --icon--shortcuts: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' fill='currentColor' class='bi bi-signpost' viewBox='0 0 16 16'%3E%3Cpath d='M7 1.414V4H2a1 1 0 0 0-1 1v4a1 1 0 0 0 1 1h5v6h2v-6h3.532a1 1 0 0 0 .768-.36l1.933-2.32a.5.5 0 0 0 0-.64L13.3 4.36a1 1 0 0 0-.768-.36H9V1.414a1 1 0 0 0-2 0zM12.532 5l1.666 2-1.666 2H2V5h10.532z'/%3E%3C/svg%3E");
-  --icon--returned-in: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' fill='currentColor' class='bi bi-arrow-return-right' viewBox='0 0 16 16'%3E%3Cpath fill-rule='evenodd' d='M1.5 1.5A.5.5 0 0 0 1 2v4.8a2.5 2.5 0 0 0 2.5 2.5h9.793l-3.347 3.346a.5.5 0 0 0 .708.708l4.2-4.2a.5.5 0 0 0 0-.708l-4-4a.5.5 0 0 0-.708.708L13.293 8.3H3.5A1.5 1.5 0 0 1 2 6.8V2a.5.5 0 0 0-.5-.5z'/%3E%3C/svg%3E");
-  --icon--available-in: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' fill='currentColor' class='bi bi-geo-fill' viewBox='0 0 16 16'%3E%3Cpath fill-rule='evenodd' d='M4 4a4 4 0 1 1 4.5 3.969V13.5a.5.5 0 0 1-1 0V7.97A4 4 0 0 1 4 3.999zm2.493 8.574a.5.5 0 0 1-.411.575c-.712.118-1.28.295-1.655.493a1.319 1.319 0 0 0-.37.265.301.301 0 0 0-.057.09V14l.002.008a.147.147 0 0 0 .016.033.617.617 0 0 0 .145.15c.165.13.435.27.813.395.751.25 1.82.414 3.024.414s2.273-.163 3.024-.414c.378-.126.648-.265.813-.395a.619.619 0 0 0 .146-.15.148.148 0 0 0 .015-.033L12 14v-.004a.301.301 0 0 0-.057-.09 1.318 1.318 0 0 0-.37-.264c-.376-.198-.943-.375-1.655-.493a.5.5 0 1 1 .164-.986c.77.127 1.452.328 1.957.594C12.5 13 13 13.4 13 14c0 .426-.26.752-.544.977-.29.228-.68.413-1.116.558-.878.293-2.059.465-3.34.465-1.281 0-2.462-.172-3.34-.465-.436-.145-.826-.33-1.116-.558C3.26 14.752 3 14.426 3 14c0-.599.5-1 .961-1.243.505-.266 1.187-.467 1.957-.594a.5.5 0 0 1 .575.411z'/%3E%3C/svg%3E");
-  --icon--use-in:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' fill='currentColor' class='bi bi-funnel' viewBox='0 0 16 16'%3E%3Cpath d='M1.5 1.5A.5.5 0 0 1 2 1h12a.5.5 0 0 1 .5.5v2a.5.5 0 0 1-.128.334L10 8.692V13.5a.5.5 0 0 1-.342.474l-3 1A.5.5 0 0 1 6 14.5V8.692L1.628 3.834A.5.5 0 0 1 1.5 3.5v-2zm1 .5v1.308l4.372 4.858A.5.5 0 0 1 7 8.5v5.306l2-.666V8.5a.5.5 0 0 1 .128-.334L13.5 3.308V2h-11z'/%3E%3C/svg%3E");
-}
-.admonition.shortcuts {
-  border-color: rgb(43, 155, 70);
-}
-.admonition.shortcuts > .admonition-title {
-  background-color: rgba(43, 155, 70, 0.1);
-  border-color: rgb(43, 155, 70);
-}
-.admonition.shortcuts > .admonition-title::before {
-  background-color: rgb(43, 155, 70);
-  -webkit-mask-image: var(--icon--shortcuts);
-  mask-image: var(--icon--shortcuts);
-}
-
-.admonition.returned-in {
-  border-color: rgb(230, 109, 15);
-}
-.admonition.returned-in > .admonition-title {
-  background-color: rgba(177, 108, 51, 0.1);
-  border-color: rgb(230, 109, 15);
-}
-.admonition.returned-in > .admonition-title::before {
-  background-color: rgb(230, 109, 15);
-  -webkit-mask-image: var(--icon--returned-in);
-  mask-image: var(--icon--returned-in);
-}
-
-.admonition.available-in {
-  border-color: rgb(183, 4, 215);
-}
-.admonition.available-in > .admonition-title {
-  background-color: rgba(165, 99, 177, 0.1);
-  border-color: rgb(183, 4, 215);
-}
-.admonition.available-in > .admonition-title::before {
-  background-color: rgb(183, 4, 215);
-  -webkit-mask-image: var(--icon--available-in);
-  mask-image: var(--icon--available-in);
-}
-
-.admonition.use-in {
-  border-color: rgb(203, 147, 1);
-}
-.admonition.use-in > .admonition-title {
-  background-color: rgba(176, 144, 60, 0.1);
-  border-color: rgb(203, 147, 1);
-}
-.admonition.use-in > .admonition-title::before {
-  background-color: rgb(203, 147, 1);
-  -webkit-mask-image: var(--icon--use-in);
-  mask-image: var(--icon--use-in);
-}
-
-.admonition.returned-in > ul:hover, .admonition.available-in > ul:hover, .admonition.use-in > ul:hover, .admonition.shortcuts > ul:hover {
-  cursor: move;
-}
-.admonition.returned-in > ul, .admonition.available-in > ul, .admonition.use-in > ul, .admonition.shortcuts > ul {
-  max-height: 200px;
-  overflow-y: scroll;
-}

docs/source/_static/style_external_link.css

@@ -1,5 +0,0 @@
-article a.reference.external:not([href*="/python-telegram-bot/blob/"])::after {
-      content: url('data:image/svg+xml,<svg width="12" height="12" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" stroke-width="1.5" stroke="%23607D8B" fill="none" stroke-linecap="round" stroke-linejoin="round"><path stroke="none" d="M0 0h24v24H0z"/><path d="M11 7h-5a2 2 0 0 0 -2 2v9a2 2 0 0 0 2 2h9a2 2 0 0 0 2 -2v-5" /><line x1="10" y1="14" x2="20" y2="4" /><polyline points="15 4 20 4 20 9" /></svg>');
-      margin: 0 0.25rem;
-      vertical-align: middle;
-}

docs/source/_static/style_general.css

@@ -1,3 +0,0 @@
-.article-container h1 {
-      overflow-wrap: anywhere;
-}

docs/source/_static/style_images.css

@@ -1,15 +0,0 @@
-figure > img {
-    height: 300px;  /* resize figures so they aren't too big */
-}
-
-@media (prefers-color-scheme: dark) {
-    body:not([data-theme="light"]) figure > img {  /* auto and dark is dark mode */
-        filter: invert(92%);
-    }
-}
-
-@media (prefers-color-scheme: light) {
-    body[data-theme="dark"] figure > img {  /* auto and light is light mode */
-        filter: invert(92%);
-    }
-}

docs/source/_static/style_mermaid_diagrams.css

@@ -1,3 +0,0 @@
-.mermaid svg {
-  height: auto;
-}

docs/source/_static/style_sidebar_brand.css

@@ -1,11 +0,0 @@
-.sidebar-sticky .sidebar-brand {
-      flex-direction: row;
-}
-
-.sidebar-sticky .sidebar-brand .sidebar-logo-container {
-      align-self: center;
-}
-
-.sidebar-sticky .sidebar-brand .sidebar-brand-text {
-      align-self: center;
-}

docs/source/changelog.rst

@@ -1 +0,0 @@
-.. include:: ../../CHANGES.rst

docs/source/coc.rst

@@ -1 +0,0 @@
-.. include:: ../../CODE_OF_CONDUCT.rst

docs/source/conf.py

@@ -1,291 +1,268 @@
-import re
+# -*- coding: utf-8 -*-
+#
+# Python Telegram Bot documentation build configuration file, created by
+# sphinx-quickstart on Mon Aug 10 22:25:07 2015.
+#
+# This file is execfile()d with the current directory set to its
+# containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
 import sys
-from pathlib import Path
+import os
+import shlex
+import telegram
 
 # If extensions (or modules to document with autodoc) are in another directory,
 # add these directories to sys.path here. If the directory is relative to the
 # documentation root, use os.path.abspath to make it absolute, like shown here.
-from sphinx.application import Sphinx
-
-sys.path.insert(0, str(Path("../..").resolve().absolute()))
+sys.path.insert(0, os.path.abspath('../..'))
 
 # -- General configuration ------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
+# ones.
+extensions = [
+    'sphinx.ext.autodoc',
+    'sphinx.ext.napoleon'
+]
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix(es) of source filenames.
+# You can specify multiple suffix as a list of string:
+# source_suffix = ['.rst', '.md']
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8-sig'
+
+# The master toctree document.
+master_doc = 'index'
+
 # General information about the project.
-project = "python-telegram-bot"
-copyright = "2015-2024, Leandro Toledo"
-author = "Leandro Toledo"
+project = u'Python Telegram Bot'
+copyright = u'2015-2016, Leandro Toledo'
+author = u'Leandro Toledo'
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
 # The short X.Y version.
-
-# Import needs to be below the sys.path.insert above
-import telegram  # noqa: E402
-
-version = telegram.__version__
+version = telegram.__version__[:3]
 # The full version, including alpha/beta/rc tags.
 release = telegram.__version__
 
-# If your documentation needs a minimal Sphinx version, state it here.
-needs_sphinx = "6.1.3"
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#
+# This is also used if you do content translation via gettext catalogs.
+# Usually you set "language" from the command line for these cases.
+language = None
 
-# Add any Sphinx extension module names here, as strings. They can be
-# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
-# ones.
-extensions = [
-    "sphinx.ext.autodoc",
-    "sphinx.ext.napoleon",
-    "sphinx.ext.intersphinx",
-    "sphinx.ext.linkcode",
-    "sphinx.ext.extlinks",
-    "sphinx_paramlinks",
-    "sphinx_copybutton",
-    "sphinx_inline_tabs",
-    "sphinxcontrib.mermaid",
-    "sphinx_search.extension",
-]
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+#today_fmt = '%B %d, %Y'
 
-# For shorter links to Wiki in docstrings
-extlinks = {
-    "wiki": ("https://github.com/python-telegram-bot/python-telegram-bot/wiki/%s", "%s"),
-    "pr": ("https://github.com/python-telegram-bot/python-telegram-bot/pull/%s", "#%s"),
-    "issue": ("https://github.com/python-telegram-bot/python-telegram-bot/issues/%s", "#%s"),
-}
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+exclude_patterns = []
 
-# Use intersphinx to reference the python builtin library docs
-intersphinx_mapping = {
-    "python": ("https://docs.python.org/3", None),
-    "APScheduler": ("https://apscheduler.readthedocs.io/en/3.x/", None),
-}
+# The reST default role (used for this markup: `text`) to use for all
+# documents.
+#default_role = None
 
-# Add any paths that contain templates here, relative to this directory.
-templates_path = ["_templates"]
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
 
-# The suffix(es) of source filenames.
-# You can specify multiple suffix as a list of string:
-source_suffix = ".rst"
-
-# The master toctree document.
-master_doc = "index"
-
-# Global substitutions
-rst_prolog = ""
-for file in Path.cwd().glob("../substitutions/*.rst"):
-    rst_prolog += "\n" + file.read_text(encoding="utf-8")
-
-# -- Extension settings ------------------------------------------------
-napoleon_use_admonition_for_examples = True
-
-# Don't show type hints in the signature - that just makes it hardly readable
-# and we document the types anyway
-autodoc_typehints = "none"
-
-# Show docstring for special members
-autodoc_default_options = {
-    "special-members": True,
-    # For some reason, __weakref__ can not be ignored by using "inherited-members" in all cases
-    # so we list it here.
-    "exclude-members": "__init__, __weakref__",
-}
-
-# Fail on warnings & unresolved references etc
-nitpicky = True
-
-# Paramlink style
-paramlinks_hyperlink_param = "name"
-
-# Linkcheck settings
-linkcheck_ignore = [
-    # Let's not check issue/PR links - that's wasted resources
-    r"http(s)://github\.com/python-telegram-bot/python-telegram-bot/(issues|pull)/\d+/?",
-    # For some reason linkcheck has a problem with these two:
-    re.escape("https://github.com/python-telegram-bot/python-telegram-bot/discussions/new"),
-    re.escape("https://github.com/python-telegram-bot/python-telegram-bot/issues/new"),
-    # Anchors are apparently inserted by GitHub dynamically, so let's skip checking them
-    "https://github.com/python-telegram-bot/python-telegram-bot/tree/master/examples#",
-    r"https://github\.com/python-telegram-bot/python-telegram-bot/wiki/[\w\-_,]+\#",
-]
-linkcheck_allowed_redirects = {
-    # Redirects to the default version are okay
-    r"https://docs\.python-telegram-bot\.org/.*": (
-        r"https://docs\.python-telegram-bot\.org/en/[\w\d\.]+/.*"
-    ),
-    # pre-commit.ci always redirects to the latest run
-    re.escape(
-        "https://results.pre-commit.ci/latest/github/python-telegram-bot/python-telegram-bot/master"
-    ): r"https://results\.pre-commit\.ci/run/github/.*",
-}
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
 
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
 
 # The name of the Pygments (syntax highlighting) style to use.
-pygments_style = "sphinx"
+pygments_style = 'sphinx'
 
-# Decides the language used for syntax highlighting of code blocks.
-highlight_language = "python3"
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+# If true, keep warnings as "system message" paragraphs in the built documents.
+#keep_warnings = False
 
 # If true, `todo` and `todoList` produce output, else they produce nothing.
 todo_include_todos = False
 
+
 # -- Options for HTML output ----------------------------------------------
 
 # The theme to use for HTML and HTML Help pages.  See the documentation for
 # a list of builtin themes.
-html_theme = "furo"
+html_theme = 'sphinx_rtd_theme'
 
 # Theme options are theme-specific and customize the look and feel of a theme
-# further. For a list of options available for each theme, see the documentation.
-html_theme_options = {
-    "navigation_with_keys": True,
-    "dark_css_variables": {
-        "admonition-title-font-size": "0.95rem",
-        "admonition-font-size": "0.92rem",
-    },
-    "light_css_variables": {
-        "admonition-title-font-size": "0.95rem",
-        "admonition-font-size": "0.92rem",
-    },
-    "footer_icons": [
-        {
-            # Telegram channel logo
-            "name": "Telegram Channel",
-            "url": "https://t.me/pythontelegrambotchannel/",
-            # Following svg is from https://react-icons.github.io/react-icons/search?q=telegram
-            "html": (
-                '<svg stroke="currentColor" fill="currentColor" stroke-width="0" '
-                'viewBox="0 0 16 16" height="1em" width="1em" xmlns="http://www.w3.org/2000/svg">'
-                '<path d="M16 8A8 8 0 1 1 0 8a8 8 0 0 1 16 0zM8.287 5.906c-.778.324-2.334.994'
-                "-4.666 2.01-.378.15-.577.298-.595.442-.03.243.275.339.69.47l.175.055c.408.133."
-                "958.288 1.243.294.26.006.549-.1.868-.32 2.179-1.471 3.304-2.214 3.374-2.23.0"
-                "5-.012.12-.026.166.016.047.041.042.12.037.141-.03.129-1.227 1.241-1.846 1.81"
-                "7-.193.18-.33.307-.358.336a8.154 8.154 0 0 1-.188.186c-.38.366-.664.64.015 1.08"
-                "8.327.216.589.393.85.571.284.194.568.387.936.629.093.06.183.125.27.187.331.23"
-                "6.63.448.997.414.214-.02.435-.22.547-.82.265-1.417.786-4.486.906-5.751a1.426 "
-                "1.426 0 0 0-.013-.315.337.337 0 0 0-.114-.217.526.526 0 0 0-.31-.093c-.3.005-.7"
-                '63.166-2.984 1.09z"></path></svg>'
-            ),
-            "class": "",
-        },
-        {  # Github logo
-            "name": "GitHub",
-            "url": "https://github.com/python-telegram-bot/python-telegram-bot/",
-            "html": (
-                '<svg stroke="currentColor" fill="currentColor" stroke-width="0" '
-                'viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8 0C3.58 0 0 3.58 0 8c0 3.54 '
-                "2.29 6.53 5.47 7.59.4.07.55-.17.55-.38 0-.19-.01-.82-.01-1.49-2.01.37-2.53-.4"
-                "9-2.69-.94-.09-.23-.48-.94-.82-1.13-.28-.15-.68-.52-.01-.53.63-.01 1.08.58 1.23"
-                ".82.72 1.21 1.87.87 2.33.66.07-.52.28-.87.51-1.07-1.78-.2-3.64-.89-3.64-3.95 "
-                "0-.87.31-1.59.82-2.15-.08-.2-.36-1.02.08-2.12 0 0 .67-.21 2.2.82.64-.18 1.32-.2"
-                "7 2-.27.68 0 1.36.09 2 .27 1.53-1.04 2.2-.82 2.2-.82.44 1.1.16 1.92.08 2.12.5"
-                "1.56.82 1.27.82 2.15 0 3.07-1.87 3.75-3.65 3.95.29.25.54.73.54 1.48 0 1.07-.01 "
-                '1.93-.01 2.2 0 .21.15.46.55.38A8.013 8.013 0 0 0 16 8c0-4.42-3.58-8-8-8z">'
-                "</path></svg>"
-            ),
-            "class": "",
-        },
-        {  # PTB website logo - globe
-            "name": "python-telegram-bot website",
-            "url": "https://python-telegram-bot.org/",
-            "html": (
-                '<svg stroke="currentColor" fill="currentColor" stroke-width="0" '
-                'viewBox="0 0 16 16" height="1em" width="1em" xmlns="http://www.w3.org/2000/svg">'
-                '<path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8zm7.5-6.923c-.67.204-1.335.82-1.887 '
-                "1.855-.143.268-.276.56-.395.872.705.157 1.472.257 2.282.287V1.077zM4.249 3.53"
-                "9c.142-.384.304-.744.481-1.078a6.7 6.7 0 0 1 .597-.933A7.01 7.01 0 0 0 3.051 "
-                "3.05c.362.184.763.349 1.198.49zM3.509 7.5c.036-1.07.188-2.087.436-3.008a9.124 "
-                "9.124 0 0 1-1.565-.667A6.964 6.964 0 0 0 1.018 7.5h2.49zm1.4-2.741a12.344 "
-                "12.344 0 0 0-.4 2.741H7.5V5.091c-.91-.03-1.783-.145-2.591-.332zM8.5 5.09V7.5h"
-                "2.99a12.342 12.342 0 0 0-.399-2.741c-.808.187-1.681.301-2.591.332zM4.51 8.5c.03"
-                "5.987.176 1.914.399 2.741A13.612 13.612 0 0 1 7.5 10.91V8.5H4.51zm3.99 0v2.409"
-                "c.91.03 1.783.145 2.591.332.223-.827.364-1.754.4-2.741H8.5zm-3.282 3.696c.12.31"
-                "2.252.604.395.872.552 1.035 1.218 1.65 1.887 1.855V11.91c-.81.03-1.577.13-2.28"
-                "2.287zm.11 2.276a6.696 6.696 0 0 1-.598-.933 8.853 8.853 0 0 1-.481-1.079 8.38 "
-                "8.38 0 0 0-1.198.49 7.01 7.01 0 0 0 2.276 1.522zm-1.383-2.964A13.36 13.36 0 0 1"
-                " 3.508 8.5h-2.49a6.963 6.963 0 0 0 1.362 3.675c.47-.258.995-.482 1.565-.667zm"
-                "6.728 2.964a7.009 7.009 0 0 0 2.275-1.521 8.376 8.376 0 0 0-1.197-.49 8.853 "
-                "8.853 0 0 1-.481 1.078 6.688 6.688 0 0 1-.597.933zM8.5 11.909v3.014c.67-.204 "
-                "1.335-.82 1.887-1.855.143-.268.276-.56.395-.872A12.63 12.63 0 0 0 8.5 11.91zm"
-                "3.555-.401c.57.185 1.095.409 1.565.667A6.963 6.963 0 0 0 14.982 8.5h-2.49a1"
-                "3.36 13.36 0 0 1-.437 3.008zM14.982 7.5a6.963 6.963 0 0 0-1.362-3.675c-.47.25"
-                "8-.995.482-1.565.667.248.92.4 1.938.437 3.008h2.49zM11.27 2.461c.177.334.339.6"
-                "94.482 1.078a8.368 8.368 0 0 0 1.196-.49 7.01 7.01 0 0 0-2.275-1.52c.218.283.4"
-                "18.597.597.932zm-.488 1.343a7.765 7.765 0 0 0-.395-.872C9.835 1.897 9.17 1.282 "
-                '8.5 1.077V4.09c.81-.03 1.577-.13 2.282-.287z"></path></svg>'
-            ),
-            "class": "",
-        },
-    ],
-}
+# further.  For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
 
 # The name for this set of Sphinx documents.  If None, it defaults to
 # "<project> v<release> documentation".
-html_title = f"python-telegram-bot<br> v{version}"
+#html_title = None
+
+# A shorter title for the navigation bar.  Default is the same as html_title.
+#html_short_title = None
 
 # The name of an image file (relative to this directory) to place at the top
 # of the sidebar.
-html_logo = "ptb-logo_1024.png"
+#html_logo = None
 
 # The name of an image file (within the static path) to use as favicon of the
 # docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
 # pixels large.
-html_favicon = "ptb-logo_1024.ico"
+#html_favicon = None
 
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ["_static"]
-html_css_files = [
-    "style_external_link.css",
-    "style_mermaid_diagrams.css",
-    "style_sidebar_brand.css",
-    "style_general.css",
-    "style_admonitions.css",
-    "style_images.css",
-]
+html_static_path = ['_static']
 
-html_permalinks_icon = "¶"  # Furo's default permalink icon is `#` which doesn't look great imo.
+# Add any extra paths that contain custom files (such as robots.txt or
+# .htaccess) here, relative to this directory. These files are copied
+# directly to the root of the documentation.
+#html_extra_path = []
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_domain_indices = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
+#html_show_sphinx = True
+
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
+#html_show_copyright = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it.  The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# This is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = None
+
+# Language to be used for generating the HTML full-text search index.
+# Sphinx supports the following languages:
+#   'da', 'de', 'en', 'es', 'fi', 'fr', 'hu', 'it', 'ja'
+#   'nl', 'no', 'pt', 'ro', 'ru', 'sv', 'tr'
+#html_search_language = 'en'
+
+# A dictionary with options for the search language support, empty by default.
+# Now only 'ja' uses this config value
+#html_search_options = {'type': 'default'}
+
+# The name of a javascript file (relative to the configuration directory) that
+# implements a search results scorer. If empty, the default will be used.
+#html_search_scorer = 'scorer.js'
 
 # Output file base name for HTML help builder.
-htmlhelp_basename = "python-telegram-bot-doc"
-
-# The base URL which points to the root of the HTML documentation. It is used to indicate the
-# location of document using The Canonical Link Relation. Default: ''.
-html_baseurl = "https://docs.python-telegram-bot.org"
+htmlhelp_basename = 'PythonTelegramBotdoc'
 
 # -- Options for LaTeX output ---------------------------------------------
 
 latex_elements = {
-    # The paper size ('letterpaper' or 'a4paper').
-    "papersize": "a4paper",
-    # The font size ('10pt', '11pt' or '12pt').
-    #'pointsize': '10pt',
-    # Additional stuff for the LaTeX preamble.
-    "preamble": r"""\setcounter{tocdepth}{2}
-\usepackage{enumitem}
-\setlistdepth{99}""",
-    # Latex figure (float) alignment
-    #'figure_align': 'htbp',
+# The paper size ('letterpaper' or 'a4paper').
+#'papersize': 'letterpaper',
+
+# The font size ('10pt', '11pt' or '12pt').
+#'pointsize': '10pt',
+
+# Additional stuff for the LaTeX preamble.
+#'preamble': '',
+
+# Latex figure (float) alignment
+#'figure_align': 'htbp',
 }
 
 # Grouping the document tree into LaTeX files. List of tuples
 # (source start file, target name, title,
 #  author, documentclass [howto, manual, or own class]).
 latex_documents = [
-    (master_doc, "python-telegram-bot.tex", "python-telegram-bot Documentation", author, "manual"),
+  (master_doc, 'PythonTelegramBot.tex', u'Python Telegram Bot Documentation',
+   u'Leandro Toledo', 'manual'),
 ]
 
 # The name of an image file (relative to this directory) to place at the top of
 # the title page.
-latex_logo = "ptb-logo_1024.png"
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# If true, show page references after internal links.
+#latex_show_pagerefs = False
+
+# If true, show URL addresses after external links.
+#latex_show_urls = False
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_domain_indices = True
+
 
 # -- Options for manual page output ---------------------------------------
 
 # One entry per manual page. List of tuples
 # (source start file, name, description, authors, manual section).
-man_pages = [(master_doc, "python-telegram-bot", "python-telegram-bot Documentation", [author], 1)]
+man_pages = [
+    (master_doc, 'pythontelegrambot', u'Python Telegram Bot Documentation',
+     [author], 1)
+]
+
+# If true, show URL addresses after external links.
+#man_show_urls = False
 
-# rtd_sphinx_search_file_type = "un-minified"  # Configuration for furo-sphinx-search
 
 # -- Options for Texinfo output -------------------------------------------
 
@@ -293,36 +270,19 @@ man_pages = [(master_doc, "python-telegram-bot", "python-telegram-bot Documentat
 # (source start file, target name, title, author,
 #  dir menu entry, description, category)
 texinfo_documents = [
-    (
-        master_doc,
-        "python-telegram-bot",
-        "python-telegram-bot Documentation",
-        author,
-        "python-telegram-bot",
-        "We have made you a wrapper you can't refuse",
-        "Miscellaneous",
-    ),
+  (master_doc, 'PythonTelegramBot', u'Python Telegram Bot Documentation',
+   author, 'PythonTelegramBot', 'Not just a Python wrapper around the Telegram Bot API',
+   'Miscellaneous'),
 ]
 
-# -- script stuff --------------------------------------------------------
+# Documents to append as an appendix to all manuals.
+#texinfo_appendices = []
 
-# Due to Sphinx behaviour, these imports only work when imported here, not at top of module.
+# If false, no module index is generated.
+#texinfo_domain_indices = True
 
-# Not used but must be imported for the linkcode extension to find it
-from docs.auxil.link_code import linkcode_resolve  # noqa: E402, F401
-from docs.auxil.sphinx_hooks import (  # noqa: E402
-    autodoc_process_bases,
-    autodoc_process_docstring,
-    autodoc_skip_member,
-)
-from docs.auxil.tg_const_role import CONSTANTS_ROLE, TGConstXRefRole  # noqa: E402
+# How to display URL addresses: 'footnote', 'no', or 'inline'.
+#texinfo_show_urls = 'footnote'
 
-
-def setup(app: Sphinx):
-    app.connect("autodoc-skip-member", autodoc_skip_member)
-    app.connect("autodoc-process-bases", autodoc_process_bases)
-    # The default priority is 500. We want our function to run before napoleon doc-conversion
-    # and sphinx-paramlinks do, b/c otherwise the inserted kwargs in the bot methods won't show
-    # up in the objects.inv file that Sphinx generates (i.e. not in the search).
-    app.connect("autodoc-process-docstring", autodoc_process_docstring, priority=100)
-    app.add_role_to_domain("py", CONSTANTS_ROLE, TGConstXRefRole())
+# If true, do not generate a @detailmenu in the "Top" node's menu.
+#texinfo_no_detailmenu = False

docs/source/contributing.rst

@@ -1 +0,0 @@
-.. include:: ../../.github/CONTRIBUTING.rst

docs/source/examples.arbitrarycallbackdatabot.rst

@@ -1,7 +0,0 @@
-``arbitrarycallbackdatabot.py``
-===============================
-
-.. literalinclude:: ../../examples/arbitrarycallbackdatabot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.chatmemberbot.rst

@@ -1,7 +0,0 @@
-``chatmemberbot.py``
-====================
-
-.. literalinclude:: ../../examples/chatmemberbot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.contexttypesbot.rst

@@ -1,7 +0,0 @@
-``contexttypesbot.py``
-======================
-
-.. literalinclude:: ../../examples/contexttypesbot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.conversationbot.rst

@@ -1,13 +0,0 @@
-``conversationbot.py``
-======================
-
-.. literalinclude:: ../../examples/conversationbot.py
-   :language: python
-   :linenos:
-
-.. _conversationbot-diagram:
-
-State Diagram
--------------
-
-.. mermaid:: ../../examples/conversationbot.mmd

docs/source/examples.conversationbot2.rst

@@ -1,13 +0,0 @@
-``conversationbot2.py``
-=======================
-
-.. literalinclude:: ../../examples/conversationbot2.py
-   :language: python
-   :linenos:
-
-.. _conversationbot2-diagram:
-
-State Diagram
--------------
-
-.. mermaid:: ../../examples/conversationbot2.mmd

docs/source/examples.customwebhookbot.rst

@@ -1,43 +0,0 @@
-``customwebhookbot.py``
-=======================
-
-This example is available for different web frameworks.
-You can select your preferred framework by opening one of the tabs above the code example.
-
-.. hint::
-
-    The following examples show how different Python web frameworks can be used alongside PTB.
-    This can be useful for two use cases:
-
-    1. For extending the functionality of your existing bot to handling updates of external services
-    2. For extending the functionality of your exisiting web application to also include chat bot functionality
-
-    How the PTB and web framework components of the examples below are viewed surely depends on which use case one has in mind.
-    We are fully aware that a combination of PTB with web frameworks will always mean finding a tradeoff between usability and best practices for both PTB and the web framework and these examples are certainly far from optimal solutions.
-    Please understand them as starting points and use your expertise of the web framework of your choosing to build up on them.
-    You are of course also very welcome to help improve these examples!
-
-.. tab:: ``starlette``
-
-    .. literalinclude:: ../../examples/customwebhookbot/starlettebot.py
-       :language: python
-       :linenos:
-
-.. tab:: ``flask``
-
-    .. literalinclude:: ../../examples/customwebhookbot/flaskbot.py
-       :language: python
-       :linenos:
-
-.. tab:: ``quart``
-
-    .. literalinclude:: ../../examples/customwebhookbot/quartbot.py
-       :language: python
-       :linenos:
-
-.. tab:: ``Django``
-
-    .. literalinclude:: ../../examples/customwebhookbot/djangobot.py
-       :language: python
-       :linenos:
-    

docs/source/examples.deeplinking.rst

@@ -1,7 +0,0 @@
-``deeplinking.py``
-==================
-
-.. literalinclude:: ../../examples/deeplinking.py
-   :language: python
-   :linenos:
-    

docs/source/examples.echobot.rst

@@ -1,7 +0,0 @@
-``echobot.py``
-==============
-
-.. literalinclude:: ../../examples/echobot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.errorhandlerbot.rst

@@ -1,7 +0,0 @@
-``errorhandlerbot.py``
-======================
-
-.. literalinclude:: ../../examples/errorhandlerbot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.inlinebot.rst

@@ -1,7 +0,0 @@
-``inlinebot.py``
-================
-
-.. literalinclude:: ../../examples/inlinebot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.inlinekeyboard.rst

@@ -1,7 +0,0 @@
-``inlinekeyboard.py``
-=====================
-
-.. literalinclude:: ../../examples/inlinekeyboard.py
-   :language: python
-   :linenos:
-    

docs/source/examples.inlinekeyboard2.rst

@@ -1,7 +0,0 @@
-``inlinekeyboard2.py``
-======================
-
-.. literalinclude:: ../../examples/inlinekeyboard2.py
-   :language: python
-   :linenos:
-    

docs/source/examples.nestedconversationbot.rst

@@ -1,13 +0,0 @@
-``nestedconversationbot.py``
-============================
-
-.. literalinclude:: ../../examples/nestedconversationbot.py
-   :language: python
-   :linenos:
-
-.. _nestedconversationbot-diagram:
-
-State Diagram
--------------
-
-.. mermaid:: ../../examples/nestedconversationbot.mmd

docs/source/examples.passportbot.rst

@@ -1,16 +0,0 @@
-``passportbot.py``
-==================
-
-.. literalinclude:: ../../examples/passportbot.py
-   :language: python
-   :linenos:
-
-.. _passportbot-html:
-
-HTML Page
----------
-
-.. literalinclude:: ../../examples/passportbot.html
-   :language: html
-   :linenos:
-    

docs/source/examples.paymentbot.rst

@@ -1,7 +0,0 @@
-``paymentbot.py``
-=================
-
-.. literalinclude:: ../../examples/paymentbot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.persistentconversationbot.rst

@@ -1,7 +0,0 @@
-``persistentconversationbot.py``
-================================
-
-.. literalinclude:: ../../examples/persistentconversationbot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.pollbot.rst

@@ -1,7 +0,0 @@
-``pollbot.py``
-==============
-
-.. literalinclude:: ../../examples/pollbot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.rawapibot.rst

@@ -1,11 +0,0 @@
-`rawapibot.py`
-==============
-
-This example uses only the pure, "bare-metal" API wrapper.
-
-
-
-.. literalinclude:: ../../examples/rawapibot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.rst

@@ -1,196 +0,0 @@
-Examples
-========
-
-In this section we display small examples to show what a bot written with
-``python-telegram-bot`` looks like.
-Some bots focus on one specific
-aspect of the Telegram Bot API while others focus on one of the
-mechanics of this library. Except for the
-:any:`examples.rawapibot` example, they all use the high-level
-framework this library provides with the
-:mod:`telegram.ext` submodule.
-
-All examples are licensed under the `CC0
-License <https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/LICENSE.txt>`__
-and are therefore fully dedicated to the public domain. You can use them
-as the base for your own bots without worrying about copyrights.
-
-Do note that we ignore one pythonic convention. Best practice would
-dictate, in many handler callbacks function signatures, to replace the
-argument ``context`` with an underscore, since ``context`` is an unused
-local variable in those callbacks. However, since these are examples and
-not having a name for that argument confuses beginners, we decided to
-have it present.
-
-:any:`examples.echobot`
------------------------
-
-This is probably the base for most of the bots made with
-``python-telegram-bot``. It simply replies to each text message with a
-message that contains the same text.
-
-:any:`examples.timerbot`
-------------------------
-
-This bot uses the
-:class:`telegram.ext.JobQueue`
-class to send timed messages. The user sets a timer by using ``/set``
-command with a specific time, for example ``/set 30``. The bot then sets
-up a job to send a message to that user after 30 seconds. The user can
-also cancel the timer by sending ``/unset``. To learn more about the
-``JobQueue``, read `this wiki article <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Extensions---JobQueue>`__.
-Note: To use ``JobQueue``, you must install PTB via ``pip install "python-telegram-bot[job-queue]"``
-
-:any:`examples.conversationbot`
--------------------------------
-
-A common task for a bot is to ask information from the user. In v5.0 of
-this library, we introduced the
-:class:`telegram.ext.ConversationHandler`
-for that exact purpose. This example uses it to retrieve
-user-information in a conversation-like style. To get a better
-understanding, take a look at the :ref:`state diagram <conversationbot-diagram>`.
-
-:any:`examples.conversationbot2`
---------------------------------
-
-A more complex example of a bot that uses the ``ConversationHandler``.
-It is also more confusing. Good thing there is a :ref:`fancy state diagram <conversationbot2-diagram>`.
-for this one, too!
-
-:any:`examples.nestedconversationbot`
--------------------------------------
-
-A even more complex example of a bot that uses the nested
-``ConversationHandler``\ s. While it’s certainly not that complex that
-you couldn’t built it without nested ``ConversationHanldler``\ s, it
-gives a good impression on how to work with them. Of course, there is a
-:ref:`fancy state diagram <nestedconversationbot-diagram>`
-for this example, too!
-
-:any:`examples.persistentconversationbot`
------------------------------------------
-
-A basic example of a bot store conversation state and user_data over
-multiple restarts.
-
-:any:`examples.inlinekeyboard`
-------------------------------
-
-This example sheds some light on inline keyboards, callback queries and
-message editing. A wiki site explaining this examples lives
-`here <https://github.com/python-telegram-bot/python-telegram-bot/wiki/InlineKeyboard-Example>`__.
-
-:any:`examples.inlinekeyboard2`
--------------------------------
-
-A more complex example about inline keyboards, callback queries and
-message editing. This example showcases how an interactive menu could be
-build using inline keyboards.
-
-:any:`examples.deeplinking`
----------------------------
-
-A basic example on how to use deeplinking with inline keyboards.
-
-:any:`examples.inlinebot`
--------------------------
-
-A basic example of an `inline
-bot <https://core.telegram.org/bots/inline>`__. Don’t forget to enable
-inline mode with `@BotFather <https://telegram.me/BotFather>`_.
-
-:any:`examples.pollbot`
------------------------
-
-This example sheds some light on polls, poll answers and the
-corresponding handlers.
-
-:any:`examples.passportbot`
----------------------------
-
-A basic example of a bot that can accept passports. Use in combination
-with the :ref:`HTML page <passportbot-html>`.
-Don’t forget to enable and configure payments with
-`@BotFather <https://telegram.me/BotFather>`_. Check out this
-`guide <https://github.com/python-telegram-bot/python-telegram-bot/wiki/Telegram-Passport>`__
-on Telegram passports in PTB.
-Note: To use Telegram Passport, you must install PTB via ``pip install "python-telegram-bot[passport]"``
-
-:any:`examples.paymentbot`
---------------------------
-
-A basic example of a bot that can accept payments. Don’t forget to
-enable and configure payments with
-`@BotFather <https://telegram.me/BotFather>`_.
-
-:any:`examples.errorhandlerbot`
--------------------------------
-
-A basic example on how to set up a custom error handler.
-
-:any:`examples.chatmemberbot`
------------------------------
-
-A basic example on how ``(my_)chat_member`` updates can be used.
-
-:any:`examples.webappbot`
--------------------------
-
-A basic example of how `Telegram
-WebApps <https://core.telegram.org/bots/webapps>`__ can be used. Use in
-combination with the :ref:`HTML page <webappbot-html>`.
-For your convenience, this file is hosted by the PTB team such that you
-don’t need to host it yourself. Uses the
-`iro.js <https://iro.js.org>`__ JavaScript library to showcase a
-user interface that is hard to achieve with native Telegram
-functionality.
-
-:any:`examples.contexttypesbot`
--------------------------------
-
-This example showcases how ``telegram.ext.ContextTypes`` can be used to
-customize the ``context`` argument of handler and job callbacks.
-
-:any:`examples.customwebhookbot`
---------------------------------
-
-This example showcases how a custom webhook setup can be used in
-combination with ``telegram.ext.Application``.
-
-:any:`examples.arbitrarycallbackdatabot`
-----------------------------------------
-
-This example showcases how PTBs “arbitrary callback data” feature can be
-used.
-Note: To use arbitrary callback data, you must install PTB via ``pip install "python-telegram-bot[callback-data]"``
-
-Pure API
---------
-
-The :any:`examples.rawapibot` example example uses only the pure, “bare-metal” API wrapper.
-
-.. toctree::
-   :hidden:
-
-   examples.arbitrarycallbackdatabot
-   examples.chatmemberbot
-   examples.contexttypesbot
-   examples.conversationbot
-   examples.conversationbot2
-   examples.customwebhookbot
-   examples.deeplinking
-   examples.echobot
-   examples.errorhandlerbot
-   examples.inlinebot
-   examples.inlinekeyboard
-   examples.inlinekeyboard2
-   examples.nestedconversationbot
-   examples.passportbot
-   examples.paymentbot
-   examples.persistentconversationbot
-   examples.pollbot
-   examples.rawapibot
-   examples.timerbot
-   examples.webappbot
-

docs/source/examples.timerbot.rst

@@ -1,7 +0,0 @@
-``timerbot.py``
-===============
-
-.. literalinclude:: ../../examples/timerbot.py
-   :language: python
-   :linenos:
-    

docs/source/examples.webappbot.rst

@@ -1,16 +0,0 @@
-``webappbot.py``
-================
-
-.. literalinclude:: ../../examples/webappbot.py
-   :language: python
-   :linenos:
-
-.. _webappbot-html:
-
-HTML Page
----------
-
-.. literalinclude:: ../../examples/webappbot.html
-   :language: html
-   :linenos:
-    

docs/source/inclusions/application_run_tip.rst

@@ -1,9 +0,0 @@
-.. tip::
-    * When combining ``python-telegram-bot`` with other :mod:`asyncio` based frameworks, using this
-      method is likely not the best choice, as it blocks the event loop until it receives a stop
-      signal as described above.
-      Instead, you can manually call the methods listed below to start and shut down the application
-      and the :attr:`~telegram.ext.Application.updater`.
-      Keeping the event loop running and listening for a stop signal is then up to you.
-    * To gracefully stop the execution of this method from within a handler, job or error callback,
-      use :meth:`~telegram.ext.Application.stop_running`.

docs/source/inclusions/bot_methods.rst

@@ -1,428 +0,0 @@
-.. raw:: html
-
-   <hr style="height:2px;border-width:0;color:gray;background-color:gray">
-   <p>Since this class has a large number of methods and attributes, below you can find a quick overview.
-
-   </p>
-   <details>
-   <summary>Sending Messages</summary>
-
-.. list-table::
-        :align: left
-        :widths: 1 4
-
-        * - :meth:`~telegram.Bot.send_animation`
-          - Used for sending animations
-        * - :meth:`~telegram.Bot.send_audio`
-          - Used for sending audio files
-        * - :meth:`~telegram.Bot.send_chat_action`
-          - Used for sending chat actions
-        * - :meth:`~telegram.Bot.send_contact`
-          - Used for sending contacts
-        * - :meth:`~telegram.Bot.send_dice`
-          - Used for sending dice messages
-        * - :meth:`~telegram.Bot.send_document`
-          - Used for sending documents
-        * - :meth:`~telegram.Bot.send_game`
-          - Used for sending a game
-        * - :meth:`~telegram.Bot.send_invoice`
-          - Used for sending an invoice
-        * - :meth:`~telegram.Bot.send_location`
-          - Used for sending location
-        * - :meth:`~telegram.Bot.send_media_group`
-          - Used for sending media grouped together
-        * - :meth:`~telegram.Bot.send_message`
-          - Used for sending text messages
-        * - :meth:`~telegram.Bot.send_paid_media`
-          - Used for sending paid media to channels
-        * - :meth:`~telegram.Bot.send_photo`
-          - Used for sending photos
-        * - :meth:`~telegram.Bot.send_poll`
-          - Used for sending polls
-        * - :meth:`~telegram.Bot.send_sticker`
-          - Used for sending stickers
-        * - :meth:`~telegram.Bot.send_venue`
-          - Used for sending venue locations.
-        * - :meth:`~telegram.Bot.send_video`
-          - Used for sending videos
-        * - :meth:`~telegram.Bot.send_video_note`
-          - Used for sending video notes
-        * - :meth:`~telegram.Bot.send_voice`
-          - Used for sending voice messages
-        * - :meth:`~telegram.Bot.copy_message`
-          - Used for copying the contents of an arbitrary message
-        * - :meth:`~telegram.Bot.copy_messages`
-          - Used for copying the contents of an multiple arbitrary messages
-        * - :meth:`~telegram.Bot.forward_message`
-          - Used for forwarding messages
-        * - :meth:`~telegram.Bot.forward_messages`
-          - Used for forwarding multiple messages at once
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Updating Messages</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :meth:`~telegram.Bot.answer_callback_query`
-      - Used for answering the callback query
-    * - :meth:`~telegram.Bot.answer_inline_query`
-      - Used for answering the inline query
-    * - :meth:`~telegram.Bot.answer_pre_checkout_query`
-      - Used for answering a pre checkout query
-    * - :meth:`~telegram.Bot.answer_shipping_query`
-      - Used for answering a shipping query
-    * - :meth:`~telegram.Bot.answer_web_app_query`
-      - Used for answering a web app query
-    * - :meth:`~telegram.Bot.delete_message`
-      - Used for deleting messages.
-    * - :meth:`~telegram.Bot.delete_messages`
-      - Used for deleting multiple messages as once.
-    * - :meth:`~telegram.Bot.edit_message_caption`
-      - Used for editing captions
-    * - :meth:`~telegram.Bot.edit_message_media`
-      - Used for editing the media on messages
-    * - :meth:`~telegram.Bot.edit_message_live_location`
-      - Used for editing the location in live location messages
-    * - :meth:`~telegram.Bot.edit_message_reply_markup`
-      - Used for editing the reply markup on messages
-    * - :meth:`~telegram.Bot.edit_message_text`
-      - Used for editing text messages
-    * - :meth:`~telegram.Bot.stop_poll`
-      - Used for stopping the running poll
-    * - :meth:`~telegram.Bot.set_message_reaction`
-      - Used for setting reactions on messages
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Chat Moderation and information</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :meth:`~telegram.Bot.approve_chat_join_request`
-      - Used for approving a chat join request
-    * - :meth:`~telegram.Bot.decline_chat_join_request`
-      - Used for declining a chat join request
-    * - :meth:`~telegram.Bot.ban_chat_member`
-      - Used for banning a member from the chat
-    * - :meth:`~telegram.Bot.unban_chat_member`
-      - Used for unbanning a member from the chat
-    * - :meth:`~telegram.Bot.ban_chat_sender_chat`
-      - Used for banning a channel in a channel or supergroup
-    * - :meth:`~telegram.Bot.unban_chat_sender_chat`
-      - Used for unbanning a channel in a channel or supergroup
-    * - :meth:`~telegram.Bot.restrict_chat_member`
-      - Used for restricting a chat member
-    * - :meth:`~telegram.Bot.promote_chat_member`
-      - Used for promoting a chat member
-    * - :meth:`~telegram.Bot.set_chat_administrator_custom_title`
-      - Used for assigning a custom admin title to an admin
-    * - :meth:`~telegram.Bot.set_chat_permissions`
-      - Used for setting the permissions of a chat
-    * - :meth:`~telegram.Bot.export_chat_invite_link`
-      - Used for creating a new primary invite link for a chat
-    * - :meth:`~telegram.Bot.create_chat_invite_link`
-      - Used for creating an additional invite link for a chat
-    * - :meth:`~telegram.Bot.edit_chat_invite_link`
-      - Used for editing a non-primary invite link
-    * - :meth:`~telegram.Bot.revoke_chat_invite_link`
-      - Used for revoking an invite link created by the bot
-    * - :meth:`~telegram.Bot.set_chat_photo`
-      - Used for setting a photo to a chat
-    * - :meth:`~telegram.Bot.delete_chat_photo`
-      - Used for deleting a chat photo
-    * - :meth:`~telegram.Bot.set_chat_title`
-      - Used for setting a chat title
-    * - :meth:`~telegram.Bot.set_chat_description`
-      - Used for setting the description of a chat
-    * - :meth:`~telegram.Bot.pin_chat_message`
-      - Used for pinning a message
-    * - :meth:`~telegram.Bot.unpin_chat_message`
-      - Used for unpinning a message
-    * - :meth:`~telegram.Bot.unpin_all_chat_messages`
-      - Used for unpinning all pinned chat messages
-    * - :meth:`~telegram.Bot.get_business_connection`
-      - Used for getting information about the business account.
-    * - :meth:`~telegram.Bot.get_user_profile_photos`
-      - Used for obtaining user's profile pictures
-    * - :meth:`~telegram.Bot.get_chat`
-      - Used for getting information about a chat
-    * - :meth:`~telegram.Bot.get_chat_administrators`
-      - Used for getting the list of admins in a chat
-    * - :meth:`~telegram.Bot.get_chat_member_count`
-      - Used for getting the number of members in a chat
-    * - :meth:`~telegram.Bot.get_chat_member`
-      - Used for getting a member of a chat
-    * - :meth:`~telegram.Bot.get_user_chat_boosts`
-      - Used for getting the list of boosts added to a chat
-    * - :meth:`~telegram.Bot.leave_chat`
-      - Used for leaving a chat
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Bot settings</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :meth:`~telegram.Bot.set_my_commands`
-      - Used for setting the list of commands
-    * - :meth:`~telegram.Bot.delete_my_commands`
-      - Used for deleting the list of commands
-    * - :meth:`~telegram.Bot.get_my_commands`
-      - Used for obtaining the list of commands
-    * - :meth:`~telegram.Bot.get_my_default_administrator_rights`
-      - Used for obtaining the default administrator rights for the bot
-    * - :meth:`~telegram.Bot.set_my_default_administrator_rights`
-      - Used for setting the default administrator rights for the bot
-    * - :meth:`~telegram.Bot.get_chat_menu_button`
-      - Used for obtaining the menu button of a private chat or the default menu button
-    * - :meth:`~telegram.Bot.set_chat_menu_button`
-      - Used for setting the menu button of a private chat or the default menu button
-    * - :meth:`~telegram.Bot.set_my_description`
-      - Used for setting the description of the bot
-    * - :meth:`~telegram.Bot.get_my_description`
-      - Used for obtaining the description of the bot
-    * - :meth:`~telegram.Bot.set_my_short_description`
-      - Used for setting the short description of the bot
-    * - :meth:`~telegram.Bot.get_my_short_description`
-      - Used for obtaining the short description of the bot
-    * - :meth:`~telegram.Bot.set_my_name`
-      - Used for setting the name of the bot
-    * - :meth:`~telegram.Bot.get_my_name`
-      - Used for obtaining the name of the bot
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Stickerset management</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :meth:`~telegram.Bot.add_sticker_to_set`
-      - Used for adding a sticker to a set
-    * - :meth:`~telegram.Bot.delete_sticker_from_set`
-      - Used for deleting a sticker from a set
-    * - :meth:`~telegram.Bot.create_new_sticker_set`
-      - Used for creating a new sticker set
-    * - :meth:`~telegram.Bot.delete_sticker_set`
-      - Used for deleting a sticker set made by a bot
-    * - :meth:`~telegram.Bot.set_chat_sticker_set`
-      - Used for setting a sticker set of a chat
-    * - :meth:`~telegram.Bot.delete_chat_sticker_set`
-      - Used for deleting the set sticker set of a chat
-    * - :meth:`~telegram.Bot.replace_sticker_in_set`
-      - Used for replacing a sticker in a set
-    * - :meth:`~telegram.Bot.set_sticker_position_in_set`
-      - Used for moving a sticker's position in the set
-    * - :meth:`~telegram.Bot.set_sticker_set_title`
-      - Used for setting the title of a sticker set
-    * - :meth:`~telegram.Bot.set_sticker_emoji_list`
-      - Used for setting the emoji list of a sticker
-    * - :meth:`~telegram.Bot.set_sticker_keywords`
-      - Used for setting the keywords of a sticker
-    * - :meth:`~telegram.Bot.set_sticker_mask_position`
-      - Used for setting the mask position of a mask sticker
-    * - :meth:`~telegram.Bot.set_sticker_set_thumbnail`
-      - Used for setting the thumbnail of a sticker set
-    * - :meth:`~telegram.Bot.set_custom_emoji_sticker_set_thumbnail`
-      - Used for setting the thumbnail of a custom emoji sticker set
-    * - :meth:`~telegram.Bot.get_sticker_set`
-      - Used for getting a sticker set
-    * - :meth:`~telegram.Bot.upload_sticker_file`
-      - Used for uploading a sticker file
-    * - :meth:`~telegram.Bot.get_custom_emoji_stickers`
-      - Used for getting custom emoji files based on their IDs
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Games</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :meth:`~telegram.Bot.get_game_high_scores`
-      - Used for getting the game high scores
-    * - :meth:`~telegram.Bot.set_game_score`
-      - Used for setting the game score
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Getting updates</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :meth:`~telegram.Bot.get_updates`
-      - Used for getting updates using long polling
-    * - :meth:`~telegram.Bot.get_webhook_info`
-      - Used for getting current webhook status
-    * - :meth:`~telegram.Bot.set_webhook`
-      - Used for setting a webhook to receive updates
-    * - :meth:`~telegram.Bot.delete_webhook`
-      - Used for removing webhook integration
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Forum topic management</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :meth:`~telegram.Bot.close_forum_topic`
-      - Used for closing a forum topic
-    * - :meth:`~telegram.Bot.close_general_forum_topic`
-      - Used for closing the general forum topic
-    * - :meth:`~telegram.Bot.create_forum_topic`
-      - Used to create a topic
-    * - :meth:`~telegram.Bot.delete_forum_topic`
-      - Used for deleting a forum topic
-    * - :meth:`~telegram.Bot.edit_forum_topic`
-      - Used to edit a topic
-    * - :meth:`~telegram.Bot.edit_general_forum_topic`
-      - Used to edit the general topic
-    * - :meth:`~telegram.Bot.get_forum_topic_icon_stickers`
-      - Used to get custom emojis to use as topic icons
-    * - :meth:`~telegram.Bot.hide_general_forum_topic`
-      - Used to hide the general topic
-    * - :meth:`~telegram.Bot.unhide_general_forum_topic`
-      - Used to unhide the general topic
-    * - :meth:`~telegram.Bot.reopen_forum_topic`
-      - Used to reopen a topic
-    * - :meth:`~telegram.Bot.reopen_general_forum_topic`
-      - Used to reopen the general topic
-    * - :meth:`~telegram.Bot.unpin_all_forum_topic_messages`
-      - Used to unpin all messages in a forum topic
-    * - :meth:`~telegram.Bot.unpin_all_general_forum_topic_messages`
-      - Used to unpin all messages in the general forum topic
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Miscellaneous</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :meth:`~telegram.Bot.create_invoice_link`
-      - Used to generate an HTTP link for an invoice
-    * - :meth:`~telegram.Bot.close`
-      - Used for closing server instance when switching to another local server
-    * - :meth:`~telegram.Bot.log_out`
-      - Used for logging out from cloud Bot API server
-    * - :meth:`~telegram.Bot.get_file`
-      - Used for getting basic info about a file
-    * - :meth:`~telegram.Bot.get_me`
-      - Used for getting basic information about the bot
-    * - :meth:`~telegram.Bot.get_star_transactions`
-      - Used for obtaining the bot's Telegram Stars transactions
-    * - :meth:`~telegram.Bot.refund_star_payment`
-      - Used for refunding a payment in Telegram Stars
-
-.. raw:: html
-
-   </details>
-   <br>
-
-.. raw:: html
-
-   <details>
-   <summary>Properties</summary>
-
-.. list-table::
-    :align: left
-    :widths: 1 4
-
-    * - :attr:`~telegram.Bot.base_file_url`
-      - Telegram Bot API file URL
-    * - :attr:`~telegram.Bot.base_url`
-      - Telegram Bot API service URL
-    * - :attr:`~telegram.Bot.bot`
-      - The user instance of the bot as returned by :meth:`~telegram.Bot.get_me`
-    * - :attr:`~telegram.Bot.can_join_groups`
-      - Whether the bot can join groups
-    * - :attr:`~telegram.Bot.can_read_all_group_messages`
-      - Whether the bot can read all incoming group messages
-    * - :attr:`~telegram.Bot.id`
-      - The user id of the bot
-    * - :attr:`~telegram.Bot.name`
-      - The username of the bot, with leading ``@``
-    * - :attr:`~telegram.Bot.first_name`
-      - The first name of the bot
-    * - :attr:`~telegram.Bot.last_name`
-      - The last name of the bot
-    * - :attr:`~telegram.Bot.local_mode`
-      - Whether the bot is running in local mode
-    * - :attr:`~telegram.Bot.username`
-      - The username of the bot, without leading ``@``
-    * - :attr:`~telegram.Bot.link`
-      - The t.me link of the bot
-    * - :attr:`~telegram.Bot.private_key`
-      - Deserialized private key for decryption of telegram passport data
-    * - :attr:`~telegram.Bot.supports_inline_queries`
-      - Whether the bot supports inline queries
-    * - :attr:`~telegram.Bot.token`
-      - Bot's unique authentication token
-
-.. raw:: html
-
-   </details>
-   <br>
-   <hr style="height:2px;border-width:0;color:gray;background-color:gray">

docs/source/inclusions/menu_button_command_video.rst

@@ -1,3 +0,0 @@
-.. raw:: html
-
-    <center><video height="300px" loop autoplay muted><source src="https://core.telegram.org/file/464001555/10fbd/jvTuV2Ke7WQ.1916669.mp4/a056de323645db409d" type="video/mp4"></video></center>

docs/source/inclusions/pool_size_tip.rst

@@ -1,10 +0,0 @@
-.. tip::
-    When making requests to the Bot API in an asynchronous fashion (e.g. via
-    :attr:`block=False <telegram.ext.BaseHandler.block>`, :meth:`Application.create_task <telegram.ext.Application.create_task>`,
-    :meth:`~telegram.ext.ApplicationBuilder.concurrent_updates` or the :class:`~telegram.ext.JobQueue`), it can happen that more requests
-    are being made in parallel than there are connections in the pool.
-    If the number of requests is much higher than the number of connections, even setting
-    :meth:`~telegram.ext.ApplicationBuilder.pool_timeout` to a larger value may not always be enough to prevent pool
-    timeouts.
-    You should therefore set :meth:`~telegram.ext.ApplicationBuilder.concurrent_updates`, :meth:`~telegram.ext.ApplicationBuilder.connection_pool_size` and
-    :meth:`~telegram.ext.ApplicationBuilder.pool_timeout` to values that make sense for your setup.

docs/source/index.rst

@@ -3,48 +3,21 @@
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.
 
-.. raw:: html
+Welcome to Python Telegram Bot's documentation!
+===============================================
 
-    <div style="display: none">
-
-Hidden Headline
-===============
-This is just here to get furo to display the right sidebar.
-
-.. raw:: html
-
-    </div>
-
-.. include:: ../../README.rst
-
-.. The toctrees are hidden such that they don't render on the start page but still include the contents into the documentation.
+Contents:
 
 .. toctree::
-   :hidden:
-   :caption: Reference
+   :maxdepth: 2
 
-   telegram
-   telegram.ext
-   telegram_auxil
-   Telegrams Bot API Docs <https://core.telegram.org/bots/api>
 
-.. toctree::
-   :hidden:
-   :caption: Resources
 
-   examples
-   Wiki <https://github.com/python-telegram-bot/python-telegram-bot/wiki>
+Indices and tables
+==================
+
+* :ref:`genindex`
+* :ref:`modindex`
+* :ref:`search`
 
-.. toctree::
-   :hidden:
-   :caption: Project
 
-   stability_policy
-   changelog
-   coc
-   contributing
-   testing
-   Website <https://python-telegram-bot.org>
-   GitHub Repository <https://github.com/python-telegram-bot/python-telegram-bot/>
-   Telegram Channel <https://t.me/pythontelegrambotchannel/>
-   Telegram User Group <https://t.me/pythontelegrambotgroup/>

docs/source/modules.rst

@@ -0,0 +1,7 @@
+telegram
+========
+
+.. toctree::
+   :maxdepth: 4
+
+   telegram

docs/source/stability_policy.rst

@@ -1,146 +0,0 @@
-Stability Policy
-================
-
-.. important::
-
-    This stability policy is in place since version 20.3.
-    While earlier versions of ``python-telegram-bot`` also had stable interfaces, they had no explicit stability policy and hence did not follow the rules outlined below in all detail.
-    Please also refer to the :ref:`changelog <ptb-changelog>`.
-
-.. caution::
-
-    Large parts of the :mod:`telegram` package are the Python representations of the Telegram Bot API, whose stability policy PTB can not influence.
-    This policy hence includes some special cases for those parts.
-
-What does this policy cover?
-----------------------------
-
-This policy includes any API or behavior that is covered in this documentation.
-This covers both the :mod:`telegram` package and the :mod:`telegram.ext` package.
-
-What doesn't this policy cover?
--------------------------------
-
-Introduction of new features or changes of flavors of comparable behavior (e.g. the default for the HTTP protocol version being used) are not covered by this policy.
-
-The internal structure of classes in PTB, i.e. things like the result of ``dir(obj))`` or the contents of ``obj.__dict__``, is not covered by this policy.
-
-Objects are in general not guaranteed to be pickleable (unless stated otherwise) and pickled objects from one version of PTB may not be loadable in future versions.
-We may provide a way to convert pickled objects from one version to another, but this is not guaranteed.
-
-Functionality that is part of PTBs API but is explicitly documented as not being intended to be used directly by users (e.g. :meth:`telegram.request.BaseRequest.do_request`) may change.
-This also applies to functions or attributes marked as final in the sense of `PEP 591 <https://peps.python.org/pep-0591/>`__.
-
-PTB has dependencies to third-party packages.
-The versions that PTB uses of these third-party packages may change if that does not affect PTBs public API.
-
-PTB does not give guarantees about which Python versions are supported.
-In general, we will try to support all Python versions that have not yet reached their end of life, but we reserve ourselves the option to drop support for Python versions earlier if that benefits the advancement of the library.
-
-PTB provides static type hints for all public attributes, parameters, return values and generic classes.
-These type hints are not covered by this policy and may change at any time under the condition that these changes have no impact on the runtime behavior of PTB.
-
-.. _bot-api-functionality-1:
-
-Bot API Functionality
-~~~~~~~~~~~~~~~~~~~~~
-
-Comparison of equality of instances of the classes in the :mod:`telegram` package is subject to change and the PTB team will update the behavior to best reflect updates in the Bot API.
-Changes in this regard will be documented in the affected classes.
-Note that equality comparison with objects that where serialized by an older version of PTB may hence give unexpected results.
-
-When the order of arguments of the Bot API methods changes or they become optional/mandatory due to changes in the Bot API, PTB will always try to reflect these changes.
-While we try to make such changes backward compatible, this is not always possible or only with significant effort.
-In such cases we will find a trade-off between backward compatibility and fully complying with the Bot API, which may result in breaking changes.
-We highly recommend using keyword arguments, which can help make such changes non-breaking on your end.
-
-..
-    We have documented a few common cases and possible backwards compatible solutions in the wiki as a reference for the dev team: https://github.com/python-telegram-bot/python-telegram-bot/wiki/Bot-API-Backward-Compatibility
-
-When the Bot API changes attributes of classes, the method :meth:`telegram.TelegramObject.to_dict` will change as necessary to reflect these changes.
-In particular, attributes deprecated by Telegram will be removed from the returned dictionary.
-Deprecated attributes that are still passed by Telegram will be available in the :attr:`~telegram.TelegramObject.api_kwargs` dictionary as long as PTB can support that with feasible effort.
-Since attributes of the classes in the :mod:`telegram` package are not writable, we may change them to properties where appropriate.
-
-Development Versions
-~~~~~~~~~~~~~~~~~~~~
-
-Pre-releases marked as alpha, beta or release candidate are not covered by this policy.
-Before a feature is in a stable release, i.e. the feature was merged into the ``master`` branch but not released yet (or only in a pre-release), it is not covered by this policy either and may change.
-
-Security
-~~~~~~~~
-
-We make exceptions from our stability policy for security.
-We will violate this policy as necessary in order to resolve a security issue or harden PTB against a possible attack.
-
-Versioning
-----------
-
-PTB uses a versioning scheme that roughly follows `https://semver.org/ <https://semver.org/>`_, although it may not be quite as strict.
-
-Given a version of PTB X.Y.Z,
-
--  X indicates the major version number.
-   This is incremented when backward incompatible changes are introduced.
--  Y indicates the minor version number.
-   This is incremented when new functionality or backward compatible changes are introduced by PTB.
-   *This is also incremented when PTB adds support for a new Bot API version, which may include backward incompatible changes in some cases as outlined* :ref:`below <bot-api-versioning>`.
--  Z is the patch version.
-   This is incremented if backward compatible bug fixes or smaller changes are introduced.
-   If this number is 0, it can be omitted, i.e. we just write X.Y instead of X.Y.0.
-
-Deprecation
-~~~~~~~~~~~
-
-From time to time we will want to change the behavior of an API or remove it entirely, or we do so to comply with changes in the Telegram Bot API.
-In those cases, we follow a deprecation schedule as detailed below.
-
-Functionality is marked as deprecated by a corresponding note in the release notes and the documentation.
-Where possible, a :class:`~telegram.warnings.PTBDeprecationWarning` is issued when deprecated functionality is used, but this is not mandatory.
-
-From time to time, we may decide to deprecate an API that is particularly widely used.
-In these cases, we may decide to provide an extended deprecation period, at our discretion.
-
-With version 20.0.0, PTB introduced major structural breaking changes without the above deprecation period.
-Should a similarly big change ever be deemed necessary again by the development team and should a deprecation period prove too much additional effort, this violation of the stability policy will be announced well ahead of the release in our channel, `as was done for v20 <https://t.me/pythontelegrambotchannel/94>`_.
-
-Non-Bot API Functionality
-#########################
-
-Starting with version 20.3, deprecated functionality will stay available for the current and the next major version.
-For example:
-
--  In PTB v20.1.1 the feature exists
--  In PTB v20.1.2 or v20.2.0 the feature is marked as deprecated
--  In PTB v21.*.* the feature is marked as deprecated
--  In PTB v22.0 the feature is removed or changed
-
-.. _bot-api-versioning:
-
-Bot API Functionality
-#####################
-
-As PTB has no control over deprecations introduced by Telegram and the schedule of these deprecations rarely coincides with PTBs deprecation schedule, we have a special policy for Bot API functionality.
-
-Starting with 20.3, deprecated Bot API functionality will stay available for the current and the next major version of PTB *or* until the next version of the Bot API.
-More precisely, two cases are possible, for which we show examples below.
-
-Case 1
-^^^^^^
-
--  In PTB v20.1 the feature exists
--  Bot API version 6.6 is released and deprecates the feature
--  PTB v20.2 adds support for Bot API 6.6 and the feature is
-   marked as deprecated
--  In PTB v21.0 the feature is removed or changed
-
-Case 2
-^^^^^^
-
--  In PTB v20.1 the feature exists
--  Bot API version 6.6 is released and deprecates the feature
--  PTB v20.2 adds support for Bot API version 6.6 and the feature is marked as deprecated
--  In PTB v20.2.* and v20.3.* the feature is marked as deprecated
--  Bot API version 6.7 is released
--  PTB v20.4 adds support for Bot API version 6.7 and the feature is removed or changed

docs/source/telegram.animation.rst

@@ -1,9 +0,0 @@
-Animation
-=========
-
-.. Also lists methods of _BaseThumbedMedium, but not the ones of TelegramObject
-
-.. autoclass:: telegram.Animation
-    :members:
-    :show-inheritance:
-    :inherited-members: TelegramObject

docs/source/telegram.at-tree.rst

@@ -1,159 +0,0 @@
-Available Types
----------------
-
-.. toctree::
-    :titlesonly:
-
-    telegram.animation
-    telegram.audio
-    telegram.birthdate
-    telegram.botcommand
-    telegram.botcommandscope
-    telegram.botcommandscopeallchatadministrators
-    telegram.botcommandscopeallgroupchats
-    telegram.botcommandscopeallprivatechats
-    telegram.botcommandscopechat
-    telegram.botcommandscopechatadministrators
-    telegram.botcommandscopechatmember
-    telegram.botcommandscopedefault
-    telegram.botdescription
-    telegram.botname
-    telegram.botshortdescription
-    telegram.businessconnection
-    telegram.businessintro
-    telegram.businesslocation
-    telegram.businessopeninghours
-    telegram.businessopeninghoursinterval
-    telegram.businessmessagesdeleted
-    telegram.callbackquery
-    telegram.chat
-    telegram.chatadministratorrights
-    telegram.chatbackground
-    telegram.backgroundtype
-    telegram.backgroundtypefill
-    telegram.backgroundtypewallpaper
-    telegram.backgroundtypepattern
-    telegram.backgroundtypechattheme
-    telegram.backgroundfill
-    telegram.backgroundfillsolid
-    telegram.backgroundfillgradient
-    telegram.backgroundfillfreeformgradient
-    telegram.chatboost
-    telegram.chatboostadded
-    telegram.chatboostremoved
-    telegram.chatboostsource
-    telegram.chatboostsourcegiftcode
-    telegram.chatboostsourcegiveaway
-    telegram.chatboostsourcepremium
-    telegram.chatboostupdated
-    telegram.chatfullinfo
-    telegram.chatinvitelink
-    telegram.chatjoinrequest
-    telegram.chatlocation
-    telegram.chatmember
-    telegram.chatmemberadministrator
-    telegram.chatmemberbanned
-    telegram.chatmemberleft
-    telegram.chatmembermember
-    telegram.chatmemberowner
-    telegram.chatmemberrestricted
-    telegram.chatmemberupdated
-    telegram.chatpermissions
-    telegram.chatphoto
-    telegram.chatshared
-    telegram.contact
-    telegram.dice
-    telegram.document
-    telegram.externalreplyinfo
-    telegram.file
-    telegram.forcereply
-    telegram.forumtopic
-    telegram.forumtopicclosed
-    telegram.forumtopiccreated
-    telegram.forumtopicedited
-    telegram.forumtopicreopened
-    telegram.generalforumtopichidden
-    telegram.generalforumtopicunhidden
-    telegram.giveaway
-    telegram.giveawaycompleted
-    telegram.giveawaycreated
-    telegram.giveawaywinners
-    telegram.inaccessiblemessage
-    telegram.inlinekeyboardbutton
-    telegram.inlinekeyboardmarkup
-    telegram.inputfile
-    telegram.inputmedia
-    telegram.inputmediaanimation
-    telegram.inputmediaaudio
-    telegram.inputmediadocument
-    telegram.inputmediaphoto
-    telegram.inputmediavideo
-    telegram.inputpaidmedia
-    telegram.inputpaidmediaphoto
-    telegram.inputpaidmediavideo
-    telegram.inputpolloption
-    telegram.inputsticker
-    telegram.keyboardbutton
-    telegram.keyboardbuttonpolltype
-    telegram.keyboardbuttonrequestchat
-    telegram.keyboardbuttonrequestusers
-    telegram.linkpreviewoptions
-    telegram.location
-    telegram.loginurl
-    telegram.maybeinaccessiblemessage
-    telegram.menubutton
-    telegram.menubuttoncommands
-    telegram.menubuttondefault
-    telegram.menubuttonwebapp
-    telegram.message
-    telegram.messageautodeletetimerchanged
-    telegram.messageentity
-    telegram.messageid
-    telegram.messageorigin
-    telegram.messageoriginchannel
-    telegram.messageoriginchat
-    telegram.messageoriginhiddenuser
-    telegram.messageoriginuser
-    telegram.messagereactioncountupdated
-    telegram.messagereactionupdated
-    telegram.paidmedia
-    telegram.paidmediainfo
-    telegram.paidmediaphoto
-    telegram.paidmediapreview
-    telegram.paidmediavideo
-    telegram.photosize
-    telegram.poll
-    telegram.pollanswer
-    telegram.polloption
-    telegram.proximityalerttriggered
-    telegram.reactioncount
-    telegram.reactiontype
-    telegram.reactiontypecustomemoji
-    telegram.reactiontypeemoji
-    telegram.replykeyboardmarkup
-    telegram.replykeyboardremove
-    telegram.replyparameters
-    telegram.sentwebappmessage
-    telegram.shareduser
-    telegram.story
-    telegram.switchinlinequerychosenchat
-    telegram.telegramobject
-    telegram.textquote
-    telegram.update
-    telegram.user
-    telegram.userchatboosts
-    telegram.userprofilephotos
-    telegram.usersshared
-    telegram.venue
-    telegram.video
-    telegram.videochatended
-    telegram.videochatparticipantsinvited
-    telegram.videochatscheduled
-    telegram.videochatstarted
-    telegram.videonote
-    telegram.voice
-    telegram.webappdata
-    telegram.webappinfo
-    telegram.webhookinfo
-    telegram.writeaccessallowed
-

docs/source/telegram.audio.rst

@@ -1,9 +1,7 @@
-Audio
-=====
+telegram.audio module
+=====================
 
-.. Also lists methods of _BaseThumbedMedium, but not the ones of TelegramObject
-
-.. autoclass:: telegram.Audio
+.. automodule:: telegram.audio
     :members:
+    :undoc-members:
     :show-inheritance:
-    :inherited-members: TelegramObject

docs/source/telegram.backgroundfill.rst

@@ -1,8 +0,0 @@
-BackgroundFill
-==============
-
-.. versionadded:: 21.2
-
-.. autoclass:: telegram.BackgroundFill
-    :members:
-    :show-inheritance:

docs/source/telegram.backgroundfillfreeformgradient.rst

@@ -1,8 +0,0 @@
-BackgroundFillFreeformGradient
-==============================
-
-.. versionadded:: 21.2
-
-.. autoclass:: telegram.BackgroundFillFreeformGradient
-    :members:
-    :show-inheritance:

docs/source/telegram.backgroundfillgradient.rst

@@ -1,8 +0,0 @@
-BackgroundFillGradient
-======================
-
-.. versionadded:: 21.2
-
-.. autoclass:: telegram.BackgroundFillGradient
-    :members:
-    :show-inheritance:

docs/source/telegram.backgroundfillsolid.rst

@@ -1,8 +0,0 @@
-BackgroundFillSolid
-===================
-
-.. versionadded:: 21.2
-
-.. autoclass:: telegram.BackgroundFillSolid
-    :members:
-    :show-inheritance: