How to Install and Uninstall python310-APScheduler Package on openSuSE Tumbleweed

Last updated: November 23,2024

1. Install "python310-APScheduler" package

Please follow the step by step instructions below to install python310-APScheduler on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python310-APScheduler
            
                    
    
    Copied

2. Uninstall "python310-APScheduler" package

This is a short guide on how to uninstall python310-APScheduler on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python310-APScheduler
            
                    
    
    Copied

3. Information about the python310-APScheduler package on openSuSE Tumbleweed

Information for package python310-APScheduler:
----------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-APScheduler
Version : 3.10.4-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 363.6 KiB
Installed : No
Status : not installed
Source package : python-APScheduler-3.10.4-1.2.src
Upstream URL : https://github.com/agronholm/apscheduler
Summary : In-process task scheduler with Cron-like capabilities
Description :
Advanced Python Scheduler (APScheduler) is an in-process task
scheduler that lets you schedule jobs (functions or any python callables) to be
executed at any time of your choosing.
This can be an alternative to externally run cron scripts for
long-running applications (e.g. web applications), as it is platform neutral
and can access the application's variables and functions.
APscheduler provides multiple job stores.
* Configurable scheduling mechanisms (triggers):
* Cron-like scheduling
* Delayed scheduling of single run jobs (like the UNIX "at" command)
* Interval-based (run a job at specified time intervals)
* Multiple, simultaneously active job stores:
* RAM
* File-based simple database (shelve)
* SQLAlchemy (any supported RDBMS works)
* MongoDB