Alex Gaynor

It's possible to go into CI and manually download a wheel if you want, but they're not published anywhere, no. On Tue, Aug 5, 2025 at 5:47 AM Gleb Khmyznikov...

I decided returning both made more sense than trying to just mirror the stdlib's API, because of the extreme risk existing code wouldn't notice the behavior change unless types also...

the CI failures appear to be the ones fixed by #1196. I can rebase after that merges.

While I think reproducible builds are generally good, our builds are just invoking upstream tools: ``` - name: Build the wheel run: | if [ -n "${{ matrix.PYTHON.ABI_VERSION }}" ];...

I'm pretty ambivalent-to-negative on replacing `actions/checkout` with raw `git` commands. Particularly for doing sparse checkouts, its' considerably simpler. What complex build logic are you talking about? The wheel-builder is more...

The wheel builder ought to be trivial, I'm not sure I see a need for anything more than a bash script (which, after all, is what the yaml is really...

The linux jobs are already running in docker containers, there should be no need to nest docker containers further. The sum total of the sdist building is `uv build --build-constraint=$BUILD_REQUIREMENTS_PATH...

Given the lack of progress here, and the fact that if/when uv and auditwheel produce deterministic wheels we will automatically take advantage, I'm going to wontfix thing.

Previously discussed in https://github.com/pyca/cryptography/issues/6573 -- given other implementations have similar limitations, I'm disinclined towards supporting these.

After discussing with @reaperhulk, we'd be willing to take a PR (which would go to rust-asn1 in the first instance) which added support for 128-bit OID arcs.