Introduction

The error TypeError: can't compare offset-naive and offset-aware datetimes occurs when you compare a datetime object without timezone information (naive) to one with timezone information (aware). This commonly happens when datetime.now() (naive) is compared to a database-stored datetime that includes timezone data (aware). The fix is to make both datetimes the same type — either both naive or both aware. The recommended approach is to always use timezone-aware datetimes with datetime.now(timezone.utc).

The Error

1from datetime import datetime, timezone
2
3# Naive datetime (no timezone)
4naive_now = datetime.now()
5# 2025-03-02 10:30:00
6
7# Aware datetime (has timezone)
8aware_time = datetime.now(timezone.utc)
9# 2025-03-02 18:30:00+00:00
10
11# This raises TypeError
12if naive_now < aware_time:
13    print("Before")
14# TypeError: can't compare offset-naive and offset-aware datetimes

Python refuses to compare them because it cannot know what timezone the naive datetime is in — the comparison would be meaningless.

Fix 1: Make Both Aware (Recommended)

1from datetime import datetime, timezone
2
3# Use timezone-aware datetime.now()
4now = datetime.now(timezone.utc)
5
6# Compare with another aware datetime
7challenge_end = datetime(2025, 12, 31, 23, 59, 59, tzinfo=timezone.utc)
8
9if now < challenge_end:
10    print("Challenge is still active")

Always using datetime.now(timezone.utc) instead of datetime.now() prevents this error entirely.

Fix 2: Add Timezone to a Naive Datetime

1from datetime import datetime, timezone
2
3naive_now = datetime.now()  # No timezone
4
5# Option 1: replace() — assumes the naive datetime is in UTC
6aware_now = naive_now.replace(tzinfo=timezone.utc)
7
8# Option 2: Use pytz for other timezones
9import pytz
10eastern = pytz.timezone("US/Eastern")
11aware_now = eastern.localize(naive_now)
12
13# Option 3: Use zoneinfo (Python 3.9+)
14from zoneinfo import ZoneInfo
15aware_now = naive_now.replace(tzinfo=ZoneInfo("America/New_York"))

replace(tzinfo=...) attaches a timezone without converting the time value. localize() from pytz is the correct way to assign a timezone to a naive datetime in older Python.

Fix 3: Make Both Naive

1from datetime import datetime, timezone
2
3aware_time = datetime(2025, 12, 31, tzinfo=timezone.utc)
4
5# Strip timezone info to make it naive
6naive_time = aware_time.replace(tzinfo=None)
7
8naive_now = datetime.now()
9
10if naive_now < naive_time:
11    print("Before the deadline")

This approach loses timezone information, which can cause subtle bugs if the datetimes were originally in different timezones. Prefer making both aware instead.

Django-Specific Fix

Django stores aware datetimes when USE_TZ = True in settings. Comparing with datetime.now() triggers this error:

1from django.utils import timezone
2
3# WRONG: naive datetime
4from datetime import datetime
5if datetime.now() < challenge.datetime_end:  # TypeError
6    pass
7
8# FIX: use Django's timezone.now()
9if timezone.now() < challenge.datetime_end:
10    print("Challenge active")
11
12# Or make a datetime aware using Django's utility
13from django.utils.timezone import make_aware
14naive_dt = datetime(2025, 6, 15, 12, 0)
15aware_dt = make_aware(naive_dt)  # Uses TIME_ZONE setting

Always use django.utils.timezone.now() instead of datetime.now() in Django projects with USE_TZ = True.

Converting Between Timezones

1from datetime import datetime, timezone
2from zoneinfo import ZoneInfo  # Python 3.9+
3
4# Create an aware datetime in UTC
5utc_time = datetime.now(timezone.utc)
6
7# Convert to other timezones
8eastern = utc_time.astimezone(ZoneInfo("America/New_York"))
9tokyo = utc_time.astimezone(ZoneInfo("Asia/Tokyo"))
10
11print(f"UTC:     {utc_time}")
12print(f"Eastern: {eastern}")
13print(f"Tokyo:   {tokyo}")
14
15# All three compare correctly — they represent the same instant
16print(utc_time == eastern == tokyo)  # True

Aware datetimes in different timezones can be compared directly because Python converts them to a common reference (UTC) internally.

Checking if a Datetime is Naive or Aware

1from datetime import datetime, timezone
2
3def is_aware(dt):
4    return dt.tzinfo is not None and dt.tzinfo.utcoffset(dt) is not None
5
6naive = datetime.now()
7aware = datetime.now(timezone.utc)
8
9print(is_aware(naive))  # False
10print(is_aware(aware))  # True
11
12# Safe comparison function
13def safe_compare(dt1, dt2):
14    if is_aware(dt1) != is_aware(dt2):
15        raise ValueError("Cannot compare naive and aware datetimes")
16    return dt1 < dt2

Common Pitfalls

• Using datetime.now() instead of datetime.now(timezone.utc): datetime.now() returns a naive datetime with no timezone information. In any application that stores or receives timezone-aware datetimes, this causes comparison errors. Always pass a timezone argument.
• Using replace(tzinfo=...) to convert timezones: replace() attaches a timezone label without adjusting the time value. To convert between timezones, use astimezone() instead. dt.replace(tzinfo=utc) says "this time IS UTC" while dt.astimezone(utc) says "convert this time TO UTC".
• Mixing pytz and zoneinfo: Python 3.9+ has zoneinfo in the standard library. Using both pytz and zoneinfo in the same project can create incompatible timezone objects. Pick one and use it consistently.
• Stripping timezone from database datetimes: Converting aware datetimes to naive with replace(tzinfo=None) loses timezone information and can cause incorrect comparisons if the original datetimes were in different timezones. Keep everything aware instead.
• Forgetting USE_TZ = True in Django: Without USE_TZ = True, Django stores naive datetimes. When you later enable it, existing naive datetimes in the database conflict with new aware datetimes, causing this error across the application.

Summary

• The error occurs when comparing a naive datetime (no timezone) with an aware datetime (has timezone)
• Fix by making both aware: use datetime.now(timezone.utc) instead of datetime.now()
• In Django, use django.utils.timezone.now() when USE_TZ = True
• Use replace(tzinfo=...) to label a naive datetime, use astimezone() to convert between timezones
• Python 3.9+ provides zoneinfo in the standard library as a replacement for pytz
• Always work with aware datetimes throughout your application to avoid this class of bugs entirely