01
Enqueue
Move email, webhooks, or media work out of the request path with one clear handoff.
Python-native background work
Background jobs, without the heavy setup.
Python Job Queue gives web teams a focused path from a request to a dependable background job, without asking them to absorb a heavier queue stack first.
For email, webhooks, media processing, and the work that should not block a request.
worker / defaultready
queue03
worker01
enqueue()
no request wait
no request wait
run()
in the background
in the background
current job
send_welcome_email
A small mental model: enqueue the work, let a worker run it, keep the request moving.
01 / The shift
Let the request stay focused.
02
Process
Let a worker pick up the job while your web response does what it came to do.
03
Understand
Keep the job lifecycle legible, so background work feels like application code, not a second product.
The Python fit
Familiar code. Fewer moving parts.
02 / Why Python
Built for the stack your team already speaks.
A Python-native queue should feel like an extension of your web app, not an infrastructure exam. The aim is a quick path to dependable jobs with less configuration than heavier queue stacks.
01 Straightforward setup
02 Clear job handoff
03 Python-native feel
04 Room to grow
03 / Start here
The first job should be the easy part.
Start with a decorator, enqueue from your application, and let the worker take it from there. The documentation is designed around that first useful loop.
Read the documentation ↗jobs.pypython
@job
def send_welcome_email(user_id):
user = get_user(user_id)
send_email(user.email)
send_welcome_email.enqueue(user.id)