Скачать или смотреть Running Two asyncio Coroutines in Separate Python Processes

Discover how to effectively manage multiple `asyncio` coroutines in Python by utilizing multiprocessing. Learn to handle user interrupts with ease!
---
This video is based on the question https://stackoverflow.com/q/68007828/ asked by the user 'Nyxynyx' ( https://stackoverflow.com/u/741099/ ) and on the answer https://stackoverflow.com/a/68008070/ provided by the user 'Will Da Silva' ( https://stackoverflow.com/u/5946921/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Running Two asyncio Coroutines, Each in its own Python Process

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Running Two asyncio Coroutines in Separate Python Processes

When developing applications in Python, especially those that require asynchronous operations, you might find yourself needing to run multiple asyncio coroutines simultaneously. However, what if you want each coroutine to operate in its own process, while still managing and terminating them easily? This guide will explore how you can do just that with the multiprocessing module, ensuring that both coroutines can be stopped cleanly when the user hits Ctrl+ C.

The Problem: Running Asyncio Coroutines in Separate Processes

Imagine you have two asyncio coroutines that need to run concurrently. You may want to keep each coroutine in its own process to ensure they don't interfere with each other. Moreover, you want the capability to stop both coroutines gracefully when the user decides to interrupt the program with Ctrl+ C.

To put it simply, you might have a setup like the following:

[[See Video to Reveal this Text or Code Snippet]]

While this structure runs fine in a single process, it does not harness the full potential of multiprocessing to allow each coroutine to operate independently.

The Solution: Using Multiprocessing with Asyncio

To achieve the functionality you need, we can utilize Python's multiprocessing library in tandem with asyncio. Here’s a structured approach to accomplish this.

Step-by-Step Breakdown

1. Define Your Coroutine Class

Keep your existing App class which manages the asynchronous operations.

[[See Video to Reveal this Text or Code Snippet]]

2. Create a Worker Function

Define a function that creates an instance of your App class and runs the coroutine. This function will handle interruptions:

[[See Video to Reveal this Text or Code Snippet]]

3. Set Up the Multiprocessing Pool

Use a multiprocessing pool to run each coroutine in its separate process:

[[See Video to Reveal this Text or Code Snippet]]

Important Considerations

Limit the Number of Processes: It’s crucial to limit the number of processes in your pool to min(len(jobs), os.cpu_count()). This prevents uninitialized workers from causing exceptions when an interruption occurs.

Graceful Shutdown: By capturing KeyboardInterrupt, you ensure a smooth shutdown of your coroutines without leaving resources hanging.

Conclusion

This method provides an effective way to run multiple asyncio coroutines in separate processes while maintaining control over them, especially when it comes to managing shutdowns. Now, if your application needs to run more than one coroutine simultaneously and independently, you can do so with confidence!

With this approach, you can enhance your Python applications by ensuring they are not only responsive but also robust against unexpected terminations.