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!

@jer Hah! 🙃

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.

When we shared last week that we withdrew from a U.S. government grant due to conflicts with our mission, the community showed incredible support. 1400+ donors and 270+ new members raised $135K+ in solidarity– thank you!! We've also had 3 new companies apply for sponsorship 🤯🥰

@glyph I hope I'm not too late! 😅

My next open in-depth #pytest trainings:

🇨🇭 October 29th to 31st, Zurich, Switzerland, with letsboot.ch: https://www.letsboot.ch/kurs/pytest
🇩🇪 🌍 March 3rd to 5th, Leipzig, Germany & Remote, with Python Academy: https://python-academy.com/courses/python_course_testing.html

@xavdid thanks forwarded to @treyhunner who did the cheatsheet part of it :)

#Python's f-strings have a super powerful templating language built in! But I always forget the exact syntax. Well, no longer! h/t @the_compiler / @treyhunner

https://fstring.help/cheat/

#qutebrowser #art #linux #MastoArt #flathub

https://flathub.org/de/apps/org.qutebrowser.qutebrowser

@flathub

@Venty liebe Grüsse zurück!

I'm delighted to announce that my introductory #pytest training ("simple, rapid and fun testing with #Python") has been accepted for both @pyconde as well as @europython! See you in Darmstadt 🇩🇪 and/or Prague 🇨🇿?

I'm already working on the next CfP, for the CH Open https://workshoptage.ch/ 🇨🇭!

@liw I feel called out. 🙃

@RussSharek @hpk I don't think there is a good solution, other than Flatpak / AppImage / standalone binaries / etc. as a workaround for people using stable distros. But people will continue installing from repos, because for many applications that might be the right thing to do (IMHO stable distributions are the wrong approach entirely for desktop systems, but I digress).

I was thinking of adding a time-bomb that warns if your qutebrowser/Qt is too old. But that seems like a slippery slope.

@RussSharek @hpk Unfortunately not an edge case. It happens over and over again that this kind of thing gets attributed to qutebrowser (case in point, "an alternative browser can't read github issues", "I hope the internals eventually catch up"), but the issue is that your OS ships an insecure and heavily outdated *browser engine* and calls that "stable".

It's arguable if that makes sense for other apps, but it certainly doesn't for a browser, especially not when ignoring security fixes.

@RussSharek @hpk Indeed a packaging issue. Some distributions (mostly Debian Stable, and by extension Ubuntu LTS and Linux Mint) give you a heavily outdated QtWebEngine/Chromium backend, and with that, a rendering engine that's more outdated than what many websites are comfortable with (plus one that lacks years of security fixes!).

qutebrowser always supports the newest Qt by the time that's released (and usually with the first Alpha/Beta release).

...whoops, I must have accidentally checked the 2024 Pretalx for PyConDE instead of 2025. At the time of writing the original toot, there was no acceptance yet, and it turns out that the basic training ("pytest - simple, rapid and fun testing with Python") was accepted for this year at #PyConDE.

⏰ Only a week remaining with early-bird pricing for my annual three-day deep dive into #pytest with #Python Academy!
📅 March 4th — 6th
🌍 Leipzig (Germany) or remote
📕 Three days of pytest knowledge from one of its core maintainers. Fixtures, mocking, plugins, …

https://python-academy.com/courses/python_course_testing.html

🎉 In related news: My "pytest tips and tricks" 1.5h training for #PyConDE was accepted, and I also submitted that plus a more beginner-focused pytest training for #Europython!

#qutebrowser is 11 years old, almost on the minute! I'm celebrating by releasing v3.4.0: https://listi.jpberlin.de/pipermail/qutebrowser/2024-December/000960.html