NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #4727 most downloaded on PyPI
Django template coverage.py plugin
Last release 6 months ago
04 Apr 2026
Release timing varies
gaps range from 5 weeks to 1.9 years
Most releases are documented
notes for 20 of 31 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
35 releases · first in 2015
Fix: {% endblock %} lines (and others) were falsely reported as unexecuted when they appeared on their own indented line (issue 74). Thanks, Marc Gibb
Drop Python 3.9 and Django 2.2. Add Python 3.14.
Drop Python 3.9 and Django 2.2. Add Python 3.14.
One column per quarter.
Support changes: dropped Python 3.8, added Python 3.13. Added Django 5.2.
Support changes: dropped Python 3.8, added Python 3.13. Added Django 5.2.
Dropped support for Python 3.7 and Django 1.x. Declared support for Python 3.12.
Dropped support for Python 3.7 and Django 1.x. Declared support for Python 3.12.
Dropped support for Python 2.7, Python 3.6, and Django 1.8.
Dropped support for Python 2.7, Python 3.6, and Django 1.8.
Declare our support for Python 3.11 and Django 4.1.
Declare our support for Python 3.11 and Django 4.1.
Nothing published for this version
If a non-UTF8 file was found when looking for templates, it would fail when reading during the reporting phase, ending execution. This failure is now
If a non-UTF8 file was found when looking for templates, it would fail when reading during the reporting phase, ending execution. This failure is now raised in a way that can be ignored with a .coveragerc setting of [report] ignore_errors=True (issue 78).
When using source=., an existing coverage HTML report directory would be found and believed to be unmeasured HTML template files. This is now fixed.
Test and claim our support on Python 3.10.
Test and claim our support on Python 3.10.
Drop support for Python 3.4 and 3.5.
Drop support for Python 3.4 and 3.5.
A setting is available: template_extensions lets you set the file extensions that will be considered when looking for unused templates (requested in issue 60).
Fix an issue on Windows where file names were being compared case-sensitively, causing templates to be missed (issue 46).
Fix an issue (issue 63) where tag libraries can't be found if imported during test collection. Thanks to Daniel Izquierdo for the fix.
Add support for: - Coverage 5
Add support for:
Add support for: - Python 3.7 & 3.8 - Django 2.2 & 3.0
Add support for:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Removes support for Django versions below 1.8. Validates support for Django version 1.11b1
Removes support for Django versions below 1.8. Validates support for Django version 1.11b1
Fixes another instance of issue 32, which was the result of an initialization order problem.
Fixes another instance of issue 32, which was the result of an initialization order problem.
Nothing published for this version
Django 1.10.5 is now supported.
Django 1.10.5 is now supported.
Checking settings configuration is deferred so that settings.py is included in coverage reporting. Fixes issue 28.
Only the django.template.backends.django.DjangoTemplates template engine is supported, and it must be configured with ['OPTIONS']['debug'] = True. Fixes issue 27.
Settings are read slightly differently, so as to not interfere with programs that don't need settings. Fixes issue 18.
Settings are read slightly differently, so as to not interfere with programs that don't need settings. Fixes issue 18.
Multiple template engines are allowed. Thanks, Simon Charette.
Multiple template engines are allowed. Thanks, Simon Charette.
No change in code, but Django 1.9.2 is now supported.
No change in code, but Django 1.9.2 is now supported.
The template debug settings are checked properly for people still using TEMPLATE_DEBUG in newer versions of Django.
The template debug settings are checked properly for people still using TEMPLATE_DEBUG in newer versions of Django.
Check if template debugging is enabled in the settings, and raise a visible warning if not. This prevents mysterious failures of the plugin, and fixes
Check if template debugging is enabled in the settings, and raise a visible warning if not. This prevents mysterious failures of the plugin, and fixes issue 17.
Potential Django 1.9 support is included, but the patch to Django hasn't been applied yet.
Explicitly configure settings if need be to get things to work.
Explicitly configure settings if need be to get things to work.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →