Skip to content
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

Investigate alernative implementation for <3.11 #42

Open
alexmojaki opened this issue Aug 10, 2022 · 2 comments
Open

Investigate alernative implementation for <3.11 #42

alexmojaki opened this issue Aug 10, 2022 · 2 comments
Assignees

Comments

@alexmojaki
Copy link
Owner

Look into the implementation described in #31 (comment)

@15r10nk 15r10nk mentioned this issue Sep 27, 2022
@15r10nk
Copy link
Collaborator

15r10nk commented Sep 27, 2022

What is the required minimum python version for this implementation.

Is 2.7 support still required?

What is with 3.4, 3.5 and 3.6?
3.6 has out of support since 6 month.

@alexmojaki
Copy link
Owner Author

There's no requirements at all since this is an enhancement. Supporting 3.7+ sounds great. Focusing only on 3.10 to start with would also be fine.

Testing many Python versions (especially 3.4) is a crude way of making tests more thorough and catching more problems. Theoretically, if an implementation passes tests in many versions, then that can make us more confident about it working in general. But that's not essential.

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

No branches or pull requests

2 participants