Documentation Improvements (#3214, #3217, #3218, #3271, #3289, #3292, #3303, #3312, #3306, #3319, #3326, #3314)
Co-authored-by: Harshil <37377066+harshil21@users.noreply.github.com>
Co-authored-by: Simon Fong <44134941+simonfongnt@users.noreply.github.com>
Co-authored-by: Piotr Rogulski <rivinek@gmail.com>
Co-authored-by: poolitzer <25934244+Poolitzer@users.noreply.github.com>
Co-authored-by: Or Bin <or@raftt.io>
Co-authored-by: Sandro <j32g7f67hb@liamekaens.com>
Co-authored-by: Hatim Zahid <63000127+HatimZ@users.noreply.github.com>
Co-authored-by: Robi <53259730+RobiMez@users.noreply.github.com>
Co-authored-by: Dmitry Kolomatskiy <58207913+lemontree210@users.noreply.github.com>
2022-11-15 09:06:23 +01:00
|
|
|
.. tip::
|
2023-08-17 11:50:26 +02:00
|
|
|
* 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`.
|
