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 [1].
Among other things, APScheduler can be used as a cross-platform, application specific replacement to platform specific schedulers, such as the cron daemon or the Windows task scheduler. Please note, however, that APScheduler is not a daemon or service itself, nor does it come with any command line tools. It is primarily meant to be run inside existing applications. That said, APScheduler does provide some building blocks for you to build a scheduler service or to run a dedicated scheduler process.
APScheduler has three built-in scheduling systems you can use:
Cron-style scheduling (with optional start/end times)
Interval-based execution (runs jobs on even intervals, with optional start/end times)
One-off delayed execution (runs jobs once, on a set date/time)
You can mix and match scheduling systems and the backends where the jobs are stored any way you like. Supported backends for storing jobs include:
Memory
SQLAlchemy (any RDBMS supported by SQLAlchemy works)
APScheduler also integrates with several common Python frameworks, like:
Documentation
Documentation can be found here.
Source
The source can be browsed at Github.
Reporting bugs
A bug tracker is provided by Github.
Getting help
If you have problems or other questions, you can either:
Ask on the #apscheduler channel on Freenode IRC
Ask on the APScheduler Google group, or
Ask on StackOverflow and tag your question with the apscheduler tag
Metadata
Release files for APScheduler 3.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| APScheduler-3.3.1.tar.gz | 84.2 kB | Without provenance | Details for APScheduler-3.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| APScheduler-3.3.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for APScheduler-3.3.1-py2.py3-none-any.whl |
Total release size: 141.2 kB
Release files / APScheduler-3.3.1.tar.gz
| Download URL | APScheduler-3.3.1.tar.gz |
|---|---|
| Size | 84.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f68874dff1bdffcc6ce3adb7840c1e4d162c609a3e3f831351df30b75732767b
|
|
BLAKE2b-256 checksum How to use checksums |
43207131b30b6476366a536f46095a31750b77aa4b643984f7bcbbed96cf2126
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / APScheduler-3.3.1-py2.py3-none-any.whl
| Download URL | APScheduler-3.3.1-py2.py3-none-any.whl |
|---|---|
| Size | 57.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
bc9f96e498adb362beb5f1d3715a2570d100183add4ace5227c1a7d5dbaac900
|
|
BLAKE2b-256 checksum How to use checksums |
22ffeb9d27536f25253c09573cc7afc6db9708ea0abad02f5ac031b412d5cbda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for APScheduler 3.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.