Drop Python 3.6 Support

[auvipy]

as python 3.6 is EOL

[auvipy]

I can also drop un supported or EOL django versions either in this PR or in a separate one. it's the maintainers call

[wieczorek1990]

Seems ok.

[auvipy]

@tomchristie boss O:)

[onegreyonewhite]

@tomchristie does it really necessary in 3.14? You haven't updated any dependence which requires that. You haven't used any syntaxes which requires the dropping old version. It will create more problems for developers but there are no profits for you.

I hope you will make informed decision. Thank you🙏🏼

[auvipy]

Python 3.6 is EOL, it is not wise to continue using it.

[onegreyonewhite]

Python 3.6 is EOL

OK. What's latest version of Python you can install to CentOS/RH 7 (which supports until 2024)?

It's not a wise to drop support without real need.

P.S.: django 2.2 EOL too. May be should cut it too?

[auvipy]

you should not use the system python on the first place. and you can upgrade to centOS 8 as well. and django 2.2, 3.0, 3.1 etc should also should not be used as they reached EOL.

[auvipy]

And you can use Pyenv for installing any non EOL python versions

[onegreyonewhite]

And you can use Pyenv for installing any non EOL python versions

I think you've confused development tools with production delivery tools.
Bringing your own python into each system is a dumb idea.

Well, it's your decision, I understand.

[auvipy]

I think you've confused development tools with production delivery tools.
Bringing your own python into each system is a dumb idea.

I understand how up to date you are.

[tomchristie]

Thank you @auvipy. Reasonable suggestion, yup. 😌

We don't have a clear policy on which Python versions we support.
I'd suggest that we should simply follow whatever Django requires.

We then need to clarify what policy we have for "which versions of Django should we support?".

Here's what I'd propose...

• We release new versions of REST framework twice a year. Same as for Django.
• We aim each new release to arrive shortly after each Django release.
• We always support the latest 5 Django releases.
• We support whichever Python versions are required by Django.

Why "support the latest 5 Django releases"? Well, because I'd like it to always be a simple fixed number, and (unless I'm messing this up?) that's the lowest number we could pick that ensures we never drop a Django version that's still covered by their "extended support" policy.

The implication for our upcoming 3.14 release is that we ought to support...

• Django 3.0, 3.1, 3.2, 4.0, 4.1.
• Python 3.6+. (See the Meta section of https://pypi.org/project/Django/3.0/)

[auvipy]

that would be a reasonable default policy

[tomchristie]

Alrighty then, let's close this off (for now).

Thanks for your time on it @auvipy. Good to get to a sensible policy here.

[wieczorek1990]

Some compile :) W dniu sob., 10.09.2022 o 11:20 Asif Saif Uddin ***@***.***> napisał(a):

…

I think you've confused development tools with production delivery tools. Bringing your own python into each system is a dumb idea. I understand how up to date you are. — Reply to this email directly, view it on GitHub <#8518 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMRLK3UJO4NK4TKVWBXKOLV5RHG3ANCNFSM5YGVPKEQ> . You are receiving this because you commented.Message ID: ***@***.***>