Skip to content

[RFC] allow major pytest releases to drop suport for soon to be eol python #11008

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

Open
RonnyPfannschmidt opened this issue May 16, 2023 · 4 comments
Labels
type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature

Comments

@RonnyPfannschmidt
Copy link
Member

follow up to #10981

in case there is a clear benefit for maintenance and the eol is close-by,
i want to allow major pytest releases to be allowed to drop support for soon to eol python versions

i would consider eol < 6 months away a good cut off

@nicoddemus
Copy link
Member

nicoddemus commented May 16, 2023

I gotta say my knee jerk reaction is -0.5 on this... we need to have very clear benefits I think to drop a Python version that is still supported.

Can we discuss a few examples where dropping a still supported version would be important? We could use those examples as basis to conclude that a certain Python version could be dropped, and used in the backwards compatibility document as reference.

@nicoddemus nicoddemus added the type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature label May 16, 2023
@Zac-HD
Copy link
Member

Zac-HD commented Jul 6, 2024

I just don't think this is worth the cost to users; Pytest is incredibly widely used and we'd only be buying ourselves a few months.

@Pierre-Sassoulas
Copy link
Member

I'm not sure that the cost for users is very high : they can still use the latest pytest compatible with their python interpreter. I don't remember a pytest version so bad that I had to upgrade because it was unusable otherwise. If there is a situation like this this we can still choose to backport. Also, the type of users that want to be on bleeding edge for all their dependencies is less likely to have a near EOL interpreter, so the users that would be affected are less likely to care much. (I've been stuck on an old interpreter for years but then 6 months if update is not going to make that big of a difference).

@RonnyPfannschmidt
Copy link
Member Author

Some examples are details like runtime support for modern annotations,the new type syntax

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature
Projects
None yet
Development

No branches or pull requests

4 participants