A5rocks
We use `uv pip compile` now, `uv pip install` isn't used yet but I don't think that needs to be tracked in this issue.
Could you provide a minimal reproducer program that has this problem (even if not frequently or under high load?)
Gah sorry I forgot about this; unfortunately I don't really have the motivation right now to figure out the right context to call the function. Uh, do you have logs...
Personally I like having a customized version of README for pypi even if it has caused issues due be being out of sync in the past. (people seeing trio in...
-snip- huh I can't find an archived page to support my memory so I was probably just misremembering. But I do think I agree that they aren't looked at much...
> > Some of your changes remind me that we should probably run shellcheck over our scripts... > > Problem is, it's written in haskell and the pre-commit integration for...
I think the 3rd is the best solution. Just a `gh pr view` on push and if there's a PR then don't run the next steps. Maybe a `if:` in...
`uv` seems to support keeping keeping things like `implementation_name` now: https://github.com/astral-sh/uv/pull/4503 I think once this uses that flag, this is good for me
I'm surprised pulling in `master` didn't work. I manually edited the test requirements to use a pre-release of cffi (IIRC? Or maybe cryptography) to fix that.
Tbh I think we should wait for 3.13 betas -> cffi release -> cryptography, for both the faster feedback cycle from CI and more guarantee that nothing will change