Zanie Blue comments

Results 2921 comments of


                                            Zanie Blue

Non-deterministic 403 errors using private pypi server with `uv pip install -r requirements.txt`

Wow, thanks for digging! I really appreciate it.

Non-deterministic 403 errors using private pypi server with `uv pip install -r requirements.txt`

cc @seanmonstar (might be interesting to you)

Non-deterministic 403 errors using private pypi server with `uv pip install -r requirements.txt`

> Just poking in briefly: reqwest doesn't do any caching of responses at all. What you see is what the server sent. Thanks! So, it sounds like, server-side, there's non-deterministic...

Non-deterministic 403 errors using private pypi server with `uv pip install -r requirements.txt`

Wow.. haha Well, if that's the case, I'm glad it's working again!

Bump libX11 from 1.6.12 -> 1.8.10

Failed with ``` 2024-10-14T21:10:56.0604744Z libX11> + pushd libX11-1.8.10 2024-10-14T21:10:56.0605428Z libX11> ~/libX11-1.8.10 ~ 2024-10-14T21:10:56.0605825Z libX11> + patch -p1 2024-10-14T21:10:56.0632934Z libX11> patching file configure 2024-10-14T21:10:56.0652430Z libX11> Hunk #1 FAILED at 19557. 2024-10-14T21:10:56.0662242Z...

Consider inline script metadadata (PEP723) for benchmark scripts.

As a note, `pipx` supports this metadata declaration too so it seems pretty reasonable to use.

Add build attestations. Closes #343

Thank you! Should we only be attesting the artifacts on `main`?

Revert "Removed leading $ from cli code blocks"

We did https://github.com/astral-sh/uv/pull/5397 to solve the copy/paste problem over in uv.

Allow to access a `Range`'s segments

Yeah this is a bit of a rough edge. Thank you for sharing your use-case! You may find the the [uv report implementation](https://github.com/astral-sh/uv/blob/2c6d3537118adf6d5d8f65610740e636c1d3e15c/crates/uv-resolver/src/pubgrub/report.rs) interesting and helpful — we have customized...

Allow to access a `Range`'s segments

> I'll have a look at it for sure, thank you!! Be warned it's quite complicated. Happy to help though. > ... but it doesn't look like pubgrub::range::Range is implementing...