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

Unresolved naive datetime rendering in the Python debugger

PyCharm's debugger displays timezone-aware datetime objects with their UTC offset, but naive datetime objects are rendered in the configured IDE time zone without any visual indicator that they lack timezone information. An open YouTrack issue debates whether naive datetimes should be assumed UTC or local time, leaving the default interpretation unresolved.

The IDE time zone setting (Settings > Appearance & Behavior > System Settings > Time Zone) governs this presentation, yet no project-level override or explicit annotation exists to differentiate naive from aware objects in the Variables or Watches panes. Code inspections for zoneinfo added in 2023.3 flag ambiguous conversions but do not enforce a project-wide time zone policy.

This behavior affects debugging sessions where naive datetimes originate from third-party libraries or legacy code, making it difficult to verify whether displayed values reflect UTC, the system zone, or the IDE override.

• What is the current default assumption for naive datetimes in the debugger—UTC or the IDE time zone—and is it documented for a given PyCharm version?
• Can the interpretation be configured per project or per debug configuration without changing the global IDE setting?
• Does the open YouTrack issue indicate a planned change that would alter the rendering in a future release?