docs: pin install to published Community release 2.0.1 - #11
Open
wolfiesch wants to merge 1 commit into
Open
Conversation
Signed-off-by: Wolfgang Schoenberger <221313372+wolfiesch@users.noreply.github.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
1 participant
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
wolfxl==2.0.1) instead of the unreleased 2.0.2.Context: PyPI currently serves 2.0.1; the previous pin made the first README command fail with
No matching distribution foundfor anyone following the docs. Dated benchmark citations of the 2.0.1 wheel are intentionally unchanged.Follow-up: the PyPI project-page long description still renders the description baked into the 2.0.1 artifacts; refreshing it requires publishing the next release.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.