<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ruff on René Welches</title><link>https://blog.renewelches.com/tags/ruff/</link><description>Recent content in Ruff on René Welches</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 07 Apr 2026 11:45:10 -0400</lastBuildDate><atom:link href="https://blog.renewelches.com/tags/ruff/index.xml" rel="self" type="application/rss+xml"/><item><title>Switching from Black to Ruff for Python Formatting in VS Code</title><link>https://blog.renewelches.com/2026/04/07/vscode-python-formatting-ruff/</link><pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.renewelches.com/2026/04/07/vscode-python-formatting-ruff/</guid><description>&lt;h1 id="switching-from-black-to-ruff-for-python-formatting-in-vs-code"&gt;Switching from Black to Ruff for Python Formatting in VS Code&lt;/h1&gt;
&lt;p&gt;In a &lt;a href="https://blog.renewelches.com/2025/11/11/vscode-python-formatter/"&gt;previous post&lt;/a&gt; I set up Black, isort, and Mypy to keep my Python code clean in VS Code. That setup worked well for a while, but I kept running into a frustrating problem: whenever I followed along with official examples from Anthropic or other third-party libraries, VS Code would light up with dozens of errors. The strict Black + Mypy configuration was fighting me more than helping me.&lt;/p&gt;</description></item></channel></rss>