Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

py3-breezy - multi-version #30837

Merged
merged 1 commit into from
Oct 16, 2024
Merged

py3-breezy - multi-version #30837

merged 1 commit into from
Oct 16, 2024

Conversation

smoser
Copy link
Member

@smoser smoser commented Oct 15, 2024

3.13 fails like this:

>  error: the configured Python interpreter version (3.13) is newer than
>  PyO3's maximum supported version (3.12)
>  = help: please check if an updated version of PyO3 is available.
>     Current version: 0.21.1
>  = help: set PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress this check
>     and build anyway using the stable ABI
>  error: `cargo rustc --lib --message-format=json-render-diagnostics
>    --manifest-path lib-rio/Cargo.toml --release -v
>    --features pyo3/extension-module --crate-type cdylib --

We can enable later.

@smoser smoser force-pushed the fix/pymv-breezy branch 2 times, most recently from d8dde1d to 50840f3 Compare October 15, 2024 15:56
3.13 fails like this:

>  error: the configured Python interpreter version (3.13) is newer than
>  PyO3's maximum supported version (3.12)
>  = help: please check if an updated version of PyO3 is available.
>     Current version: 0.21.1
>  = help: set PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress this check
>     and build anyway using the stable ABI
>  error: `cargo rustc --lib --message-format=json-render-diagnostics
>    --manifest-path lib-rio/Cargo.toml --release -v
>    --features pyo3/extension-module --crate-type cdylib --

We can enable later.
@smoser smoser force-pushed the fix/pymv-breezy branch 3 times, most recently from 0bb9925 to 7d80bdd Compare October 15, 2024 18:35
@smoser smoser enabled auto-merge (squash) October 15, 2024 18:43
@smoser smoser merged commit 24ee509 into wolfi-dev:main Oct 16, 2024
14 of 17 checks passed
@xnox
Copy link
Member

xnox commented Oct 16, 2024

@jelmer is this something we can fix in PyO3? cause typically in wolfi we ship everything on release day, and it's been like 9 days and we still don't have python3.13 for everything.

@jelmer
Copy link

jelmer commented Oct 16, 2024

@xnox the fix for this is pretty trivial and can be found here: https://code.launchpad.net/~jelmer/brz/bump-pyo3/+merge/474976

Unfortunately I'm still rebuilding our CI so have not yet been able to land that PR.

@jelmer
Copy link

jelmer commented Oct 20, 2024

3.3.9 is now out with newer pyo3

@smoser
Copy link
Member Author

smoser commented Oct 21, 2024

3.3.9 is now out with newer pyo3

octo-sts saw that and authored #31272 . I'll dig into what is broken and fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants