Fix docs build: pin setuptools<81 so pkg_resources remains available#260
Merged
Conversation
Contributor
|
Documentation available at: |
jlstpaul
approved these changes
May 11, 2026
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.
Pull Request
Follow-up to #258. Adding
setuptoolstodocs/requirements.txtwas not enough to unblock the docs build on Python 3.14: pip resolvedsetuptoolsto version 82.0.1, which no longer bundles thepkg_resourcesmodule. Sincemike<2.0(still pinned in this repo) importspkg_resourceson startup, the build continues to fail withModuleNotFoundError: No module named 'pkg_resources'.Pinning
setuptools<81keeps the install on a setuptools release line that still shipspkg_resources, which is the smallest change that unblocks the existingmike<2.0pin. A larger follow-up could upgrademiketo a 2.x release that no longer depends onpkg_resources, but that is out of scope here.This is not a spec change, so the spec-change checklist does not apply.
By contributing to this project, all contributors certify to the Developer Certificate of Origin in CONTRIBUTING.md.