Drop 3.5

[asvetlov]

Fixes #3947

[webknjaz]

@asvetlov FYI I've rebased this

[webknjaz]

It's okay to just remove this check since setuptools that supports python_requires is shipped with Python 3.6.

[asvetlov]

I want to fail loudly even on Python 3.5

[webknjaz]

I've triggered a full matrix build for this branch now: https://travis-ci.com/aio-libs/aiohttp/builds/126532209

[asvetlov]

Thanks.
pypy fails on the branch on yarl encoding, I need to investigate

[asvetlov]

The failure source is different behavior of yarl quoting/unquoting for cythonized and pure python versions

[asvetlov]

The failure reason is a different behavior of pure python and cythonized yarl versions.
The bug is fixed on yarl master, I'll move failed tests into yarl repository.

[patchback]

Backport to 3.9: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply cfb40b7 on top of patchback/backports/3.9/cfb40b7282ce41d10fcfc2021992808760f9bf6e/pr-4046

Backporting merged PR #4046 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.9/cfb40b7282ce41d10fcfc2021992808760f9bf6e/pr-4046 upstream/3.9

4. Now, cherry-pick PR Drop 3.5 #4046 contents into that branch:

   $ git cherry-pick -x cfb40b7282ce41d10fcfc2021992808760f9bf6e

   If it'll yell at you with something like fatal: Commit cfb40b7282ce41d10fcfc2021992808760f9bf6e is a merge but no -m option was given., add -m 1 as follows intead:

   $ git cherry-pick -m1 -x cfb40b7282ce41d10fcfc2021992808760f9bf6e

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Drop 3.5 #4046 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.9/cfb40b7282ce41d10fcfc2021992808760f9bf6e/pr-4046

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to 3.8: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply cfb40b7 on top of patchback/backports/3.8/cfb40b7282ce41d10fcfc2021992808760f9bf6e/pr-4046

Backporting merged PR #4046 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.8/cfb40b7282ce41d10fcfc2021992808760f9bf6e/pr-4046 upstream/3.8

4. Now, cherry-pick PR Drop 3.5 #4046 contents into that branch:

   $ git cherry-pick -x cfb40b7282ce41d10fcfc2021992808760f9bf6e

   If it'll yell at you with something like fatal: Commit cfb40b7282ce41d10fcfc2021992808760f9bf6e is a merge but no -m option was given., add -m 1 as follows intead:

   $ git cherry-pick -m1 -x cfb40b7282ce41d10fcfc2021992808760f9bf6e

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Drop 3.5 #4046 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.8/cfb40b7282ce41d10fcfc2021992808760f9bf6e/pr-4046

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[webknjaz]

Backported as 72d3550 and 461c98c to address the compatibility issues with Python 3.11 in tests.