<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pyright on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pyright/</link>
    <description>Recent content in Pyright on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 02 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pyright/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Python Type Checking: MyPy vs Pyright vs Pyre vs Pytype vs Beartype</title>
      <link>https://www.pistack.xyz/posts/2026-07-02-python-type-checkers-mypy-pyright-pyre-pytype-beartype/</link>
      <pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-02-python-type-checkers-mypy-pyright-pyre-pytype-beartype/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Python&amp;rsquo;s dynamic typing is both its greatest strength and its most notorious weakness. While duck typing enables rapid prototyping, it also allows entire categories of bugs to slip through to production — &lt;code&gt;AttributeError&lt;/code&gt;, &lt;code&gt;TypeError&lt;/code&gt;, and &lt;code&gt;NoneType&lt;/code&gt; errors are among the most common Python exceptions in production logs. Static type checking bridges this gap, catching type errors at development time without sacrificing Python&amp;rsquo;s flexibility.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
