Skip to content

Python 3.7 #517

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

Merged
merged 2 commits into from
Oct 7, 2021
Merged

Python 3.7 #517

merged 2 commits into from
Oct 7, 2021

Conversation

nschloe
Copy link
Owner

@nschloe nschloe commented Oct 7, 2021

Fixes #516.

@klieret
Copy link

klieret commented Oct 7, 2021

You're fast, wow :D

@nschloe nschloe merged commit 51df162 into main Oct 7, 2021
@nschloe nschloe deleted the python3.7 branch October 7, 2021 11:35
@nschloe
Copy link
Owner Author

nschloe commented Oct 7, 2021

This doesn't really fix the problem for 3.6 users as 0.9.13 is "out there" now, but I'm assuming everyone will switch to 3.7 when 3.6 reaches EOL anyway (this December).

@klieret
Copy link

klieret commented Oct 7, 2021

I think you should yank 0.9.13 from pypy. Then people on py 3.6 will automatically fall back to 0.9.12 since 0.9.14 then has the new requirement.

And yes, 3.6 is old :)

@nschloe
Copy link
Owner Author

nschloe commented Oct 7, 2021

I think you should yank 0.9.13 from pypy.

Good idea, done that.

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.

future feature annotations is not defined
2 participants