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

Drop Python 3.6 support #250

Closed
Saransh-cpp opened this issue Sep 1, 2022 · 2 comments · Fixed by #251
Closed

Drop Python 3.6 support #250

Saransh-cpp opened this issue Sep 1, 2022 · 2 comments · Fixed by #251
Milestone

Comments

@Saransh-cpp
Copy link
Member

Just saw scikit-hep/awkward#1661

I remember @henryiii mentioning dropping Python 3.6 support. Maybe this should be dropped in Vector v1.0?

@jpivarski
Copy link
Member

I know he's in favor of dropping it everywhere and getting into a regular schedule of adopting/dropping Python versions according to coordinated standards (e.g. NEP 29 and Scikit-HEP developer pages).

It's best, however, to drop a Python version while not also introducing a lot of other changes, so that users don't have to choose between features that are known to work in Python 3.6 (because your tests against Vector's main pass) and being able to use Python 3.6.

They should probably also align with at least minor version updates. You have a lot of changes since 0.8.5, so you'd want to release 0.9.0 with Python 3.6 support, so that users can get these updates even if they can't give up Python 3.6, and then immediately release 0.10.0 without Python 3.6 support and develop from there, so that constraints on what versions people can use are as independent of each other as possible. Version 1.0.0 will include other big changes.

@Saransh-cpp
Copy link
Member Author

Saransh-cpp commented Sep 2, 2022

Oh, that makes sense, thanks! I will remove the support once v0.9.0 is out, and tag a new version along with the removal (v0.10.0).

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 a pull request may close this issue.

2 participants