Skip to content

Conversation

@marcharper
Copy link
Member

No description provided.

@drvinceknight
Copy link
Member

I suspect we've already discussed this and I'm just forgetting but is there a reason why we cannot add 3.7 and keep 3.5?

@marcharper
Copy link
Member Author

No reason, just matching with Travis. We "officially" support the two latest released of Python but I don't see any problem leaving 3.5 in.

@meatballs
Copy link
Member

I can't remember precisely what they were, but there were some things we wanted to do that were only supported in 3.6+ and we decided to leave them until 3.7 came along and we could drop 3.5

@drvinceknight
Copy link
Member

Let's go ahead and merge, if something comes up that needs us to bring 3.5 back in then we can always do that.

@drvinceknight drvinceknight merged commit 9d5a0f9 into master Sep 4, 2019
@marcharper marcharper deleted the marcharper-patch-1 branch September 5, 2019 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants