async_sched
Use async to have functions run on a schedule.
Example
Async Sched can run tasks on a schedule. It can also receive new tasks (in limited fashion) and change the running schedules without stopping the service.
scheduler.py
schedules/
task1.py
task2.py
# scheduler.py
import async_sched
srv = async_sched.start_server(('127.0.0.1', 8000),
update_path='./schedules',
global_server=True)
# srv.add('3 Second', async_sched.Schedule(seconds=3), print, 'Hello 3 seconds')
srv.run_forever()
Task 1 in the schedules directory will automatically be imported. Because start_server sets the server as an accessible attribute with get_server we can dynamically add schedules.
# schedules/task1.py
from async_sched import get_server, Schedule
import datetime
def print_task1():
print('Hello! I am task 1 ' + str(datetime.datetime.now()))
s = Schedule(seconds=30, repeat=True)
# This will remove an existing 'Task 1' and schedule a new 'Task 1'
server = get_server()
server.add('Task 1', s, print_task1)
In the task 2 file we are not scheduling any commands, but we are registering a callback function that can be run from a client later.
# schedules/task2.py
from async_sched import get_server, Schedule
import datetime
server = get_server()
@server.register_callback # or @server.register_callback('print_task2')
def print_task2(name):
print('Task 2 is running! ', name, str(datetime.datetime.now()))
Now run the scheduler server to listen to remote commands and manage the running schedules.
python scheduler.py
# or python -m async_sched.server.run –path “schedules” –host “127.0.0.1” –port 8000
Use a client to print the running schedules.
python -m async_sched.client.request_schedules –host “127.0.0.1” –port 8000
Reload the files in the ./schedules/ directory.
python -m async_sched.client.update server –host “127.0.0.1” –port 8000
Stop a schedule that is running.
python -m async_sched.client.stop_schedule “Task 1” –host “127.0.0.1” –port 8000
Run a registered callback function.
python -m async_sched.client run_command “print_task2” “hello” –host “127.0.0.1” –port 8000
Schedule a registered command.
python -m async_sched.client schedule_command “print_task2” “hello” –seconds 10 –host “127.0.0.1” –port 8000
Metadata
Release files for async-sched 1.2.5
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 |
|---|---|---|---|---|
| async_sched-1.2.5.tar.gz | 17.7 kB | Without provenance | Details for async_sched-1.2.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| async_sched-1.2.5-py3-none-any.whl | Python 3 | none | any | Details for async_sched-1.2.5-py3-none-any.whl |
Total release size: 78.0 kB
Release files / async_sched-1.2.5.tar.gz
| Download URL | async_sched-1.2.5.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c6e51e4fc1a99ac986bbf4fe6b5b382c04f01e10c7c82584194b068ff03393a
|
|
BLAKE2b-256 checksum How to use checksums |
97ad9ff4d09d4171d817489876b42dc3123c0e0e1307dd87b4702ef222a403c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.1
|
Release files / async_sched-1.2.5-py3-none-any.whl
| Download URL | async_sched-1.2.5-py3-none-any.whl |
|---|---|
| Size | 60.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a8324994e0a5f0daacdbb3776529693690112b12519d227536079e51e855307
|
|
BLAKE2b-256 checksum How to use checksums |
b8782d6a39f1efdf051a12decfdeab09b1d6779947bdff9752eee6c6024c6aed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.1
|
Security for async-sched 1.2.5
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.