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

Port to Sphinx 8.0 #1047

Merged
merged 1 commit into from
Dec 18, 2024
Merged

Port to Sphinx 8.0 #1047

merged 1 commit into from
Dec 18, 2024

Conversation

cjwatson
Copy link
Contributor

What do these changes do?

The old intersphinx_mapping format has been removed; it must now map identifiers to (target, inventory) tuples.

Are there changes in behavior for the user?

No.

Checklist

  • I think the code is well written
  • [N/A] Unit tests for the changes exist
  • Documentation reflects the changes

The old `intersphinx_mapping` format has been removed; it must now map
identifiers to (target, inventory) tuples.
@Dreamsorcerer Dreamsorcerer merged commit d8fc8de into aio-libs:master Dec 18, 2024
11 checks passed
Copy link

codecov bot commented Dec 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (8c30c82) to head (08fc388).
Report is 11 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #1047   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           19        19           
  Lines         1472      1472           
  Branches        25        25           
=========================================
  Hits          1472      1472           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@asvetlov
Copy link
Member

Should we back port it to 3.12?

@cjwatson cjwatson deleted the sphinx-8.0 branch December 18, 2024 19:59
@cjwatson
Copy link
Contributor Author

I don't think I really have an opinion - I've just been going round patching a big pile of Debian packages that are affected by this and sending things upstream where appropriate. If you're actively supporting your 3.12 branch then it would probably make sense so that people can keep on using it with current Sphinx, and it should be pretty harmless.

@Dreamsorcerer
Copy link
Member

Should we back port it to 3.12?

I think you're looking at the wrong repo..

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