Successfully tracked down the Hyrum's Law one, nice work

> downstream developers will learn to depend on every possible behavior your API accomplishes, even the unintended ones

https://xkcd.com/1172/

+1 for Mise, it has just totally solved the 1..N problem for us and made it hilariously easy to be more consistent across local dev and workflows

some discussion in https://news.ycombinator.com/item?id=44303052, which seems to have been posted first

some discussion in https://news.ycombinator.com/item?id=44303052, which seems to have been posted first

Their status page has updated w/ a GitHub Copilot degraded perf warning. Seems like they're at least aware of it

Yep. Some of it's working fine, but various file downloads are giving 500/503

Say what you want, Astral ships impressively fast and their stuff works well. Python has been looking for better tooling for a long time.

I’ve had this same thought. Ruff doesn’t support extensions / custom lint rules that I’m aware of, so maybe don’t get your hopes up.

Not supporting plugins for a type checker to me is a plus. It’s quite frustrating that some Python projects only typecheck if you have plugins. That is a major source of frustration.

python packages that do a lot of metaprot can only be properly type checked if you replicate that metaprogramming at the type level. e.g. if dataclasses were not part of the standard library they would need a plug-in to be handled correctly.

I mean that kind of code exists; things like attrs are too magical otherwise

AWS supports Valkey for Elasticache, and they actually bill it 33% cheaper. We use it and it works well.

Yes, this is it. You can usually find some discounted or free way to get most books, but I had classes where you literally submitted homework through the same system you accessed the book through, and it was like $150.