[53.0.0_maintenance] Workaround py03 doc failure#6941
Merged
andygrove merged 1 commit intoapache:53.0.0_maintenancefrom Jan 4, 2025
Merged
[53.0.0_maintenance] Workaround py03 doc failure#6941andygrove merged 1 commit intoapache:53.0.0_maintenancefrom
andygrove merged 1 commit intoapache:53.0.0_maintenancefrom
Conversation
andygrove
approved these changes
Jan 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
Docs are failing with newer versions of rust on maintenance_53.0.0
Apparently it is a known issue with py03:
create_exceptionmacro triggersunexpected_cfgslint in nightly build PyO3/pyo3#4743@psvri fixed this on main by upgrading to py03 0.23 in
Are there any user-facing changes?
No, this is designed to get CI passing on the maintenance_53.0.0 branch