538f1e3972
- Pyrogram core is now fully asynchronous - Ditched Python 3.5, welcome 3.6 as minimum version. - Moved all types to pyrogram.types - Turned the Filters class into a module (filters) - Moved all filters to pyrogram.filters - Moved all handlers to pyrogram.handlers - Moved all emoji to pyrogram.emoji - Renamed pyrogram.api to pyrogram.raw - Clock is now synced with server's time - Telegram schema updated to Layer 117 - Greatly improved the TL compiler (proper type-constructor hierarchy) - Added "do not edit" warning in generated files - Crypto parts are executed in a thread pool to avoid blocking the event loop - idle() is now a separate function (it doesn't deal with Client instances) - Async storage, async filters and async progress callback (optional, can be sync too) - Added getpass back, for hidden password inputs
79 lines
2.6 KiB
Python
79 lines
2.6 KiB
Python
# Pyrogram - Telegram MTProto API Client Library for Python
|
|
# Copyright (C) 2017-2020 Dan <https://github.com/delivrance>
|
|
#
|
|
# This file is part of Pyrogram.
|
|
#
|
|
# Pyrogram is free software: you can redistribute it and/or modify
|
|
# it under the terms of the GNU Lesser General Public License as published
|
|
# by the Free Software Foundation, either version 3 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# Pyrogram 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 General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU Lesser General Public License
|
|
# along with Pyrogram. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
import asyncio
|
|
import logging
|
|
import signal
|
|
|
|
log = logging.getLogger(__name__)
|
|
|
|
loop = asyncio.get_event_loop()
|
|
event = asyncio.Event()
|
|
|
|
|
|
async def idle():
|
|
"""Block the main script execution until a signal is received.
|
|
|
|
This function will run indefinitely in order to block the main script execution and prevent it from
|
|
exiting while having client(s) that are still running in the background.
|
|
|
|
It is useful for event-driven application only, that are, applications which react upon incoming Telegram
|
|
updates through handlers, rather than executing a set of methods sequentially.
|
|
|
|
The way Pyrogram works, it will keep your handlers in a pool of worker threads, which are executed concurrently
|
|
outside the main thread; calling idle() will ensure the client(s) will be kept alive by not letting the main
|
|
script to end, until you decide to quit.
|
|
|
|
Once a signal is received (e.g.: from CTRL+C) the function will terminate and your main script will continue.
|
|
Don't forget to call :meth:`~pyrogram.Client.stop` for each running client before the script ends.
|
|
|
|
Example:
|
|
.. code-block:: python
|
|
:emphasize-lines: 13
|
|
|
|
from pyrogram import Client, idle
|
|
|
|
app1 = Client("account1")
|
|
app2 = Client("account2")
|
|
app3 = Client("account3")
|
|
|
|
... # Set handlers up
|
|
|
|
app1.start()
|
|
app2.start()
|
|
app3.start()
|
|
|
|
idle()
|
|
|
|
app1.stop()
|
|
app2.stop()
|
|
app3.stop()
|
|
"""
|
|
|
|
def handler():
|
|
log.info("Stop signal received")
|
|
event.set()
|
|
|
|
asyncio.get_event_loop().add_signal_handler(signal.SIGINT, handler)
|
|
|
|
log.info("Idle started")
|
|
await event.wait()
|
|
|
|
log.info("Idle stopped")
|
|
event.clear()
|