Season's Savings | ₹5/mo for 3 months

₹199/month after first 3 months. Renews automatically. Terms apply.
#505 Introducing diskcache-oxide cover art

#505 Introducing diskcache-oxide

#505 Introducing diskcache-oxide

Listen for free

View show details
About this listen
Topics covered in this episode: tinyjobs: a SQLite job queue goes free-threadedfunkycache: cache Python functions in SQLiteGhostman - a keyboard-driven terminal API clientdiskcache-oxide: A shared, durable disk cacheExtrasJokeWatch on YouTube About the show Sponsored by LongLink: pythonbytes.fm/longlink Connect with the hosts Michael: Mastodon / BlueSky / X / LinkedInCalvin: Mastodon / BlueSky / X / LinkedInShow: Mastodon / BlueSky / X Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: tinyjobs: a SQLite job queue goes free-threaded tinyjobs is a Python job queue and cron scheduler that starts with a SQLite file and no dependencies. Switch the URL to Postgres or Redis without rewriting tasks. It runs async tasks natively, embeds workers in FastAPI, and plugs into Django 6's tasks framework. The creator's free-threading audit found four races hidden by the GIL. Background jobs without deploying a broker, plus a concrete case study in what removing the GIL exposes.The creator reports races in the task registry, codec cache, cross-thread flag and thread pool. hiredis can re-enable the GIL; the worker warns when it detects that.On 3.14t, --loops N runs event loops in separate threads. The author's laptop benchmark hit 42,000 async jobs/s with eight loops and two Redis instances, close to eight processes. SQLite rejects loops above one.Clock-skew lesson: two hosts 20 minutes apart duplicated 492 of 3,000 jobs on 0.7.0. Using Redis server time fixed that test, not the general exactly-once problem.Author's SQLite measurements: about 572 jobs/s end-to-end; a 20,000-job burst drained in four seconds. Synthetic workloads and different harnesses, not interchangeable throughput claims.At-least-once delivery still requires idempotent tasks. Python 3.12+; young project, with the README now listing v0.11.0 versus the email's v0.9.0. Docker setup: services: web: build: . command: uvicorn main:api --host 0.0.0.0 volumes: [jobs:/data] worker: build: . command: tinyjobs worker --app tasks:app --shutdown-timeout 25 stop_grace_period: 40s volumes: [jobs:/data] volumes: jobs: external: true Calvin #2: funkycache: cache Python functions in SQLite Alex Chan's functools.cache-style decorator stores results in SQLite, so they survive after the process exits. He built it to speed up his static site build.It's released on PyPI: funkycache 1.0.4, from November 15. The first release, 1.0.0, came out November 7. It needs Python 3.14+ and depends on pydantic and xxhash.Usage: cache = FunkyCache(storage="sqlite"), then @cache.register(files=[...], values=[...]). A cache entry is invalidated when the function's source file changes or when any listed file or value changes, such as a library version.Return values go through Pydantic's TypeAdapter, based on the return type hint, so it only works on typed code.Generators get special handling. functools.cache hands every caller the same generator object. funkycache saves the output as a list and gives each caller a fresh iterator, up to a soft memory limit.Cache keys are JSON hashed with XXH64. They're deliberately lossy, and that's fine because nothing reads the original arguments back out of a key.The design notes are a good segment on their own: the author had used MD5 because they "conflated weak with fast," and in their limited testing JSON was faster than pickle and easier to debug.With a warm cache the site builds in about half a second, and the library is only a few hundred lines including tests. It doesn't watch files on purpose, to stay small. Calvin #3: Ghostman - a keyboard-driven terminal API client A local-first Postman alternative that runs in the terminal, with no cloud account required. It's MIT licensed and was featured in PyCoder's Weekly #760.It's released on PyPI: pip install ghostman, then run ghostman. The current version is 0.1.8, from November 3. The first release, 0.1.0, came out October 31. It needs Python 3.10+.It's built on Textual, httpx and Rich, so it's pure Python under the hood.It sends GET, POST, PUT, DELETE and PATCH requests, shows DNS and time-to-first-byte timing live, and colors JSON responses automatically.A built-in webhook inspector: Ctrl+W starts a listener on port 9090. Captured payloads show headers and timestamps, and you can load one straight into the request editor.Collections are plain JSON/YAML files you can commit to Git. The README gives two different folders for them (.ghostman/ and ~/.ghostman/).It's fully keyboard-driven: Ctrl+S sends, Ctrl+K saves, Ctrl+N starts a new request, Ctrl+Q quits.The author claims about 30MB of RAM and a cold start of about 150ms; I haven't checked either number. It's a young project, with 158 stars and 15 commits. ...
adbl_web_anon_alc_button_suppression_t1
No reviews yet