-
-
Notifications
You must be signed in to change notification settings - Fork 497
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 support for running on legacy Python? #1958
Comments
I don't have a version support policy anywhere. I generally deprecate the versions once it's a pain to support them in the CI or deprecations are a problem (like the ones you are talking about). The reason why 3.6 is still supported is that 3.6 hasn't been a problem for a long time. So if you feel like a new version would benefit a lot from dropping Python < 3.9 we could also do that. Since Jedi isn't moving in a big pace anymore, it's not a big issue for users anyway, because they can just use older packages. So feel free to propose whatever. Personally I feel it's a bit early to drop 3.8, but < 3.7 is end of life officially, so I don't care about them anymore really. |
@davidhalter what are your thoughts on dropping support for running on older versions of Python? Looking at some of the deprecation warnings we're getting, support for e.g: Python 3.14 (when we get there) is likely to mean we need to drop support for Python < 3.9. There could be other things we hit sooner.
I'm assuming that we could keep the grammars around so that Jedi can keep support for parsing older versions of Python if that's desired. Do you have a version support policy somewhere?
The text was updated successfully, but these errors were encountered: