This release is a pre-release and may not be stable for production use.
Advanced Python Scheduler (APScheduler) is a task scheduler and task queue system for Python. It can be used solely as a job queuing system if you have no need for task scheduling. It scales both up and down, and is suitable for both trivial, single-process use cases as well as large deployments spanning multiple nodes. Multiple schedulers and workers can be deployed to use a shared data store to provide both a degree of high availability and horizontal scaling.
APScheduler comes in both synchronous and asynchronous flavors, making it a good fit for both traditional, thread-based applications, and asynchronous (asyncio or Trio) applications. Documentation and examples are provided for integrating with either WSGI or ASGI compatible web applications.
Support is provided for persistent storage of schedules and jobs. This means that they can be shared among multiple scheduler/worker instances and will survive process and node restarts.
The built-in persistent data store back-ends are:
PostgreSQL
MySQL and derivatives
SQLite
MongoDB
The built-in event brokers (needed in scenarios with multiple schedulers and/or workers):
PostgreSQL
Redis
MQTT
The built-in scheduling mechanisms (triggers) are:
Cron-style scheduling
Interval-based scheduling (runs tasks on even intervals)
Calendar-based scheduling (runs tasks on intervals of X years/months/weeks/days, always at the same time of day)
One-off scheduling (runs a task once, at a specific date/time)
Different scheduling mechanisms can even be combined with so-called combining triggers (see the documentation for details).
You can also implement your custom scheduling logic by building your own trigger class. These will be treated no differently than the built-in ones.
Other notable features include:
You can limit the maximum number of simultaneous jobs for a given task (function)
You can limit the amount of time a job is allowed to start late
Jitter (adjustable, random delays added to the run time of each scheduled job)
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 in the apscheduler room on Gitter
Post a question on GitHub discussions, or
Post a question on StackOverflow and add the apscheduler tag
1 maintainer
Metadata
1 maintainer
Release files for APScheduler 4.0.0a6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| apscheduler-4.0.0a6.tar.gz | 3.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apscheduler-4.0.0a6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 MB
Release files / apscheduler-4.0.0a6.tar.gz
| Download URL | apscheduler-4.0.0a6.tar.gz |
|---|---|
| Size | 3.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5134617c028f097de4a09abbeefc42625cb0ce3adcb4ce49d74cc26054084761
|
|
BLAKE2b-256 checksum How to use checksums |
407fca0404dac83438b5dcb75c797092381040320be84f3af098cf9a486529e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 27, 2025.
Transparency logRelease files / apscheduler-4.0.0a6-py3-none-any.whl
| Download URL | apscheduler-4.0.0a6-py3-none-any.whl |
|---|---|
| Size | 88.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87031f7537aaa6ea2d3e69fdd9454b641f18938fc8cd0c589972006eceba8ee9
|
|
BLAKE2b-256 checksum How to use checksums |
3dbd35b5691919859a906cd098d62e2a1399cb8ede3e05b6480cf15d472ad5b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 27, 2025.
Transparency log
