Freya / The Compiler

@the_compiler
853 Followers
363 Following
110 Posts
Likes #Python. Writing #qutebrowser, a vim-like webbrowser (see @qutebrowser). #pytest maintainer, with company trainings/coaching via https://bruhin.software
qutebrowserhttps://www.qutebrowser.org/
Pronounsshe/they
Join Freya Bruhin (@the_compiler) at EuroPython for "Property based testing with Hypothesis" talk: https://ep2026.europython.eu/NEH7RE

My #pytest quick reference brochures finally arrived at #PyConDE 🥰

Find them at this desk at the entrance, or at the community sponsors desk in the Lounge (first floor). Please take as many as you (and/or your colleagues) need, I have 500 here weighing in at >30kg, and I am here by train 😅

#Python

I wanted to design a #pytest cheat sheet for a while, finally started last week to have it ready for #PyConDE.

I wanted to have a 6 page leaflet (A4 split into thirds), then hyperfocus kicked, and I ended up with a 40 page booklet instead! 🤯

I ordered 500 copies to my hotel, if all goes well they will arrive on Wed. Make sure to get yours, or I'll have to figure out a way to get 30kg home safely again 😅.

Released under CC BY-ND: https://github.com/The-Compiler/pytest-quick-ref

PDF: https://pyte.st/ref.pdf

#Python

GitHub - The-Compiler/pytest-quick-ref: PDF/paper cheat sheet for pytest

PDF/paper cheat sheet for pytest. Contribute to The-Compiler/pytest-quick-ref development by creating an account on GitHub.

GitHub
Burn-in testing or did we get this wrong?

"The brain for nose was dropped. nose has been deprecated for 10 years and the brain required some maintenance."

Ah yes, programmers naming things!

source: https://github.com/pylint-dev/astroid/blob/main/ChangeLog

astroid/ChangeLog at main · pylint-dev/astroid

A common base representation of python source code for pylint and other projects - pylint-dev/astroid

GitHub

I have some big news to share: My name and pronouns changed! 🎉

After more than a year of self-discovery and a sometimes exhausting double identity, it finally felt like the right time to take this big step. Big kudos to everyone who I told in person in the last couple of months, I'm glad to have received nothing but support from amazing people.

A new chapter has barely started, and to say I'm excited seems like an understatement!

So, a weird thing happened today.

I built a desktop out of the spare parts from my wife's desktop, and did a fresh Arch install. I'm installing a bunch of needed software, and decided to install a bunch of browsers, just to try some; I've been using LibreWolf for quite a while.

First one I try is @qutebrowser and... it instantly feels like home, even before I've tweaked key bindings. It reminds me very much of my old project Coconut, which was also a PyQt-based browser.

Feels good to be home.

Your `pip` unwrapped 🎇

- you tried to install `requirements.txt` 18 times this year. Doing better than last year!
- of the packages you installed 67% started with py, 11% python, and 6% Py. You guessed wrong 85 times.
- your love for building source has no bounds, except maybe the 92 failed compiles
- you updated `requests` 18 times. Urllib is feeling lonely.
- the average time between updating `pip` was 97 days. But we warned you 338 times!

In short: our costs have gone up, our assets and revenue have gone down, and demand for the PSF’s work continues to grow. Meanwhile, Python usage is surging (which is great!), but corporate investment in the language and community hasn’t kept pace.
Even still, we’re raising the flag early: the PSF has only ~6 months of runway and needs your support to sustain essential #Python & #PyPI infrastructure, #PyConUS, and, hopefully, to reopen our Grants Program.