[3.14] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped in a Task

[deadlovelll]

Fix wait_for() docs claiming a coroutine is wrapped in a Task

Manual backprort of #155895 for 3.14

• Issue: asyncio.wait_for() docs still say a coroutine is wrapped in a Task #155894

[read-the-docs-community]

Documentation build overview

📚 cpython-previews | 🛠️ Build #34137258 | 📁 Comparing 4d48fdd against main (61818b6)

  🔍 Preview build  

418 files changed · + 1 added · ± 397 modified · - 20 deleted

+ Added

• library/asyncio-policy.html

± Modified

• about.html
• bugs.html
• glossary.html
• index.html
• license.html
• py-modindex.html
• c-api/allocation.html
• c-api/apiabiversion.html
• c-api/arg.html
• c-api/buffer.html
• and 387 more...

- Deleted

• _static/tachyon-example-flamegraph.html
• _static/tachyon-example-heatmap.html
• c-api/sentinel.html
• c-api/slots.html
• deprecations/c-api-pending-removal-in-3.19.html
• deprecations/c-api-pending-removal-in-3.20.html
• deprecations/pending-removal-in-3.20.html
• deprecations/pending-removal-in-3.21.html
• deprecations/soft-deprecations.html
• extending/first-extension-module.html
• and 10 more...

[bedevere-bot]

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

Hi! The buildbot AMD64 Fedora Stable LTO + PGO 3.14 (tier-1) has failed when building commit 5a7c9d2.

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/#/builders/1723/builds/1171) and take a look at the build logs.
4. Check if the failure is related to this commit (5a7c9d2) 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/#/builders/1723/builds/1171

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

Click to see traceback logs

Note: switching to '5a7c9d25588ba41cfd93ec32ccdb67e4519b1d74'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 5a7c9d25588ba [3.14] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped in a Task (#156039)
Switched to and reset branch '3.14'

find: ‘build’: No such file or directory
find: ‘build’: No such file or directory
find: ‘build’: No such file or directory
find: ‘build’: No such file or directory
make[2]: [Makefile:3398: clean-retain-profile] Error 1 (ignored)
./Modules/socketmodule.c: In function ‘getsockaddrarg’:
./Modules/socketmodule.c:2646:9: warning: ‘strncpy’ specified bound 64 equals destination size [-Wstringop-truncation]
 2646 |         strncpy((char *)sa->salg_name, name, sizeof(sa->salg_name));
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ar: unable to copy file 'libpython3.14.a'; reason: No space left on device
make[2]: *** [Makefile:1180: libpython3.14.a] Error 1
make[1]: *** [Makefile:1012: profile-gen-stamp] Error 2
make: *** [Makefile:1024: profile-run-stamp] Error 2

[bedevere-bot]

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

Hi! The buildbot AMD64 Fedora Stable LTO 3.14 (tier-1) has failed when building commit 5a7c9d2.

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/#/builders/1760/builds/1165) and take a look at the build logs.
4. Check if the failure is related to this commit (5a7c9d2) 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/#/builders/1760/builds/1165

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

Click to see traceback logs

Note: switching to '5a7c9d25588ba41cfd93ec32ccdb67e4519b1d74'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 5a7c9d25588 [3.14] gh-155894: Fix wait_for() docs claiming a coroutine is wrapped in a Task (#156039)
Switched to and reset branch '3.14'

ar: unable to copy file 'libpython3.14.a'; reason: No space left on device
make: *** [Makefile:1180: libpython3.14.a] Error 1