Skip to content

Adhere to the standard for dropping Python versions #27557

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

Closed
datapythonista opened this issue Jul 24, 2019 · 8 comments
Closed

Adhere to the standard for dropping Python versions #27557

datapythonista opened this issue Jul 24, 2019 · 8 comments
Assignees
Labels
Dependencies Required and optional dependencies Docs good first issue
Milestone

Comments

@datapythonista
Copy link
Member

Maintainers from several scientific Python projects are defining a standard to for all projects to drop support of old Python versions in a synchronized way. The standard is defined in this PR: numpy/numpy#14086

I think pandas is already quite synchronized with the rest of the ecosystem, and I think the timeline of the standard matches what we have in mind in the short term (stopping support of Python 3.5 in the next release).

I create this issue to have a discussion in case anyone has comments. And I propose that if there is agreement, we adhere to the standard formally.

@datapythonista datapythonista added Ideas Long-Term Enhancement Discussions 2/3 Compat Dependencies Required and optional dependencies labels Jul 24, 2019
@TomAugspurger
Copy link
Contributor

TomAugspurger commented Jul 24, 2019 via email

@jorisvandenbossche
Copy link
Member

+1 as well

@jbrockmendel
Copy link
Member

Works for me.

@simonjayhawkins
Copy link
Member

from https://numpy.org/neps/nep-0029-deprecation_policy.html#implementation

Implementation
We suggest that all projects adopt the following language into their development guidelines:

This project supports:

All minor versions of Python released 42 months prior to the project, and at minimum the two latest minor versions.

All minor versions of numpy released in the 24 months prior to the project, and at minimum the last thee minor versions.

In setup.py, the python_requires variable should be set to the minimum supported version of Python. All supported minor versions of Python should be in the test matrix and have binary artifacts built for the release.

Minimum Python and NumPy version support should be adjusted upward on every major and minor release, but never on a patch release.

@simonjayhawkins simonjayhawkins removed the Ideas Long-Term Enhancement Discussions label Oct 4, 2019
@mroeschke
Copy link
Member

mroeschke commented Jul 10, 2021

Think all that's left is documenting that we mirror numpy in https://pandas.pydata.org/docs/development/policies.html

@Sadin
Copy link

Sadin commented Nov 10, 2021

Hello all, I'd like to tackle this, what needs to be updated? Docs?

@MarcoGorelli
Copy link
Member

That's right

@JosephParampathu
Copy link
Contributor

take

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependencies Required and optional dependencies Docs good first issue
Projects
None yet
Development

No branches or pull requests