pico-scheduling

Scheduled method execution for the pico ecosystem: @scheduled on component methods, powered by APScheduler.

Installation

pip install pico-scheduling

Auto-discovered by pico-boot; with plain pico-ioc add "pico_scheduling" to init(modules=[...]).

Quick start

from pico_ioc import component
from pico_scheduling import scheduled

@component
class Reports:
    @scheduled(every=300)          # every 5 minutes
    def refresh_cache(self): ...

    @scheduled(cron="0 3 * * *")   # 03:00 daily
    async def nightly_rollup(self): ...

Jobs start when the container starts and stop on container.shutdown(). Each run resolves the component through the container (prototype scope gives a fresh instance per run). A failing job is logged and does not stop the schedule. Sync and async methods both work.

Disable everything with config:

scheduling:
  enabled: false

Documentation

Full documentation: https://dperezcabrera.github.io/pico-scheduling/

Built for AI-assisted development

pico-scheduling is part of an ecosystem designed for humans and coding agents building software together. Every package ships AGENTS.md working conventions, an llms.txt machine-readable docs index and documented behaviour pinned by regression tests; pico-testing gives agents a verification loop for their own changes, and releases are gated by the whole ecosystem booting together against real infrastructure. The full story: Built for AI-assisted development.

Install the agent skills for Claude Code or OpenAI Codex:

curl -sL https://raw.githubusercontent.com/dperezcabrera/pico-skills/main/install.sh | bash

The pico-conventions skill teaches the assistant this module's API surface and invariants; /add-component and /add-tests scaffold components and tests that use it.

License

MIT