<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Python on JVQ.net</title>
    <link>https://jvq.net/tags/python/</link>
    <description>Recent content in Python on JVQ.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jvq.net/tags/python/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>jvq Catches a Python Cleanup That Made URL Parsing Nearly Five Times Slower</title>
      <link>https://jvq.net/jvq-catches-a-python-cleanup-that-made-url-parsing-nearly-five-times-slower/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://jvq.net/jvq-catches-a-python-cleanup-that-made-url-parsing-nearly-five-times-slower/</guid>
      <description>&lt;p&gt;A log pipeline pulls query parameters out of request paths, millions of times a day. The function that does it is eight lines of hand-written splitting. It&amp;rsquo;s fast, and it has a bug everyone has learned to live with: &lt;code&gt;%20&lt;/code&gt; and &lt;code&gt;+&lt;/code&gt; come through undecoded.&lt;/p&gt;&#xA;&lt;p&gt;So someone opens a pull request that fixes it the proper way, with the standard library. Two lines replace eight. The review is easy to approve. This is a worked example we set up to show what jvq does with a change like that: a small repository with a pytest-benchmark suite, four real commits, and jvq 0.5.0 run on each one on a two-core cloud VM.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
