Determine the minimum required versions of dependencies from package metadata for docs #3380
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.
Description of proposed changes
It's possible to determine the minimum required versions from the package metadata using codes like below. So that we don't have to update the
doc/minversions.md
file everytime we bump the minimum required versions (e.g., #3372).This PR uses the same codes to determine the minimum required versions and store in the
requirements
dictionary, which can be used in the documentation using syntax like{{ requires.python }}
.Preview: