Stop using the cgi module, deprecated in Python 3.11 per PEP 594

[scop]

What do these changes do?

Removes use of the cgi module which is deprecated in 3.11+ per https://peps.python.org/pep-0594/#cgi

Are there changes in behavior for the user?

No

Related issue number

No

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> for example (588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the pr
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

[scop]

Untested and mostly for discussion purposes for now, quite likely some refinements would be in order.

[codecov]

Codecov Report

Merging #6708 (b2c51ac) into master (65bf205) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #6708   +/-   ##
=======================================
  Coverage   93.36%   93.36%           
=======================================
  Files         104      104           
  Lines       30628    30631    +3     
  Branches     3077     3077           
=======================================
+ Hits        28596    28599    +3     
  Misses       1859     1859           
  Partials      173      173           

Flag	Coverage Δ
unit	93.28% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
aiohttp/helpers.py	95.78% <100.00%> (+0.02%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 65bf205...b2c51ac. Read the comment docs.

[patchback]

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

❌ Failed to cleanly apply a045480 on top of patchback/backports/3.9/a0454809e3fd15f70c95d794addf005d9bd95b23/pr-6708

Backporting merged PR #6708 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/a0454809e3fd15f70c95d794addf005d9bd95b23/pr-6708 upstream/3.9

4. Now, cherry-pick PR Stop using the cgi module, deprecated in Python 3.11 per PEP 594 #6708 contents into that branch:

   $ git cherry-pick -x a0454809e3fd15f70c95d794addf005d9bd95b23

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

   $ git cherry-pick -m1 -x a0454809e3fd15f70c95d794addf005d9bd95b23

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Stop using the cgi module, deprecated in Python 3.11 per PEP 594 #6708 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.9/a0454809e3fd15f70c95d794addf005d9bd95b23/pr-6708

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.

[Dreamsorcerer]

If you could also handle the backport, that would be great.

[scop]

#6734

[patchback]

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

❌ Failed to cleanly apply a045480 on top of patchback/backports/3.8/a0454809e3fd15f70c95d794addf005d9bd95b23/pr-6708

Backporting merged PR #6708 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/a0454809e3fd15f70c95d794addf005d9bd95b23/pr-6708 upstream/3.8

4. Now, cherry-pick PR Stop using the cgi module, deprecated in Python 3.11 per PEP 594 #6708 contents into that branch:

   $ git cherry-pick -x a0454809e3fd15f70c95d794addf005d9bd95b23

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

   $ git cherry-pick -m1 -x a0454809e3fd15f70c95d794addf005d9bd95b23

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Stop using the cgi module, deprecated in Python 3.11 per PEP 594 #6708 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.8/a0454809e3fd15f70c95d794addf005d9bd95b23/pr-6708

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 to 3.8 as cb79f0d