andenacitelli

+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

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.

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.

They yanked the relevant change and pushed a new one with a revert, this is now resolved

Took them seemingly forever to do. The reversion, sure, that might take a bit to proof, but the yank should have been done way sooner

From what I gather this has basically derailed CI for the morning for the majority of places out there. Only workaround is pinning build-time dependencies, which only pip and uv seem to let you do well. Poetry is SOL / heavily cache-dependent as to whether it works.

A full rewrite instead of finding a way to gradually increment already feels like a lot of risk. Asking your core dev team to potentially pick up an entirely new skillset in Rust would introduce too much on top and probably cause people to flake from the project.

Totally agree something like Rust would be good in a vacuum, but existing contributors and ecosystem would present problems. Having tooling built in the same ecosystem as the end product makes it way easier to contribute.