Hynek Schlawack
Software engineer and open-source maintainer of attrs and structlog; writes about Python, software design and career growth at hynek.me.
Hynek Schlawack did not write this page. ppll compiled it from their own words, each linked to the source. Is this you? · Report a mistake
Latest Bluesky
What they believe
-
Virtual environments do not measurably affect an application's runtime performance.
You can also disregard claims that virtual environments measurably affect your application's runtime performance.
hynek.meSaid 2 Sept 2024This on korrents
-
uv's bottom pinning simplifies dependency resolution by limiting the number of eligible versions.
On the other side, bottom pinning as employed by uv simplifies the resolution process by limiting the amount of eligible versions while resolving them.
youtube.comSaid 6 Jul 2025This on korrents
The bold line is korrents’ wording; the quote is theirs. These 2: what they wrote before what they said aloud, one per source, newest first.
Feed
As its own page →Hiding
20 November
15 November
14 November
13 November
4 November
2 November
1 November
28 October
22 October
21 October
19 October
17 October
11 October
6 September
4 September
2 September
Nothing matches.
Beliefs
Korrents What they believe 75 beliefs — each backed by an exact quote.
Each is a — compiled by korrents.com, not by them: the one-line wordings are korrents', the quotes are theirs.
Recent
uv's bottom pinning simplifies dependency resolution by limiting the number of eligible versions.
On the other side, bottom pinning as employed by uv simplifies the resolution process by limiting the amount of eligible versions while resolving them.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Calendar-based versioning is much more common than people may think, and top-pinning to the current major version falls on its face with it.
it isolates you from security updates once they're only available on a major version bump in semantic versioning and it completely falls on its face with calendar-based versioning that is much more common than you may think.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Optional development helpers such as debuggers are a matter of taste, so it is better to inject them per person than argue over which is best.
You can have an endless argument over what debugger is best, or you can accept that these development helpers a) are a matter of taste
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Show 57 more
pdbpp is the best Python debugger module.
Like the objectively best debugger module called pdbpp that has just found new maintainership and works on new python versions again, which makes me incredibly happy.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Running tools in module form with -m is recommended whenever possible, because it removes a moving part that can go wrong.
I still recommend everyone to use the -m form whenever possible, both with uv run and python itself. It just removes another moving part that can go wrong and despite uv, there's still plenty of moving parts left that can break.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Generative AI coding agents are more effective when given a quick way to get feedback on their own changes.
it's kind of experiencing a renaissance with generative AI coding agents that are much more effective at their hallucinations if you give them a quick way to obtain feedback to their own changes.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Contrary to common claims, makefiles are not standardized, since GNU and BSD make differ greatly.
Secondly, and contrary to common claims, they are very much not standardized. For example, there's a huge difference between GNU and BSD makes.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Make is a build tool, not a tool for running arbitrary commands, so it lacks affordances such as easily passing arguments.
Make, as the name indicates, is for building things, usually software, and not running arbitrary commands. Which means that it is lacking affordances that you like to have, like easily passing arguments to a target, and that you occasionally have to fight make's instincts.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Developers should use just instead of make as their command runner.
So after literally decades of making do with make, and after years of living with a great alternative, I'm here to say just use just instead.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
People should not be afraid to create shell aliases for commands they use a lot.
And you too shouldn't be afraid to create aliases for commands you use a lot. It's your shell, make it serve you.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Starting custom commands and aliases with a comma is a useful way to list only your own commands with tab completion.
But also consider starting your commands and aliases with a comma, such that comma tab presents you with a nice list of only your custom commands.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
With uv and a justfile, tox is no longer needed for applications.
I used to use tox for this, even though that it's not necessarily what it's been made for, but it's a great way to deterministically run commands in a Python environment. But with uv, I don't need that anymore for applications, since I have a just file anyway.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Overmind is much nicer than docker-compose for running multiple local processes at once.
But if you sometimes need to run multiple processes at once, like a web app and a worker, do check it out. It's much nicer to use than docker-compose
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Reading dotenv files automatically before executing would be a security risk.
Of course, just randomly reading dot env files before executing would be a security risk.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
uv run solves the problem of a local virtualenv falling out of date after pulling a co-worker's lock-file changes.
This means that the frequent gotcha of Git pulling some changes and your co-worker updated a bunch of dependencies in a lock file and your local virtualenv still has the old ones. It's solved forever.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Forcing a whole team to run code only through uv run might go too far and cause resistance.
people tend to get grumpy and defensive when you force new things on them. No matter how many serious problems it solves, replacing the plumbing can raise some grumbles but should be fine overall. But also forcing everyone to only run the code using uv run... This might be one bridge too far that could cause resistance.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Your shell can and should be fish.
It will look at how the envrc script changes the environment variables and then apply those changes back into your current shell which totally can and should be fish.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
uv being categorically faster enables new workflows, such as syncing and activating a virtualenv every time you enter a directory.
Being able to do this unconditionally is what Charlie Marsh means when he says that uv being categorically faster is enabling completely new workflows. This is one of them.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Creating educational material all year round can improve one's conference speaking.
Curiously, one of the most interesting compliments I got was that my conference speaking noticeably improved through my YouTubing, which is not something I expected to happen. But I guess agonizing over creating compelling educational material all year around helps creating other compelling educational material.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
The Philippines are probably the friendliest place on earth.
And the Philippines are probably the friendliest place on earth and incredible fun, especially on the less frequented islands.
uv: Making Local Python Workflows FAST and BORING in 2025 Said 6 Jul 2025
Python's packaging and project tooling got infinitely better and faster over 2024.
the good news is that over the run of 2024, Python's packaging and project tooling got infinitely better and faster.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Shipping Python applications in Docker containers quickly with safe, reproducible builds is a solved problem in 2025.
Because local workflows can be ergonomic and robust now. Yes, really, with Python. And shipping Python applications using Docker containers really fast with safe, reproducible builds is a solved problem in 2025.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Using Docker locally for development is a terrible experience compared with today's local tooling.
What I won't talk ever about is using Docker locally for development because it's such a terrible development experience compared to what's possible with local tooling nowadays.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
For many people uv has already lived up to its ambition of being the only Python packaging tool, and in some ways surpassed its role models.
It appeared pretty much exactly a year ago in February of 2024 and for many people it already has lived up to the ambition. In some ways it has even surpassed its role models.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
If you ship Python applications in Docker containers without special Conda features, uv is the only tool you need.
As for Astral's ambition, if you already ship Python applications in Docker containers and got your way doing that without some special Conda features it is the only tool you need.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Contextualized, earned opinions are more helpful than pseudo-objective content about tools the author has never really used.
Personally I find pseudo-objective or unbiased content where people talk in theoretical terms about things they've never used themselves in anger rather unhelpful and I prefer contextualized earned opinions.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Making a Python application a proper package narrows the states the project can be in and greatly simplifies import logic.
There is no shame in going adhoc. The current implementation of PyPI which is called warehouse uses that layout. But I'm gonna be a model Python citizen and show you how to do it properly because it tightens the envelope of possible states and shapes that my project can be in which simplifies import logic greatly.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Ad hoc project layouts are prevalent in Python because packaging tooling was a trash fire around 2010 and people avoided it.
But I honestly think that the prevalence of adhoc design in the Python ecosystem is just that Python's packaging tooling used to be a trash fire around 2010 – the formative years – and people did anything necessary to avoid interacting with it
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
In the age of uv it is time to reconsider ad hoc Python project layouts.
and are just doing whatever they're always done or whatever they see around the internet. I don't know I think in the age of UV it's time to reconsider.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
An unimportable src directory ensures tests only import installed package code, which catches a whole category of packaging bugs.
to make sure that when I run tests against the package the tests imports only pick up code that is part of the package and guaranteed to be installed and not imported accidentally because they're laying around. This catches a whole category of packaging and installation bugs
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
100% test coverage is the only correct test coverage.
Simple but it happens to give us 100% test coverage which happens to be the only correct test coverage.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Narrow, well-defined entry points across system boundaries make interactions easier to reason about and contain complexity better.
Boundaries between systems are extremely important to contain complexity. Entry points allow you to interact with such a system across boundaries in a controlled way. The narrower and better defined an entry point the easier it is to reason about the interactions with the system and the better the containment of the complexity.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Applications should have clear standardized entry points whose only job is to bridge between the real world and the application.
I'm not a fan of like randomly groping into packages. I like to have clear standardized entry points into my applications whose only job is to bridge between the dirty real world and my pristine application.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Entry-point modules are the one place where it is acceptable to omit code from coverage, provided they are kept free of loops and if statements.
And this is the only module where you have my blessing to add it to coverage's `omit` list. And to mitigate the risk this introduces I keep them as simple as possible with no loops or if statements
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
An application shipped to a server does not need a meaningful package version.
since this is an application that is eventually shipped to a server we don't care about package versions and we can set it to zero and never touch it again.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Dependency groups help package maintainers whose development extras otherwise leak into PyPI metadata.
Therefore this is great for package maintainers that are annoyed that it looks like our packages depend on pytest or sphinx because their development extras leak into PyPI.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Complaining to open source projects that changes broke your production shows you do not have your dependencies under control.
complaining on open source projects about changes breaking your production is very bad karma and shows that you don't have your dependencies under control?
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Unless told to do things in non-standard ways, uv leaves almost no room for user error.
And unless you've explicitly told uv to do things in non-standard ways, there's almost no room for error from your side. It's essentially foolproof, which is my favorite kind of proof.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
Naming pytest fixture functions with an underscore and setting their name explicitly avoids accidentally using the function object as the fixture.
I name my pytest fixture functions with an underscore and set their name explicitly to avoid the confusing error of forgetting to declare dependency in a test and accidentally using the function object as the fixture.
My 2025 uv-based Python Project Layout for Production Apps Said 24 Feb 2025
How a system deals with failure is what separates a robust system from one everybody mocks, and most failures are temporary.
So you see, the difference between a robust system that lets you sleep at night and a system that everybody mocks on social media is how you deal with failure. And fortunately, most of failures are temporary.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Indiscriminate retries can take down whole systems.
However, the lesser-known proverb is, if you indiscriminately try, try, try again, you can take down whole systems, your systems.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
At scale every system is flaky, and the more components it has, the flakier it gets.
At certain scale and under real-world conditions that we all live under, regardless of your level of denial, every system is flaky. And the more components it takes to do its job, aka how complex it is, the more things and the more connections between things can fail, which makes it flakier.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
A system not designed for reliability and failure will demand a lot of manual work instead of new development.
So if you don't design your systems for reliability, you won't get a robust system. Period. And because failure is inevitable, a system that is not built for failure will make you do a lot of manual work to keep things working instead of building cool new stuff.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Services retrying immediately after a shared failure can amount to a distributed denial of service attack against yourself.
So yeah, big picture. The danger is that you might run a distributed denial of service attack against yourself.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Because the cause of a failure is unknown, retries should start with a short backoff and increase it exponentially.
And of course, you don't know which of those reasons is at play. So you need to cater to all of them by starting with a short backoff and then exponentially increase every failed retry.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Retries must stop eventually because not everything recovers within a useful time frame.
But it also means that you have to stop trying eventually because not everything recovers within a time frame that makes sense for your operation.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Forgetting timeouts on remote calls is as dangerous as unbounded retries and can take down whole companies.
Forgetting to use timeouts on everything remote is the kissing cousin of unbounded retries. It can literally take down whole companies at once, blocking calls, start cascading until everything ends up in a standstill.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Retries need random jitter, because identical backoffs still make all clients retry at the same time.
But if all clients have the same backoff, they still retry at the same time, so they still take the target down just a little bit later. Which brings us to the final piece of a well-behaved retry. We add a random amount of time to each backoff to spread out the retries.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Retrying only at the edges works in simple systems, but in complex ones the edge is unclear and no server should know the whole topology.
One simple one is where you retry only at the edges. So only the first client is allowed to retry. But in sufficiently complex systems, it's unclear where the edge is. No server has complete knowledge of the topology around itself. And it shouldn't.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Tenacity's default retry is unbounded and has neither a backoff nor a jitter.
However, by default, this code will do everything wrong I've just explained to you. It's unbounded. So it will retry until the heat end of the universe or your system, whichever comes first, and has neither a backoff nor a jitter.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Tenacity is a wonderful package because it has all the knobs needed for great retries.
But I've always said Tenacity is wonderful. And it truly is. Because it has all the knobs you need to get really great retries.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Behaviour that is only implied by a function's defaults adds mental burden when reasoning about code.
If it's just implied by the defaults of a function, one has to know that it does the wrong thing by default, adding mental burden when trying to reason about the behavior of code.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Retrying on HTTP 500 errors is right, but retrying on 400-range errors, especially 401 and 403, will probably get you banned.
And while you should retry on a 500 error, retrying on errors in a 400 range, especially 401 and 403, is probably gonna get you banned rather sooner than later.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Retry parameters can be tuned as long as the backoff is exponential and has an upper bound.
And these parameters should be fine for most applications. But, of course, you can tune all numbers to your liking as long as it's exponential and has an upper bound.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Automated testing matters because you cannot trust yourself to write correct code or to not break it later.
I care a lot about automated testing because I don't trust myself to write correct code and if I did by accident, I don't trust myself to not break it in the future.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Retries should be logged even when they succeed, otherwise they look like unexplained performance regressions.
Firstly, of course, you want to know that something went wrong, even if it worked out eventually, because otherwise, regular retries look like weird performance regressions.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
structlog is the best Python logging package and the standard library's logging is the worst.
stamina comes with built-in support for the best Python logging package, structlog, with the best logo, thanks to Lynn Root, and falls back to the worst logging package, which is the standard library.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
A sudden rise in retries from one or more systems is a sign that something is off and should be investigated.
If one or more systems suddenly generate a lot of retries, that's a sign that something is off and you should investigate.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Chasing SEO and zeitgeist topics for a YouTube channel is something to emphatically avoid.
unless I listen to the siren's call of SEO and serve zeitgeist topics everyone is searching for, which is something I emphatically do not want to do.
Master Flaky Systems With Retries in Python 🐍 (avoid self-DDoS) Said 9 Dec 2024
Virtual environments do not measurably affect an application's runtime performance.
You can also disregard claims that virtual environments measurably affect your application's runtime performance.
Why I Still Use Python Virtual Environments in Docker Said 2 Sept 2024
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
Where they publish
Site hynek.me Writing on Python, software design and career growth.
Link verified 25 Sept 2026.
x.com @hynek Notes on Python and software engineering.
Recent
- For all your #Python retrying needs, here's stamina 26.2.0 & it's a big one: Native raise TryAgain with minimum backoff! RetryDetails filtering! Explicit block names for non-decorator retries! Lazy imports on Python 3.15! Bug fixes! Optimizations! Oh my! 15 Nov 2026 github.com
- Happy to announce bgt 26.3.0, the best way to reliably run background threads in #Python that comes with only one, but really cool change: easy async work units! 14 Nov 2026 github.com
- To rid myself of the new incomplete provenance red badge of shame on PyPI, here's argon2-cffi-bindings 26.2.0! As a bonus it comes with stable ABI drivers for free-threaded Python 3.15 and later. #Python 13 Nov 2026 github.com
Show 17 more
- looks like some PHP RCE (CVE-2026-109618 / CVE-2026-109619 / PHP-UP-2026) deets started to drop. as a LAMP shared webhoster we're obviously Very Excited™ 21 Oct 2026 jackalsyn.com
- Here's build-and-inspect-python-package 3.0.2 brought to you by certifi and the number 4: 21 Oct 2026 github.com
- It's possible to deliver quality code with genAI just like it's possible to be on a diet in a candy shop. 17 Oct 2026
- I feel this in my bones. My failure to produce/deliver contains multitudes, but this is the core of the issue. The audience and (more importantly) exchange for any type of content have all but collapsed. 1/2 11 Oct 2026 borretti.me
- In a mad dash before my first proper vacation this year, here's pgbg 26.2 with the non-Postgres parts ripped out and imported from bgt. Architecturally, I'm very happy with both and hope y'all try to play around with it! 6 Sept 2026 github.com
- Due to popular demand (it's me—I'm the demand), I've decided to cut pgbg in two and liberate the database-agnostic parts. So if you want a self-healing way to run a background thread in Python with flexible wakeups, check it out! 4 Sept 2026 bgt.hynek.me
- When I was advocating for nogil/free-threading, I always said that it’s important not to judge threads by the APIs we have, but by the APIs we will build once they’re worth the trouble. Here’s my first contribution: https://t.co/6V3ZsIHlbS 1/2 2 Sept 2026
- Happy/nervous to announce argon2-cffi-bindings, the low-level C binding wheels used by argon2-cffi. It's a big release w/ wheels for new platforms, but the biggest item is the liberation from setuptools w/ great help by Nathan & Henry! 🥳 #Python 20 Aug 2026 github.com
- Happy to announce v3.0.0 of my build-and-inspect-python-package GitHub Action that does what the name says. 1/4 30 Jul 2026
- To clean myself of my writing dry spell, here’s a TIL that probably should’ve been a blog post: TIL: SQLite WAL Mode Can Lock Short-Lived Readers 26 Jul 2026 hynek.me
- Good morning! Since it's become a drag to support in mainline, I've extracted svcs's Pyramid support into an own package svcs-pyramid. That means, the next svcs version will ship WITHOUT a `svcs.pyramid` module: 26 Jul 2026 github.com
- I’m somewhat embarrassed to finally announce svcs 26.1.0 – my solution to #Python service location and dependency injection. 13 Jul 2026 github.com
- WHOA, Pyrefly is adding proper attrs support in 1.2dev!!! 🤩 2 Jul 2026 pyrefly.org
- A quick shadow drop of sorts: who hasn't implemented a cache on top of Postgres? I know, everyone has. And yet, here's another contender that's based on psycopg and can use existing SQLAlchemy engines (or whatever you implement): ⚡️psycache ⚡️ 1/2 24 Jun 2026
- for no particular reason whatsoever, I've updated my guide on how to measure #Python coverage across GitHub Action containers without an external service (*cough* Codecov *cough*) 9 Jun 2026 hynek.me
- I'm very relieved to finally announce structlog 26.1.0! Given how long this release took, it's pretty thicc with nice things all over the board! Apologies for the long release cycle; it's been a victim of the slopocalypse and me trying to navigate my way thru the new normal. 1/2 6 Jun 2026
- the biggest damage by the slopocalipse is that we’re forgetting how shit most humans are at writing code 5 Jun 2026
Link verified 25 Sept 2026. Recent items update automatically from the channel.
Bluesky hynek.me Notes on Python and software engineering.
Recent
- i'm sure someone already made that joke but looking at my brokerage account: did everyone sell all their shares just to buy anthropic?? 20 Nov 2026
- For all your #Python retrying needs, here's stamina 26.2.0 & it's a big one: Native raise TryAgain with minimum backoff! RetryDetails filtering! Explicit block names for non-decorator retries! Lazy imports on Python 3.15! Bug fixes! Optimizations! Oh my! 15 Nov 2026 github.com
- i want the time and youth back i lost to the only non-CVE soupsieve version having a >=3.11.5 pin 14 Nov 2026
Show 17 more
- weee somehow I missed that Nox now has a parallel mode like tox and it takes stamina's full test suite from over 30s to under 5s! 🤩 14 Nov 2026 github.com
- Happy to announce bgt 26.3.0, the best way to reliably run background threads in #Python that comes with only one, but really cool change: easy async work units! 14 Nov 2026 github.com
- To rid myself of the new incomplete provenance red badge of shame on PyPI, here's argon2-cffi-bindings 26.2.0! As a bonus it comes with stable ABI drivers for free-threaded Python 3.15 and later. #Python 13 Nov 2026 github.com
- is literally anything gonna get any better now pls 4 Nov 2026
- so openat()/openat2() have been fucked on Rosetta for a while… what are the odds Apple fixes it given they want to drop it next year? 😑 28 Oct 2026
- Whenever someone says software design doesn’t matter I’ll link them to the PHP RCE patches now. 22 Oct 2026
- looks like some PHP RCE (CVE-2026-109618 / CVE-2026-109619 / PHP-UP-2026) deets started to drop. as a LAMP shared webhoster we're obviously Very Excited™ 21 Oct 2026 jackalsyn.com
- Here's build-and-inspect-python-package 3.0.2 brought to you by certifi and the number 4: 21 Oct 2026 github.com
- As I walked thru a pitch-black park watching people walking their dogs with torches and passing kids going to school illuminated only by their smart phones, I once again realized how much wintertime abolitionists can go pound sand. #oneMoreWeek 19 Oct 2026
- It's possible to deliver quality code with genAI just like it's possible to be on a diet in a candy shop. 17 Oct 2026
- ohhhhh 17 Oct 2026 team17.com
- I feel this in my bones. My failure to produce/deliver contains multitudes, but this is the core of the issue. The audience and (more importantly) exchange for any type of content have all but collapsed. 11 Oct 2026 borretti.me
- a good day to advertise kapeli.com/dash ;) #hugOps (I noticed because my monthly update builds failed due to intersphinx 😬) 1 Oct 2026
- Traveling keeps reminding me of how much work it is to: a) deal with impromptu to-do items (usually via email) b) keep everything charged Somehow we’re serfs to email and chargers, and nobody is setting shit on fire. 26 Sept 2026
- I was not joking folks 25 Sept 2026 negroniweek.com
- Happy Negroni week to everyone who celebrates! 25 Sept 2026
- *takes a glance at my GitHub inbox* I’m gonna block so many accounts once I’m back. 16 Sept 2026
Link verified 25 Sept 2026. Recent items update automatically from the channel.
YouTube Hynek Schlawack Python screencasts: uv, project layout, testing.
Recent
Link verified 8 Nov 2026. Recent items update automatically from the channel.
GitHub hynek attrs, structlog and other Python libraries.
Recent
- stamina — Production-grade retries for Python 15 Nov 2026
- pgbg — PostgreSQL-orchestrated background threads for Python 15 Nov 2026
- bgt — Fault-tolerant background threads for Python 15 Nov 2026
Show 13 more
- svcs — A Flexible Service Locator for Python. 13 Nov 2026
- doc2dash — Create docsets for Dash.app-compatible API browsers. 13 Nov 2026
- argon2-cffi — Secure Password Hashes for Python 13 Nov 2026
- argon2-cffi-bindings — Low-level Python CFFI Bindings for Argon2 13 Nov 2026
- prometheus-async — Async Python helpers for the official prometheus-client. 2 Nov 2026
- environ-config — Python Application Configuration With Environment Variables 2 Nov 2026
- structlog — Simple, powerful, and fast logging for Python. 2 Nov 2026
- pem — PEM file parsing in Python. 2 Nov 2026
- hatch-fancy-pypi-readme — Fancy PyPI READMEs with Hatch 2 Nov 2026
- svcs-pyramid — Pyramid integration for the svcs Python service locator 2 Nov 2026
- setup-cached-uv — Use uv in GitHub Actions by adding one line to the workflow. 1 Nov 2026
- build-and-inspect-python-package — Build and Inspect Python Packages in GitHub Actions 1 Nov 2026
- psycache — A psycopg-Backed PostgreSQL Cache 29 Sept 2026
Link verified 25 Sept 2026. Recent items update automatically from the channel.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.