Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python 3.8 has been released, so Travis should test against it instead of 3.7 #336

Closed
smithfarm opened this issue Aug 24, 2020 · 1 comment · Fixed by #338
Closed

Python 3.8 has been released, so Travis should test against it instead of 3.7 #336

smithfarm opened this issue Aug 24, 2020 · 1 comment · Fixed by #338

Comments

@smithfarm
Copy link
Contributor

Travis is currently configured to run unit tests in two environments: Python 3.6 and 3.7.

But now that Python 3.8 is out, we should change 3.7 to 3.8.

smithfarm added a commit to smithfarm/ceph-salt that referenced this issue Aug 24, 2020
And for local testing we can get away with 3.6 only. (It's convenient to
be able to run "tox" and not get all tests repeated in 3.8 after they
all ran once in 3.6.)

Fixes: ceph#336
Signed-off-by: Nathan Cutler <ncutler@suse.com>
@ricardoasmarques
Copy link
Contributor

Relates to #148

smithfarm added a commit to smithfarm/ceph-salt that referenced this issue Aug 25, 2020
And for local testing we can get away with 3.6 only. (It's convenient to
be able to run "tox" and not get all tests repeated in 3.8 after they
all ran once in 3.6.)

Fixes: ceph#336
Signed-off-by: Nathan Cutler <ncutler@suse.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants