Make a release for legacy python versions #50
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.
Hi Oz,
since the merge of PR #49 the tests are broken, because
pytests>=5. 0.0
dropped support for legacy python versions (namely in this casepy27
andpy34
).This PR will pass the tests and should be the release candidate for a minor version (i.e.
0. 6.0
), so please bump the version after the merge.To get up to date again, I will make a PR that drops all legacy code and make a note for users to use this release if they need support for older python versions.
P.S.: If you also stopped using py27 we could also upgrade
bumpversion
tobump2version
, which is a fork ofbumpversion
which is still maintained and supports python 2+3.