<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Date and Time on Nalar</title>
    <link>https://nalar.dev/tags/date-and-time/</link>
    <description>Recent content in Date and Time on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/date-and-time/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Handle Time Zones Correctly with Python zoneinfo</title>
      <link>https://nalar.dev/handle-time-zones-correctly-with-python-zoneinfo/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/handle-time-zones-correctly-with-python-zoneinfo/</guid>
      <description>&lt;p&gt;Time-zone code becomes difficult when an application needs more than a fixed UTC offset. Civil-time rules change, daylight-saving transitions can repeat or skip local clock readings, and the rules for a place are not captured by labels such as UTC+7 or UTC-5.&lt;/p&gt;&#xA;&lt;p&gt;Python 3.9 added &lt;code&gt;zoneinfo&lt;/code&gt; to the standard library to provide IANA time-zone support through the familiar &lt;code&gt;datetime&lt;/code&gt; API. It is the right starting point when an application needs rules for named zones such as &lt;code&gt;Asia/Jakarta&lt;/code&gt;, &lt;code&gt;Europe/Berlin&lt;/code&gt;, or &lt;code&gt;America/New_York&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
