messense

> do you see any concerns with adding this to `maturin`? No concern, I think a `generate-stubs` command will be very useful for users wanting to commit `pyi` files in...

> @messense, when might you plan to do the next `maturin` release? I'll release a new version after fixing https://github.com/PyO3/maturin/issues/1804 this week.

maturin 1.3.1 is out with the GraalPy wheel filename fix.

IMO it's not a big issue for `maturin`, we can detect `pyo3` version and change the `abi3` detection logic to * `unstable-python-api`/`unlimited-api` features means non-abi3 * otherwise it's abi3 It...

> what about a feature called `no-abi3` I feel that `no-abi3` seems to imply that it's opt-out of some feature rather than opt-in to version specific feature, given that features...

Not implemented yet.

Sorry, it's unlikely there will be updates since rocketmq clients development has moved to https://github.com/apache/rocketmq-clients.

I've also encountered this issue, turns out the range request was modified by [ProxySG](https://www.broadcom.com/products/cybersecurity/network/web-protection/proxy-sg-and-advanced-secure-gateway) that turns it into a non-range request, thus `smart_open` chokes on its response. I've also tried...

See https://github.com/ziglang/zig/pull/11906, consider open a PR to filter it out like https://github.com/rust-cross/cargo-zigbuild/pull/97.

So the flag is added by `cargo-auditable`, simply remove it might have other unintended effects? https://github.com/rust-secure-code/cargo-auditable/blob/da85607fb1a09435d77288ccf05a92b2e8ec3f71/cargo-auditable/src/rustc_wrapper.rs#L56