Trove Classifiers and Data Optimization in Python

• * Mozilla’s Lifeline is Safe After Judge’s Google Antitrust Ruling*
• * troml - suggests or fills in trove classifiers for your projects*
• * pqrs: Command line tool for inspecting Parquet files*
• * Testing for Python 3.14*
• Extras
• Joke

About the show

Sponsored by us! Support our work through:

• Our courses at Talk Python Training
• The Complete pytest Course
• Patreon Supporters

Connect with the hosts

• Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky)
• Brian: @brianokken@fosstodon.org / @brianokken.bsky.social
• Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky)

Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too.

Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it.

Michael #1: Mozilla’s Lifeline is Safe After Judge’s Google Antitrust Ruling

• A judge lets Google keep paying Mozilla to make Google the default search engine but only if those deals aren’t exclusive.
• More than 85% of Mozilla’s revenue comes from Google search payments.
• The ruling forbids Google from making exclusive contracts for Search, Chrome, Google Assistant, or Gemini, and forces data sharing and search syndication so rivals get a fighting chance.

Brian #2: troml - suggests or fills in trove classifiers for your projects

• Adam Hill
• This is super cool and so welcome.
• Trove Classifiers are things like <code>Programming Language :: Python :: 3.14</code> that allow for some fun stuff to show up in PyPI, like the versions you support, etc.
• Note that just saying you require 3.9+ doesn’t tell the user that you’ve actually tested stuff on 3.14. I like to keep Trove Classifiers around for this reason.
• Also, License classifier is deprecated, and if you include it, it shows up in two places, in Meta, and in the Classifiers section. Probably good to only have one place. So I’m going to be removing it from classifiers for my projects.
• One problem, classifier text has to be an exact match to something in the classifier list, so we usually recommend copy/pasting from that list.
• But no longer! Just use troml!
• It just fills it in for you (if you run troml suggest --fix). How totally awesome is that!
• I tried it on pytest-check, and it was mostly right. It suggested me adding 3.15, which I haven’t tested yet, so I’m not ready to add that just yet. :)
• BTW, I talked with Brett Cannon about classifiers back in ‘23 if you want some more in depth info on trove classifiers.

Michael #3: pqrs: Command line tool for inspecting Parquet files

• pqrs is a command line tool for inspecting Parquet files
• This is a replacement for the parquet-tools utility written in Rust
• Built using the Rust implementation of Parquet and Arrow
• pqrs roughly means "parquet-tools in rust"
• Why Parquet?
  • Size
    • A 200 MB CSV will usually shrink to somewhere between about 20-100 MB as Parquet depending on the data and compression. Loading a Parquet file is typically several times faster than parsing CSV, often 2x-10x faster for a full-file load and much faster when you only read some columns.
  • Speed
    • Full-file load into pandas: Parquet with pyarrow/fastparquet is usually 2x–10x faster than reading CSV with pandas because CSV parsing is CPU intensive (text tokenizing, dtype inference).
      • Example: if read_csv is 10 seconds, read_parquet might be ~1–5 seconds depending on CPU and codec.
    • Column subset: Parquet is much faster if you only need some columns — often 5x–50x faster because it reads only those column chunks.
    • Predicate pushdown & row groups: When using dataset APIs (pyarrow.dataset) you can push filters to skip row groups, reducing I/O dramatically for selective queries.
    • Memory usage: Parquet avoids temporary string buffers and repeated parsing, so peak memory and temporary allocations are often lower.

Brian #4: Testing for Python 3.14

• Python 3.14 is just around the corner, with a final release scheduled for October.
• What’s new in Python 3.14
• Python 3.14 release schedule
• Adding 3.14 to your CI tests in GitHub Actions
  • Add “3.14” and optionally “3.14t” for freethreaded
  • Add the line allow-prereleases: true
• I got stuck on this, and asked folks on Mastdon and Bluesky
• A couple folks suggested the allow-prereleases: true step. Thank you!
• Ed Rogers also suggested Hugo’s article Free-threaded Python on GitHub Actions, which I had read and forgot about. Thanks Ed! And thanks Hugo!

Extras

Brian:

• dj-toml-settings : Load Django settings from a TOML file. - Another cool project from Adam Hill
• LidAngleSensor for Mac - from Sam Henri Gold, with examples of creaky door and theramin
• Listener Bryan Weber found a Python version via Changelog, pybooklid, from tcsenpai
• Grab PyBay

Michael:

• Ready prek go! by Hugo van Kemenade

Joke: Console Devs Can’t Find a Date