Skip to content

CI: use py37 by default? #4370

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.

Sign up for GitHub

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

Jump to bottom
Closed
blueyed opened this issue Nov 11, 2018 · 0 comments
Closed

CI: use py37 by default? #4370

blueyed opened this issue Nov 11, 2018 · 0 comments
Labels
type: enhancement new feature or API change, should be merged into features branch type: infrastructure improvement to development/releases/CI structure

Comments

@blueyed
Copy link
Contributor

blueyed commented Nov 11, 2018

We should use py37 by default instead of py36.

After #4368.

Involves also changing tox.ini then.
@blueyed blueyed added type: enhancement new feature or API change, should be merged into features branch type: infrastructure improvement to development/releases/CI structure labels Nov 11, 2018
blueyed added a commit to blueyed/pytest that referenced this issue Nov 11, 2018
@blueyed
CI: use py37 instead of py36 by default
cf222eb 
Closes pytest-dev#4370.
@blueyed blueyed mentioned this issue Nov 11, 2018
Merged
blueyed added a commit to blueyed/pytest that referenced this issue Nov 12, 2018
@blueyed
CI: use py37 instead of py36 by default
5d20bdf 
Closes pytest-dev#4370.
blueyed added a commit to blueyed/pytest that referenced this issue Nov 12, 2018
@blueyed
CI: use py37 instead of py36 by default
935b106 
Closes pytest-dev#4370.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement new feature or API change, should be merged into features branch type: infrastructure improvement to development/releases/CI structure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blueyed