<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Env-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/env-management/</link>
    <description>Recent content in Env-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/env-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Python Configuration Libraries: Pydantic Settings vs Dynaconf vs python-decouple vs environs — Complete Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-06-22-python-configuration-libraries-pydantic-dynaconf-decouple-environs-guide/</link>
      <pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-22-python-configuration-libraries-pydantic-dynaconf-decouple-environs-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every Python application — whether a Django monolith, a FastAPI microservice, or a CLI tool — needs configuration. The Twelve-Factor App methodology prescribes storing configuration in environment variables, but raw &lt;code&gt;os.getenv()&lt;/code&gt; calls with manual type coercions become unmaintainable quickly. The Python ecosystem has evolved four mature libraries that bring structure to configuration management: &lt;strong&gt;Pydantic Settings&lt;/strong&gt; (type-validated, model-based), &lt;strong&gt;Dynaconf&lt;/strong&gt; (multi-source, layered), &lt;strong&gt;python-decouple&lt;/strong&gt; (lightweight, env-focused), and &lt;strong&gt;environs&lt;/strong&gt; (marshmallow-powered, Flask-friendly).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
