Migrate to the next version of Python requests when released

Hello Maintainers,

I am a PMC member of Apache Airflow, and I wanted to give you a bit of heads-up with rather important migration to the upcoming version of requests library in your Python release.

Since you are using requests library in your project, you are affected.

As discussed at length in https://issues.apache.org/jira/browse/LEGAL-572 we found out that the chardet library used by requests library was a mandatory dependency to requests and since it has LGPL licence, we should not release any Apache Software with it.

Since then (and since in Airflow we rely on requests heavily) we have been working with the requests maintainers and “charset-normalizer” maintainer to make it possible to replace chardet with MIT-licensed charset-normalizer instead so that requests library can be used in Python releases by Apache projects.

This was a bumpy road but finally the PR by @ashb has been merged: https://github.com/psf/requests/pull/5797 and we hope soon a new version of requests library will be released.

This is just a heads-up. I will let you know when it is released, but I have a kind requests as well - I might ask the maintainers to release a release candidate of requests and maybe you could help to test it before it is released, that would be some re-assurance for the maintainers of requests who are very concerned about stability of their releases.

Let me know if you need any more information and whether you would like to help in testing the candidate when it is out.

[Kami]

Since Python 3.5 is EOL for more than a year now (https://endoflife.date/python), I think it’s reasonable for us to drop support for it in the release after the next one.

Next one will be 3.4.0 and should go out this year and the one after that will be 3.5.0 and will likely go out some time next year.

What do other people think? /cc @c-w @vdloo @tonybaloney @micafer @RunOrVeith

EDIT: Per package download stats (https://pypistats.org/packages/apache-libcloud), Python 3.5, on average, represents less than 2% of daily downloads.

[Kami]

@potiuk Thanks for your input and additional context (and of course many thanks for bringing this issue to our and other projects attention and coordinating with the requests project, etc.)

@justinmclean Also thanks for your input. With all the info above, we would like to get some additional clarify on how to proceed here.

We will of course comply with any legal requirements, but we need to know how to proceed so we can plan and execute accordingly.

If there is no other way, but to update our setup.py metadata file but to require requests >= 2.26.0 (which will likely cause issues with a lot of our users and they won’t be able to upgrade), we will also need to drop support for Python 3.5 since that version is only available for Python >= 3.6 (that’s something we have been planning to do in the future anyway, but not just yet).