How to Install and Uninstall python312-nest-asyncio Package on openSuSE Tumbleweed

Last updated: November 23,2024

1. Install "python312-nest-asyncio" package

Here is a brief guide to show you how to install python312-nest-asyncio on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python312-nest-asyncio
            
                    
    
    Copied

2. Uninstall "python312-nest-asyncio" package

In this section, we are going to explain the necessary steps to uninstall python312-nest-asyncio on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python312-nest-asyncio
            
                    
    
    Copied

3. Information about the python312-nest-asyncio package on openSuSE Tumbleweed

Information for package python312-nest-asyncio:
-----------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-nest-asyncio
Version : 1.6.0-1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 25.6 KiB
Installed : No
Status : not installed
Source package : python-nest-asyncio-1.6.0-1.4.src
Upstream URL : https://github.com/erdewit/nest_asyncio
Summary : Patch asyncio to allow nested event loops
Description :
By design asyncio `does not allow `_
its event loop to be nested. This presents a practical problem:
When in an environment where the event loop is
already running it's impossible to run tasks and wait
for the result. Trying to do so will give the error
"``RuntimeError: This event loop is already running``".
The issue pops up in various environments, such as web servers,
GUI applications and in Jupyter notebooks.
This module patches asyncio to allow nested use of ``asyncio.run`` and
``loop.run_until_complete``.