Python Choosing a Date and Time Representation

Choose date, time, datetime or numeric timestamps according to the question.

How It Works

Use date for birthdays and days on a calendar; time for wall-clock scheduling; datetime with timezone for an instant; timedelta for elapsed periods. POSIX timestamps describe an instant relative to an epoch. Avoid mixing naive local datetimes with aware UTC values.

Use zoneinfo for real geographic timezone rules instead of inventing a fixed UTC offset.

Step-by-Step Example

from datetime import date, datetime, timedelta, timezone

birthday = date(2000, 7, 9)
created_at = datetime(2026, 10, 17, 12, tzinfo=timezone.utc)
trial_length = timedelta(days=14)
print(birthday.year)
print(int(created_at.timestamp()))
print(trial_length.days)

Understanding the Example

• The expression 'date(2000, 7, 9)' supplies the value stored as 'birthday'. This value is then used or checked by the later statements.
• The expression 'datetime(2026, 10, 17, 12, tzinfo=timezone.utc)' supplies the value stored as 'created_at'. This value is then used or checked by the later statements.

A successful run of this example prints the following output:

2000
1792238400
14

Where This Fits in a Real Program

For event timestamps, distinguish the displayed local clock from the instant that it represents. Store or exchange an unambiguous aware value, then convert it when displaying it to a user. For repeated calendar appointments, use a geographic timezone so daylight-saving rules are not lost.

Practice: Try It Yourself

Choose a type for a birthday, a server log event and a stopwatch interval.

For this exercise, predict the result before running the changed code. Then explain the difference between the original and modified cases using the actual values, not just whether the program completed.

Further Reading

Read the official Python documentation for complete parameters, return types and exceptions.

Common Beginner Mistakes

• Saving an appointment as an unlabeled timestamp and later interpreting it in the wrong timezone.
• Using a fixed 30-day timedelta as if it were always one calendar month.

Key Takeaways

• Choose date, time, datetime or numeric timestamps according to the question.
• Use date for birthdays and days on a calendar; time for wall-clock scheduling; datetime with timezone for an instant; timedelta for elapsed periods.
• Use zoneinfo for real geographic timezone rules instead of inventing a fixed UTC offset.