Introduction

Printing every calendar date between two dates is a common task in reporting, scheduling, and data backfills. The core logic is simple, but real code still needs to decide whether the range is inclusive, how input strings are parsed, and how to avoid subtle bugs around time-of-day values.

Use date Objects For Day-By-Day Iteration

If you only care about calendar days, iterate with datetime.date rather than full timestamps. That removes timezone and hour-level noise from the problem.

1from datetime import date, timedelta
2
3
4def iter_days(start: date, end: date):
5    current = start
6    while current <= end:
7        yield current
8        current += timedelta(days=1)
9
10
11for day in iter_days(date(2025, 1, 1), date(2025, 1, 5)):
12    print(day, day.strftime("%A"))

This prints each date along with the weekday name. The <= comparison makes the range inclusive of both endpoints.

Parse Input Carefully

In real applications, dates often start as strings. Parse them once at the boundary of your program and convert them into date values before looping.

1from datetime import datetime
2
3
4def parse_date(value: str):
5    return datetime.strptime(value, "%Y-%m-%d").date()
6
7
8start = parse_date("2025-03-01")
9end = parse_date("2025-03-04")
10
11for day in iter_days(start, end):
12    print(day.isoformat(), day.strftime("%A"))

Keeping parsing separate from iteration makes the loop easier to test and reuse.

Inclusive Versus Exclusive End Dates

A lot of off-by-one bugs come from not deciding whether the end date belongs in the output. For a report that covers both March 1 and March 4, you want an inclusive loop. For a half-open interval that behaves like Python slices, you want to stop before the end date.

1from datetime import date, timedelta
2
3
4def iter_days_exclusive(start: date, end: date):
5    current = start
6    while current < end:
7        yield current
8        current += timedelta(days=1)
9
10
11for day in iter_days_exclusive(date(2025, 3, 1), date(2025, 3, 4)):
12    print(day)

That version prints March 1, 2, and 3 only.

Formatting The Output

Once you have a correct date iterator, formatting becomes trivial. For example, if you want Monday 2025-03-03:

for day in iter_days(date(2025, 3, 1), date(2025, 3, 3)):
    print(day.strftime("%A %Y-%m-%d"))

If the consumer is another program, prefer machine-friendly strings such as isoformat() instead of human-formatted text.

Returning A List Instead Of Printing

Functions are more reusable when they return data instead of printing directly.

1from datetime import date
2
3
4def list_days(start: date, end: date) -> list[str]:
5    return [day.isoformat() for day in iter_days(start, end)]
6
7
8print(list_days(date(2025, 3, 1), date(2025, 3, 3)))

This makes it easy to plug the result into an API response, a template, or a test assertion.

Handling Timestamps With Time Components

If the inputs are full timestamps, convert them to plain dates before iterating unless you explicitly want hour-level stepping.

1from datetime import datetime
2
3start_dt = datetime.fromisoformat("2025-03-01T17:30:00")
4end_dt = datetime.fromisoformat("2025-03-03T08:15:00")
5
6for day in iter_days(start_dt.date(), end_dt.date()):
7    print(day)

This prevents confusing behavior where two timestamps on the same calendar date compare differently because of their time-of-day portion.

Why pandas Is Usually Overkill Here

Libraries such as pandas can generate date ranges, but for simple day-by-day iteration the standard library is usually clearer and easier to deploy.

1import pandas as pd
2
3for day in pd.date_range("2025-03-01", "2025-03-03", freq="D"):
4    print(day.date())

That works, but pulling in pandas for a small utility function is often unnecessary unless the surrounding code is already built around DataFrames.

Common Pitfalls

The most common bug is off-by-one range logic. Another is mixing datetime values with date values and accidentally comparing timestamps instead of calendar days. Developers also frequently parse input inside the loop, which adds clutter and makes the code harder to test. If your application cares about time zones, convert the timestamps into the intended local date before stepping by whole days.

Summary

• Use date values and timedelta(days=1) for calendar-day iteration.
• Decide explicitly whether the end date is inclusive or exclusive.
• Parse input once, then loop over normalized date objects.
• Return data from helper functions when possible instead of printing directly.
• Convert timestamps to plain dates before iterating if only day-level output matters.