Alex Gaynor

A pretty typical use case for releasing the GIL is to process a `&[u8]` that was extracted from a `&PyBytes`. `&PyBytes` are immutable so it's sound, as long as someone...

Quite bad :-( It's still something like 1/4 of all of our downloads. From the metrics, a huge portion of the downloads comes from Amazon Linux 2.

Hmmm, ok. Sub-interpreters feels like a very deep mess.

What would the equivalent of `borrow()`, `try_borrow()`, etc. be with this approach?

Ah. Well then, I'd never noticed that. Sorry for the noise!

What's the use case for `PyAny::get_refcnt`? Perhaps it should be deprecated in favor of methods with narrower semantics.

One note: it'd be useful if pyo3 still supported specifying the abi3 minimum version if it differs from the current python. For cryptography on Windows and macOS we build abi-py36...

As the OP indicates here, passlib will work with latest bcrypt, it simply emits a warning. You should be able to silence that warning with a logging configuration.

I'm one of the maintainers of pyca/cryptography, a popular Python package (top 20 downloads from PyPI most days) with a risk component. I can provide some limited stats on versions...

Sure -- though I'm not sure we've had a finding so far (yay memory safe languages). https://github.com/alex/rust-asn1/tree/main/.github/workflows is where the workflows are.