-
|
I don't suppose this is exposed in any metadata besides this error message is there? If this is exposed somewhere else then please let me know what I've overlooked instead, thanks :-) |
Beta Was this translation helpful? Give feedback.
Answered by
lmmx
Oct 24, 2025
Replies: 1 comment
-
|
aha, I was thinking along env var lines this is much easier: Lines 52 to 54 in 1a3e53f hmmm So I can get at this automatically via PYO3_FFI_VERSION=$(cargo tree -i pyo3-ffi --edges no-dev,no-build,no-proc-macro --prefix none | head -n1 | cut -d " " -f 2 | sed 's/^v//')or for situations without cargo // otherwise avoiding it (like possibly in CI before building it) PYO3_FFI_VERSION=$(grep -m 1 -A 1 'name = "pyo3-ffi"' Cargo.lock | tail -n1 | cut -d '"' -f 2)then use it to get the version curl -sL "https://static.crates.io/crates/pyo3-ffi/pyo3-ffi-$PYO3_FFI_VERSION.crate" \
| tar -xzO "pyo3-ffi-$PYO3_FFI_VERSION/Cargo.toml" \
| uvx --from=toml-cli toml get --toml-path=/dev/stdin package.metadata.cpython.max-version \
| tr -d '"'
3.14 |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
lmmx
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
aha, I was thinking along env var lines this is much easier:
pyo3/pyo3-ffi/Cargo.toml
Lines 52 to 54 in 1a3e53f
hmmm
So I can get at this automatically via
PYO3_FFI_VERSION=$(cargo tree -i pyo3-ffi --edges no-dev,no-build,no-proc-macro --prefix none | head -n1 | cut -d " " -f 2 | sed 's/^v//')or for situations without cargo // otherwise avoiding it (like possibly in CI before building it)
PYO3_FFI_VERSION=$(grep -m 1 -A 1 'name = "pyo3-ffi"' Cargo…