<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>TOML on Nalar</title>
    <link>https://nalar.dev/tags/toml/</link>
    <description>Recent content in TOML 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/toml/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Parse TOML Configuration Safely with Python tomllib</title>
      <link>https://nalar.dev/parse-toml-configuration-safely-with-tomllib/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/parse-toml-configuration-safely-with-tomllib/</guid>
      <description>&lt;p&gt;Python 3.11 added &lt;code&gt;tomllib&lt;/code&gt;, giving applications a standard-library parser for TOML configuration files. That removes a dependency for a common task, but parsing is only one part of loading configuration correctly.&lt;/p&gt;&#xA;&lt;p&gt;A configuration loader still needs to decide how large an input may be, what keys and types are accepted, whether floating-point values require exact decimal semantics, and how syntax errors should be reported. It also needs to remember that &lt;code&gt;tomllib&lt;/code&gt; reads TOML; it is not a TOML writer or a schema validator.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
