PyCharm debugger naive datetime interpretation defaults to IDE time zone without visual distinction

Direct answer

In PyCharm's Python debugger, naive datetime objects are most likely rendered using the global IDE time zone configured under Settings > Appearance & Behavior > System Settings > Time Zone, not UTC. There is no known project-level or per-run-configuration override for this presentation. This is a likely explanation from model knowledge, not a confirmed specification for every PyCharm build; the exact rendering behavior is version-sensitive and should be verified against your specific IDE version.

Likely behavior vs. confirmed facts

The confirmed, observable behavior is that timezone-aware datetime values display their UTC offset or tzinfo information in the Variables and Watches panes. The likely, but unconfirmed, behavior is that naive values are interpreted through the IDE's global time-zone setting without a visual marker distinguishing them from aware values. Because the debugger does not annotate naive objects, a displayed value alone cannot prove whether tzinfo is present.

What you can control

The only presentation control identified in model knowledge is the global IDE time-zone setting. Changing that setting affects other IDE displays and is risky on shared machines. A safer approach is to normalize datetimes at the code boundary: attach an explicit zone with zoneinfo.ZoneInfo or convert to UTC before the value reaches the debugger, rather than relying on debugger rendering.

Verification steps for your build

To confirm the behavior on your exact PyCharm version, run a minimal script with both object types and compare rendering:

from datetime import datetime, timezone
naive = datetime(2026, 10, 18, 12, 0, 0)
aware = datetime(2026, 10, 18, 12, 0, 0, tzinfo=timezone.utc)
breakpoint()  # or set a manual breakpoint here

1. Toggle the IDE Time Zone setting between the system default and UTC, then rerun the same breakpoint. If only the naive value changes while the aware value remains fixed, the IDE time zone is driving the naive presentation.
2. In the same session, evaluate naive.tzinfo, naive.utcoffset(), aware.tzinfo, and aware.utcoffset() in a watch or evaluate expression. These expose the actual object state independent of the debugger's display.
3. Check your PyCharm build's help documentation or release notes for any debugger datetime rendering changes.

Regarding the open issue

The referenced YouTrack issue should be treated as an unresolved product decision, not a roadmap commitment. Do not assume a future switch to UTC or to IDE-local rendering until release notes or the issue state are verified.

One diagnostic detail that changes the recommendation

If your IDE Time Zone is already set to UTC and naive values still shift when the system clock changes, the behavior differs from the likely explanation above; in that case, the controlling factor may be the JVM or OS default rather than the IDE setting, and the normalization advice becomes more urgent.