Drop support for Python 3.6 and 3.7 #329
Comments
|
Drop 3.7, too?
…On Sun, Feb 5, 2023, 08:13 Ben Mares ***@***.***> wrote:
Checklist
- I added a descriptive title
- I searched open requests and couldn't find a duplicate
What is the idea?
Ease development through use of modern Python
Why is this needed?
Working with type annotations becomes much easier when I can use from
__future__ import annotations
What should happen?
Bump minimal Python version to 3.7
Additional Context
Any thoughts, @bollwyvl <https://github.com/bollwyvl>?
—
Reply to this email directly, view it on GitHub
<#329>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALCRCGQT5APYKL7GPOIVDWV6YSHANCNFSM6AAAAAAURZPZVY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I didn't want to be too radical, but yes! 😄 |
maresb
changed the title
maresb
added a commit
to maresb/conda-lock
that referenced
this issue
Feb 5, 2023
maresb
added a commit
to maresb/conda-lock
that referenced
this issue
Feb 5, 2023
maresb
added a commit
that referenced
this issue
Feb 6, 2023
Drop support for Python 3.6 and 3.7 Closes #329 Co-authored-by: Srinivas Lade <srinulade1@gmail.com> Co-authored-by: Daniel Bast <2790401+dbast@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
What is the idea?
Ease development through use of modern Python
Why is this needed?
Working with type annotations becomes much easier when I can use
from __future__ import annotationsWhat should happen?
Bump minimal Python version to 3.7
Additional Context
Any thoughts, @bollwyvl?
The text was updated successfully, but these errors were encountered: