Failing test cases for requirements range expressions and prereleases #350
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.
Here is an oddity, continued from #349:
Prereleases are included in
>=
,<
requirement ranges, even when they don't have prerelease segments. But anyone specifying for example< 1.5.0
is most certainly not expecting to use 1.5.0.beta.0 if they happen to have it installed.Failed test output:
Also, a command line example:
Is this all expected behavior?