Fix/issue 69 #70
Closed
Fix/issue 69 #70
Conversation
This file contains 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
|
@oschwald Do you have any opinion on the versioning related "question"? |
|
Thanks! I merged from the CLI and released 2.0.1. I yanked 2.0.0. |
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.
Description
The current version, which is stated to be Python 3 only, actually gets into Python 2 installations because of a missing python_requires update
This PR closes #69.
Note
Also bumped the history and version number to help you prepare the new release. Of course, Yanking 2.0.0 would be needed to completely fix the issue, or I could update the PR to use a post version.