Python-native / idea stage

Move slow work out of requests.

A simple, Python-native background job queue for small teams.

Keep web requests focused when emails, reports, imports, and other long-running tasks need somewhere else to run. The intended hand-off is straightforward: enqueue the work, let a worker run it, and handle the result separately.

Read the documentation See the hand-off

At this stage

The product is currently an idea. Customer outcomes, reliability, and production requirements still need to be validated.

Conceptual API shapePY / 01

01 queue = Queue()
02 queue.enqueue(send_email, to=user.email)
03 queue.enqueue(generate_report, user_id=user.id)
04 queue.run() # start worker

Emails · reports · imports · long-running tasks

Illustrative flow

NO LIVE JOB

01Request path

The request stays focused.

A long-running task is ready to leave the web request.

Status

Ready to hand off

01 / 04

The example shows the intended mechanism; it does not install a queue or execute work from this page.

01 / The mechanism

The request returns to being a request.

The problem is not every task. It is the work that makes a request wait: sending an email, generating a report, processing an import. A queue creates a clear boundary between asking for the work and doing the work.

Enqueue the work

Give the queue a Python callable and the arguments it needs for an email, report, import, or other slow task.

Run a worker

Let a worker process the queued job outside the web request that created it.

Handle the result

Treat the job outcome as its own flow instead of making the original request wait for every step.

02 / The trade-off

Choose the boundary you want to operate.

Small Python teams often choose between keeping slow work in a request, building an in-process or custom runner, or taking on a more complex queue and its surrounding infrastructure. python job queue is being shaped around a simpler Python-native path.

Current workaround

Keep the work in the request.

The request stays responsible for every step, even when the work is better suited to a background process.

Intended direction

Hand the work to a worker.

A clear API and minimal setup are the provisional promise: move long-running work out of the request path without unnecessary infrastructure complexity.

03 / Setup notes

Start with the smallest useful hand-off.