Repository navigation
docs: note Python 3.12+ requirement on pip install page - #1236
Merged
Merged
Conversation
pip install was silently rolling back to old releases on Python 3.9/3.10/3.11. Pre-2026.4.5.3 releases will be yanked from PyPI; this updates the install docs with a top-of-page Python 3.12+ note and a bottom "Legacy Python versions" section explaining how to install pre-2026.4.5.3 versions explicitly via `pip install autofit==<version>` if needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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.
Summary
Adds a Python 3.12+ requirement note to the top of the pip install page,
plus a "Legacy Python versions" section at the bottom explaining how to
install pre-
2026.4.5.3releases ofautofitvia explicit version pin.Context: users on Python 3.9/3.10/3.11 currently see
pip install autofitsilently roll back to a pre-
2026.4.5.3release (which doesn't carry therequires-python>=3.12pin). They then download the latest workspace,which is paired with the current
PyAutoFitversion, and hit unrelated-lookingimport errors.
This PR is paired with a follow-up PyPI yank of all releases of
autofitprior to
2026.4.5.3. Yanked releases remain installable via explicit==pin (so existing lockfiles keep working), but pip will no longerfall back to them. Users on unsupported Python will instead get a clear
"no matching distribution" error pointing them at the version requirement.
API Changes
None — docs-only change.
Test Plan
make htmlbuilds the modifieddocs/installation/pip.rstwithoutwarnings.
"Legacy Python versions" section.
🤖 Generated with Claude Code