timeloop
An elegant way to run period tasks.
Decision gist · record as of 2026-08-14
No. The package is abandoned (last release 2019-02-12, no maintenance since 2022-12-29) and Python support is unspecified, creating risk for compatibility issues with modern Python versions. For new projects, use a maintained alternative. For existing code already using timeloop, migration is low-friction given the simple API, but do not adopt it for new work.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Python support is unspecified; compatibility with modern Python versions is not documented.
- Installation is frictionless with no runtime dependencies.
- However, the package is abandoned—last release was 2019-02-12, over 2740 days ago, with no maintenance activity since 2022-12-29.
License · maintenance · safety
MIT (permissive) — MIT license is permissive, allowing commercial and private use with minimal restrictions.
last release 2019-02-12 (2740 days) · last repo commit 2022-12-29 · 245 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 161,467 downloads/mo, #10,629 on PyPI
Alternatives
Verify before relying
from timeloop import Timeloop
from datetime import timedelta
tl = Timeloop()
@tl.job(interval=timedelta(seconds=2))
def sample_job():
print("Job executed")
tl.start()
tl.stop()- Whether the package works reliably with modern Python versions given unspecified Python support.
- Whether thread-safety guarantees hold under concurrent job execution or high load.
- Whether graceful shutdown actually waits for all in-flight tasks before returning.
What it is and what it does
Timeloop is a lightweight scheduler that runs decorated functions at fixed intervals using separate threads. You define jobs with a decorator specifying a timedelta interval, then call start() to begin execution. Each job runs in its own thread, and the service handles graceful shutdown by waiting for all currently executing tasks to finish before stopping.
The package is designed for simple periodic task patterns—background maintenance jobs, polling loops, or recurring checks. It offers two modes: non-blocking (start in a background thread, requiring manual stop() on exit) and blocking (start in the main thread with automatic graceful shutdown on signal). No external dependencies are required, making it a minimal addition to any project.
Use it for
- Run background maintenance tasks at regular intervals without external job queues.
- Implement polling loops that check an external service at fixed time intervals.
- Schedule periodic health checks or monitoring tasks within a long-running application.
- Execute recurring data synchronization or batch processing jobs on a simple interval schedule.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
No.
The package is abandoned (last release 2019-02-12, no maintenance since 2022-12-29) and Python support is unspecified, creating risk for compatibility issues with modern Python versions. For new projects, use a maintained alternative. For existing code already using timeloop, migration is low-friction given the simple API, but do not adopt it for new work.
Install
timeloop on PyPI
Before you install
Installation is frictionless with no runtime dependencies. However, the package is abandoned—last release was 2019-02-12, over 2740 days ago, with no maintenance activity since 2022-12-29. Use only if you accept that no updates or bug fixes will be forthcoming.
Python support is unspecified; compatibility with modern Python versions is not documented.
License in practice
MIT license is permissive, allowing commercial and private use with minimal restrictions.
Quickstart
from timeloop import Timeloop
from datetime import timedelta
tl = Timeloop()
@tl.job(interval=timedelta(seconds=2))
def sample_job():
print("Job executed")
tl.start()
tl.stop()
Verify before relying
- Whether the package works reliably with modern Python versions given unspecified Python support.
- Whether thread-safety guarantees hold under concurrent job execution or high load.
- Whether graceful shutdown actually waits for all in-flight tasks before returning.
Package facts
| License | MIT permissive |
| Python support | Not specified |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Abandoned 2,740 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 161,467 / month, #10,629 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: timeloop-1.0.2-py2-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “periodic task scheduler”
- timeloopTimeloop runs periodic tasks at fixed intervals on separate threads,…
- sqlalchemy-celery-beatProvides a SQLAlchemy-backed scheduler for Celery that stores…
- celery-redbeatRedBeat is a Celery Beat scheduler that persists scheduled tasks and…
Give your agent the search over MCP, or paste the wish link into any chat.
More Monitoring packages
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
Provides generated Python code for OpenTelemetry semantic conventions, enabling standardized attribute naming and constant definitions for instrumentation and telemetry collection.
Install it if you are using OpenTelemetry and want to follow semantic conventions correctly.
Provides the reference implementation of the OpenTelemetry API for collecting and exporting traces, metrics, and logs from Python applications.
Provides the abstract API and interfaces for OpenTelemetry instrumentation in Python, defining how to emit traces, metrics, and logs without tying code to a specific SDK implementation.
Exports OpenTelemetry observability data to an OpenTelemetry Collector using Protobuf-encoded messages over HTTP.
Install it if you are using OpenTelemetry in Python and need to send data to a Collector over HTTP.
Provides automatic instrumentation commands and programmatic APIs to inject distributed tracing into Python applications without code changes, detecting and instrumenting packages used by your program.
Install it if you need distributed tracing without code changes and have compatible instrumented packages in your environment.
See also schedule · rq-scheduler · APScheduler · scheduler · aiojobs · django-crontab · django-apscheduler · streamlit-autorefresh · Flask-APScheduler · openjd-sessions