Introduction

Calculating "six months from today" sounds simple, but months are not a fixed number of days. datetime.timedelta cannot add calendar months directly, so the correct solution depends on whether you want true month arithmetic or an approximation such as 180 days. For most business logic, you want true calendar months.

Why timedelta Is Not Enough

timedelta handles days, seconds, and smaller fixed units. Months are variable in length, so this does not work reliably:

1from datetime import date, timedelta
2
3today = date(2024, 8, 31)
4wrong = today + timedelta(days=180)
5
6print(wrong)

Adding 180 days is not the same as adding six calendar months. Some month ranges cross February, leap years, or 30-day months. If you care about calendar meaning, use month-aware logic.

Recommended Approach: relativedelta

The easiest month-aware solution is dateutil.relativedelta. The python-dateutil package is not part of the standard library, but it is widely used and solves this problem correctly.

1from datetime import date
2from dateutil.relativedelta import relativedelta
3
4today = date.today()
5six_months_later = today + relativedelta(months=6)
6
7print(today)
8print(six_months_later)

This handles end-of-month behavior intelligently. For example:

1from datetime import date
2from dateutil.relativedelta import relativedelta
3
4print(date(2024, 1, 31) + relativedelta(months=1))
5print(date(2024, 8, 31) + relativedelta(months=6))

Output:

2024-02-29
2025-02-28

That is usually what people mean by "one month later" or "six months later." The day is preserved when possible, and if the target month is shorter, the result lands on the last valid day of that month.

Pure Standard Library Option

If you cannot use python-dateutil, you can implement month arithmetic with calendar.monthrange.

1from datetime import date
2import calendar
3
4def add_months(d, months):
5    month_index = d.month - 1 + months
6    year = d.year + month_index // 12
7    month = month_index % 12 + 1
8    last_day = calendar.monthrange(year, month)[1]
9    day = min(d.day, last_day)
10    return date(year, month, day)
11
12today = date.today()
13print(add_months(today, 6))

This helper:

• rolls the month forward across year boundaries
• clamps the day to the last valid day of the target month
• works for common calendar-date scenarios

For many codebases, this is a good fallback if external dependencies are undesirable.

datetime Versus date

If you also care about time-of-day, use datetime instead of date. The same idea applies, but you need to preserve hours, minutes, and timezone handling.

With dateutil:

1from datetime import datetime, timezone
2from dateutil.relativedelta import relativedelta
3
4now = datetime.now(timezone.utc)
5future = now + relativedelta(months=6)
6
7print(now.isoformat())
8print(future.isoformat())

If your application stores timezone-aware datetimes, keep them timezone-aware during the calculation. Adding months to a naive local datetime can create ambiguity later when the value moves across systems with different timezone assumptions.

Be Clear About The Business Rule

Different domains mean different things by "six months from now":

• subscription billing often means same day-of-month when possible
• legal or compliance rules may define month boundaries differently
• reporting systems may want "end of the month six months ahead"

For example, some business rules treat 2024-08-31 + 6 months as the last day of February. Others may prefer the first day of the following month for special cases. The code should reflect the real rule rather than relying on a vague phrase.

Testing Edge Cases

Month arithmetic bugs usually appear around boundary dates, so test them directly:

1from datetime import date
2
3test_dates = [
4    date(2024, 1, 31),
5    date(2024, 2, 29),
6    date(2024, 8, 31),
7    date(2024, 12, 15),
8]
9
10for d in test_dates:
11    print(d, "->", add_months(d, 6))

A few explicit tests are much better than assuming the same logic works for every month length.

Common Pitfalls

• Using timedelta(days=180) and calling it "six months."
• Thinking python-dateutil is part of the standard library. It is an external package.
• Forgetting end-of-month behavior such as January 31 or August 31.
• Mixing naive and timezone-aware datetime values in the same workflow.
• Writing month arithmetic once and never testing leap-year and month-end cases.

Summary

• 'timedelta cannot add true calendar months.'
• For most real applications, use relativedelta(months=6) from python-dateutil.
• If you need a standard-library-only solution, compute the target year, month, and last valid day manually.
• End-of-month behavior is the main source of surprises, so test it directly.
• Decide whether you want calendar months or an approximate day count before writing the code.