Skip to content
This repository was archived by the owner on Aug 1, 2024. It is now read-only.

Conversation

@timmc-edx
Copy link
Contributor

No description provided.

@timmc-edx
Copy link
Contributor Author

I'm not totally sure if downgrading Python from 3.6 to 3.5 is correct, since this isn't deployed per se, but it would put it in line with our other repos.

@robrap
Copy link
Contributor

robrap commented Mar 11, 2020

@timmc-edx: I'd have the same question about Python 3.5 vs 3.6. It would be great if we could have a documented decision around this for people to refer to.

Copy link
Contributor

@jmbowman jmbowman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Switching to 3.5 for consistency seems like a good idea. We're likely to go to 3.8 next rather than 3.6 anyway, so not sure we gain much from 3.6 testing.

@timmc-edx timmc-edx merged commit 5f4339f into master Mar 11, 2020
@timmc-edx timmc-edx deleted the timmc/fix-upgrade branch March 11, 2020 18:16
@thraxil thraxil mentioned this pull request Jan 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

4 participants