How to Install and Uninstall python312-pyinotify Package on openSuSE Tumbleweed

Last updated: November 08,2024

1. Install "python312-pyinotify" package

This guide covers the steps necessary to install python312-pyinotify on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python312-pyinotify
            
                    
    
    Copied

2. Uninstall "python312-pyinotify" package

Please follow the guidance below to uninstall python312-pyinotify on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python312-pyinotify
            
                    
    
    Copied

3. Information about the python312-pyinotify package on openSuSE Tumbleweed

Information for package python312-pyinotify:
--------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-pyinotify
Version : 0.9.6-5.7
Arch : noarch
Vendor : openSUSE
Installed Size : 321.1 KiB
Installed : No
Status : not installed
Source package : python-pyinotify-0.9.6-5.7.src
Upstream URL : https://github.com/seb-m/pyinotify
Summary : Python module for watching filesystems changes
Description :
pyinotify is a Python module for watching filesystems changes. By its design
pyinotify can be used for any kind of fs monitoring.
pyinotify relies on a recent Linux Kernel feature (merged in kernel 2.6.13)
called inotify. inotify is an event-driven notifier, its notifications are
exported from kernel space to user space. The raw interface of inotify is
compounded of three system calls. pyinotify binds these system calls and
provides an implementation on top of them offering a generic and abstract way
to use inotify with Python. Pyinotify doesn't requires much detailed knowledge
of inotify. Moreover, it only needs few statements for initializing, watching,
handling (eventually trough a new separate thread), and processing events
notifications through subclassing. The only things to know is the path of items
to watch, the kind of events to monitor and the actions to execute on these
notifications.