django-timezone-field
A Django app providing DB, form, and REST framework fields for zoneinfo and pytz timezone objects.
Decision gist · record as of 2026-08-14
Yes. The package is actively maintained, has no known vulnerabilities, low install friction, and solves a real Django need—timezone field handling—across models, forms, and REST APIs. It cleanly handles the pytz-to-zoneinfo transition and is compatible with current Django versions (4.2 through 6.1). Install it if you need timezone storage and validation in Django.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Django 4.2 or later; if using pytz instead of zoneinfo, pytz must be installed separately.
- Low friction: pure Python wheel with only Django and backports.zoneinfo as runtime dependencies.
- Actively maintained with recent releases supporting Django 6.1 and Python 3.14.
License · maintenance · safety
BSD-2-Clause (permissive) — BSD-2-Clause permissive license allows commercial and private use with minimal restrictions.
last release 2026-06-06 (69 days) · last repo commit 2026-06-06 · 414 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 8,827,989 downloads/mo, #1,592 on PyPI
Alternatives
Verify before relying
pip install django-timezone-field
from django.db import models
class MyModel(models.Model):
tz = TimeZoneField(default="UTC")
my_model = MyModel()
my_model.tz # returns zoneinfo.ZoneInfo object by default- Whether tzdata package is automatically installed or must be added separately for full IANA timezone coverage on systems with incomplete timezone databases.
What it is and what it does
django-timezone-field bridges Django models, forms, and REST serializers with Python's timezone handling, letting you store timezone identifiers in the database and retrieve them as either zoneinfo or pytz objects. It handles the transition from pytz to zoneinfo by supporting both, with defaults that follow Django's own deprecation timeline: zoneinfo is the default for Django 4.0+, while Django 5.0+ drops pytz support entirely and this package follows suit.
The package stores timezone values as strings in the database but automatically converts them to timezone objects on retrieval, validates against known timezone names, and renders timezone choices in forms with optional GMT offset display. It works across Django's ORM, form validation, and Django REST Framework serialization without requiring data migrations when switching between pytz and zoneinfo.
Use it for
- Store user or location timezone preferences in a Django model and retrieve them as timezone objects for datetime operations.
- Build a form or API endpoint where users select their timezone from a validated dropdown or choice field.
- Migrate an existing Django project from pytz to zoneinfo while keeping the same database schema and field behavior.
- Display timezone choices with GMT offsets in admin or user-facing forms for clarity (e.g., 'GMT+04:00 Asia/Dubai').
- Serialize timezone data in Django REST Framework APIs, accepting and returning timezone identifiers as strings.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
The package is actively maintained, has no known vulnerabilities, low install friction, and solves a real Django need—timezone field handling—across models, forms, and REST APIs. It cleanly handles the pytz-to-zoneinfo transition and is compatible with current Django versions (4.2 through 6.1). Install it if you need timezone storage and validation in Django.
Install
django-timezone-field on PyPI
Before you install
Low friction: pure Python wheel with only Django and backports.zoneinfo as runtime dependencies. Actively maintained with recent releases supporting Django 6.1 and Python 3.14.
Requires Django 4.2 or later; if using pytz instead of zoneinfo, pytz must be installed separately.
License in practice
BSD-2-Clause permissive license allows commercial and private use with minimal restrictions.
Quickstart
pip install django-timezone-field
from django.db import models
class MyModel(models.Model):
tz = TimeZoneField(default="UTC")
my_model = MyModel()
my_model.tz # returns zoneinfo.ZoneInfo object by defaultVerify before relying
- Whether tzdata package is automatically installed or must be added separately for full IANA timezone coverage on systems with incomplete timezone databases.
Package facts
| License | BSD-2-Clause permissive |
| Python support | Supports the current Python release <4.0,>=3.8 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagesDjangobackports.zoneinfo |
| Maintenance | Actively maintained 69 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 8,827,989 / month, #1,592 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaEnvironment :: Web EnvironmentFramework :: DjangoFramework :: Django :: 4.2Framework :: Django :: 5.0Framework :: Django :: 5.1Framework :: Django :: 5.2Framework :: Django :: 6.0Framework :: Django :: 6.1Intended Audience :: DevelopersLicense :: OSI Approved :: BSD LicenseOperating System :: OS IndependentProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9Topic :: Utilities |
Evidence: django_timezone_field-7.2.2-py3-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 › “django timezone field”
- django-timezone-fieldProvides Django database, form, and REST framework fields for storing…
- django-choices-fieldProvides Django model fields that store and retrieve Django's…
- mssql-djangoDjango database backend that connects Django applications to…
Give your agent the search over MCP, or paste the wish link into any chat.
More Utilities packages
Converts domain names between Unicode and ASCII-compatible encoding (Punycode) according to IDNA 2008 and Unicode Technical Standard 46, with security validation and broader script coverage than the standard library.
Install it if you work with internationalized domain names, need to validate domains, or use HTTP clients that depend on it transitively.
Detects and normalizes text encoding from unknown or ambiguous sources, supporting all IANA character sets that Python's core library provides codecs for, with the ability to register custom codecs.
Setuptools is a Python build backend and package management tool that handles building, distributing, and installing Python packages, including support for C/C++ extension modules.
Pluggy provides a plugin system that lets you define hook specifications and register implementations to be called in sequence, enabling extensible Python applications without tight coupling.
Install it if you're building an extensible application or framework.
Pygments is a syntax highlighter that colorizes source code and text in over 500 languages and formats, outputting to HTML, LaTeX, RTF, SVG, images, or ANSI terminal sequences.
Install it if you need to display or transform source code.
Six provides utility functions to write Python code that runs on both Python 2.7 and Python 3.3+, smoothing over language differences between the two versions.
See also pytz · pytzdata · backports.zoneinfo · tzfpy · pytz-deprecation-shim · DateTime · tzlocal · django-localflavor · l18n · tzdata