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

Test against Python 3.9 #1680

Merged
merged 1 commit into from
Oct 19, 2020
Merged

Test against Python 3.9 #1680

merged 1 commit into from
Oct 19, 2020

Conversation

sloria
Copy link
Member

@sloria sloria commented Oct 19, 2020

No description provided.

@sloria sloria merged commit f37da1a into dev Oct 19, 2020
@sloria sloria deleted the test-py39 branch October 19, 2020 03:24
@lafrech
Copy link
Member

lafrech commented Oct 19, 2020

Wondering if it is worth testing on all those versions or if we could just test on min and max (3.5 and 3.9). To shorten execution time and limit CPU waste.

@sloria
Copy link
Member Author

sloria commented Oct 19, 2020

I have no strong opinion on it. FWIW, the execution time wouldn't be affected much since we get 10 parallel builds with AP.

@lafrech
Copy link
Member

lafrech commented Oct 19, 2020

FWIW, the execution time wouldn't be affected much since we get 10 parallel builds with AP.

Fair enough.

CPU waste point still stands. I can't think of an issue what would appear in 3.7 then disappear in 3.8 for instance, so I don't think those tests are useful. But maybe the waste is peanuts and not worth considering.

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 this pull request may close these issues.

None yet

2 participants