bpo-42740: Fix get_args for PEP 585 collections.abc.Callable

[Fidget-Spinner]

PR 1/2. Needs backport to 3.9.

https://bugs.python.org/issue42740

Automerge-Triggered-By: GH:gvanrossum

[Fidget-Spinner]

I deleted the news entry as it can share the same one as GH-23060.

[miss-islington]

Sorry, I can't merge this PR. Reason: Base branch was modified. Review and try the merge again..

[miss-islington]

Sorry, I can't merge this PR. Reason: Base branch was modified. Review and try the merge again..

[miss-islington]

@Fidget-Spinner: Status check is done, and it's a success ✅ .

[miss-islington]

Sorry, I can't merge this PR. Reason: Pull Request is not mergeable.

[miss-islington]

Thanks @Fidget-Spinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

[bedevere-bot]

GH-23977 is a backport of this pull request to the 3.9 branch.

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot s390x RHEL8 LTO 3.x has failed when building commit 4140f10.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/567/builds/1215) and take a look at the build logs.
4. Check if the failure is related to this commit (4140f10) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/567/builds/1215

Summary of the results of the build (if available):

== Tests result: ENV CHANGED ==

411 tests OK.

10 slowest tests:

• test_concurrent_futures: 3 min 10 sec
• test_peg_generator: 2 min 52 sec
• test_gdb: 1 min 49 sec
• test_multiprocessing_spawn: 1 min 7 sec
• test_multiprocessing_forkserver: 59.1 sec
• test_asyncio: 55.4 sec
• test_multiprocessing_fork: 51.8 sec
• test_signal: 47.0 sec
• test_tokenize: 36.3 sec
• test_io: 33.3 sec

1 test altered the execution environment:
test_asyncio

14 tests skipped:
test_devpoll test_ioctl test_kqueue test_msilib test_nis
test_ossaudiodev test_startfile test_tix test_tk test_ttk_guionly
test_winconsoleio test_winreg test_winsound test_zipfile64

Total duration: 4 min 53 sec

Click to see traceback logs

Traceback (most recent call last):
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel8-z.lto/build/Lib/asyncio/sslproto.py", line 321, in __del__
    self.close()
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel8-z.lto/build/Lib/asyncio/sslproto.py", line 316, in close
    self._ssl_protocol._start_shutdown()
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel8-z.lto/build/Lib/asyncio/sslproto.py", line 590, in _start_shutdown
    self._abort()
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel8-z.lto/build/Lib/asyncio/sslproto.py", line 731, in _abort
    self._transport.abort()
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel8-z.lto/build/Lib/asyncio/selector_events.py", line 680, in abort
    self._force_close(None)
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel8-z.lto/build/Lib/asyncio/selector_events.py", line 731, in _force_close
    self._loop.call_soon(self._call_connection_lost, exc)
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel8-z.lto/build/Lib/asyncio/base_events.py", line 745, in call_soon
    self._check_closed()
  File "/home/dje/cpython-buildarea/3.x.edelsohn-rhel8-z.lto/build/Lib/asyncio/base_events.py", line 510, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

[gvanrossum]

@Mariatta, can you look at the comments by Miss Islington in this PR? She seemed confused (several messages with "Status check, it's a success" but a red X mark). In general she often leaves noise comments -- perhaps several actions each trigger a run and the runs race with each other?

[Fidget-Spinner]

@Mariatta, can you look at the comments by Miss Islington in this PR? She seemed confused (several messages with "Status check, it's a success" but a red X mark). In general she often leaves noise comments -- perhaps several actions each trigger a run and the runs race with each other?

I think the PR with "Status check, it's a success", with a red X mark is GH-23942.