How to Install and Uninstall python3-APScheduler.noarch Package on Fedora 35
Last updated: January 11,2025
1. Install "python3-APScheduler.noarch" package
This is a short guide on how to install python3-APScheduler.noarch on Fedora 35
$
sudo dnf update
Copied
$
sudo dnf install
python3-APScheduler.noarch
Copied
2. Uninstall "python3-APScheduler.noarch" package
Please follow the instructions below to uninstall python3-APScheduler.noarch on Fedora 35:
$
sudo dnf remove
python3-APScheduler.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the python3-APScheduler.noarch package on Fedora 35
Last metadata expiration check: 5:15:18 ago on Wed Sep 7 08:25:01 2022.
Available Packages
Name : python3-APScheduler
Version : 3.7.0
Release : 4.fc35
Architecture : noarch
Size : 103 k
Source : python-APScheduler-3.7.0-4.fc35.src.rpm
Repository : fedora
Summary : In-process task scheduler with Cron-like capabilities
URL : https://github.com/agronholm/apscheduler
License : MIT
Description : Advanced Python Scheduler (APScheduler) is a Python library that lets you
: schedule your Python code to be executed later, either just once or
: periodically. You can add new jobs or remove old ones on the fly as you
: please. If you store your jobs in a database, they will also survive
: scheduler restarts and maintain their state. When the scheduler is
: restarted, it will then run all the jobs it should have run while it was
: offline.
Available Packages
Name : python3-APScheduler
Version : 3.7.0
Release : 4.fc35
Architecture : noarch
Size : 103 k
Source : python-APScheduler-3.7.0-4.fc35.src.rpm
Repository : fedora
Summary : In-process task scheduler with Cron-like capabilities
URL : https://github.com/agronholm/apscheduler
License : MIT
Description : Advanced Python Scheduler (APScheduler) is a Python library that lets you
: schedule your Python code to be executed later, either just once or
: periodically. You can add new jobs or remove old ones on the fly as you
: please. If you store your jobs in a database, they will also survive
: scheduler restarts and maintain their state. When the scheduler is
: restarted, it will then run all the jobs it should have run while it was
: offline.