Runtime time zone mismatch during region-specific date parsing

Google Colab runtimes operate on a default UTC time zone. When processing datasets containing region-specific timestamps or performing date conversions, the lack of a localized system clock can lead to unexpected offsets in time-series analysis.

While libraries like pytz or zoneinfo can handle conversions within a script, the underlying runtime environment remains anchored to UTC. This creates a discrepancy between the local system time and the intended regional time zone for the analysis.

What is the most efficient method to synchronize the Colab runtime's system-level time zone with a specific region? Does modifying the environment variable TZ persist across all cells in a single session, or is a programmatic approach required for every date-parsing operation?