<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pydantic on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pydantic/</link>
    <description>Recent content in Pydantic on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 03 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pydantic/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Python Data Class Libraries: dataclasses vs attrs vs Pydantic vs cattrs vs dataclasses-json</title>
      <link>https://www.pistack.xyz/posts/2026-07-03-python-data-class-libraries-dataclasses-attrs-pydantic-cattrs/</link>
      <pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-03-python-data-class-libraries-dataclasses-attrs-pydantic-cattrs/</guid>
      <description>&lt;p&gt;Python 3.7 introduced &lt;code&gt;dataclasses&lt;/code&gt; as a stdlib way to reduce boilerplate when defining data containers. Since then, a rich ecosystem of complementary and competing libraries has emerged — each offering different trade-offs in validation, serialization, and performance. For Python developers building APIs, data pipelines, or configuration systems, understanding these options is essential.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
