version.text replaces pretty_version #549
Merged
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.
Companion to python-poetry/poetry#7305
Downstream tests should fail until python-poetry/poetry#7305 propagates
I suppose the
Package
could instead continue to accept the pretty_version in its constructor but just ignore it: while that would be backwards-compatible it would also be rather misleading.I don't think it's worth it myself - but if you really wanted to go through the deprecation cycle I suppose we could check for not-None pretty_version and warn