--- title: "#493: CalVer and LTS" url: https://daily.dev/posts/493-calver-and-lts-zsmdgihad source_url: https://pythonbytes.fm/episodes/show/493/calver-and-lts type: article source: "Planet Python" published: 2026-08-26T01:52:11.124Z updated: 2026-08-26T01:59:15.738Z tags: ["python", "django", "cpython"] reading_time: 9 upvotes: 1 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # #493: CalVer and LTS **[Planet Python](https://daily.dev/sources/planetpython)** · 9 min read · 1 upvotes · 0 comments ## Summary A roundup of Python community news covering three self-hosted web UI projects for Traefik, nginx, and Caddy reverse proxies; Wagtail 8.0's release with custom base page models, a new read/write REST API, and security fixes; CPython officially adding RISC-V as a tier 3 supported platform under PEP 11; and Django's plan starting with Django 2028 to move to annual calendar-versioned releases where every version gets three years of support, eliminating the old LTS/non-LTS distinction. Extra links cover Python docs adding time-complexity notes, a free book, a uv Python-pruning script, and Ollama cloud models. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Is RISC-V officially supported by CPython now? Yes, CPython added RISC-V as a tier 3 platform under PEP 11, specifically targeting 64-bit Linux via riscv64-unknown-linux-gnu. Tier 3 means a core developer contact and buildbot exist and breakage gets noticed, but failures do not block releases, there are no python.org installers, and binary wheel parity for native extensions is not guaranteed. _Track platform support changes like this on daily.dev before porting Python workloads to new architectures._ ### When will Django switch to calendar versioning and annual LTS-style releases? Starting with Django 2028, Django moves to one feature release every January, adopts calendar-based version numbers, and supports each release for three years total: one year of mainstream bug fixes followed by two years of security and data-loss fixes. This removes the separate LTS designation since every release becomes long-supported. Three versions stay supported at once, and nothing changes before 2028, so Django 5.2 LTS and 6.2 LTS commitments remain intact. _Follow Django's release cadence shift on daily.dev to plan upgrade paths ahead of the 2028 change._ ### What changed in Wagtail 8.0? Wagtail 8.0 adds support for custom base page models so projects no longer have to subclass Wagtail's default Page, introduces a new v3 REST API that handles both read and write CMS operations for the first time, adds a global permission policy registry, and stops auto-converting AVIF and WebP images to PNG by default. It also ships five security fixes and formalizes Django 6.1 support with uv-based CI. _Check breaking changes like the AVIF/WebP conversion default before upgrading Wagtail with daily.dev._ ## Similar posts on daily.dev - [PyCoder’s Weekly](https://daily.dev/posts/pycoder-s-weekly-oekitkw2s) · Planet Python · 0 upvotes · 0 comments - [PyCoder’s Weekly](https://daily.dev/posts/pycoder-s-weekly-q28dvgitx) · Planet Python · 0 upvotes · 0 comments --- Tags: [#python](https://daily.dev/tags/python), [#django](https://daily.dev/tags/django), [#cpython](https://daily.dev/tags/cpython) [View this post on daily.dev](https://daily.dev/posts/493-calver-and-lts-zsmdgihad)