Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

[3.13] gh-74929: PEP 667 general docs update (gh-119201)#119291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
ncoghlan merged 1 commit intopython:3.13frommiss-islington:backport-e870c85-3.13
May 21, 2024

Conversation

miss-islington
Copy link
Contributor

@miss-islingtonmiss-islington commentedMay 21, 2024•
edited by github-actionsbot
Loading

  • expand on What's New entry for PEP 667 (including porting notes)
  • define 'optimized scope' as a glossary term
  • cover comprehensions and generator expressions in locals() docs
  • review all mentions of "locals" in documentation (updating if needed)
  • review all mentions of "f_locals" in documentation (updating if needed)
    (cherry picked from commite870c85)

Co-authored-by: Alyssa Coghlanncoghlan@gmail.com

📚 Documentation preview 📚:https://cpython-previews--119291.org.readthedocs.build/

* expand on What's New entry for PEP 667 (including porting notes)* define 'optimized scope' as a glossary term* cover comprehensions and generator expressions in locals() docs* review all mentions of "locals" in documentation (updating if needed)* review all mentions of "f_locals" in documentation (updating if needed)(cherry picked from commite870c85)Co-authored-by: Alyssa Coghlan <ncoghlan@gmail.com>
@bedevere-bot
Copy link

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

Hi! The buildbots390x Fedora Clang Installed 3.13 has failed when building commitdb64dae.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/1392/builds/34) and take a look at the build logs.
  4. Check if the failure is related to this commit (db64dae) 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/1392/builds/34

Failed tests:

  • test_free_threading

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

==

Click to see traceback logs
remote:Enumerating objects: 19, done.remote:Counting objects:   5% (1/19)remote:Counting objects:  10% (2/19)remote:Counting objects:  15% (3/19)remote:Counting objects:  21% (4/19)remote:Counting objects:  26% (5/19)remote:Counting objects:  31% (6/19)remote:Counting objects:  36% (7/19)remote:Counting objects:  42% (8/19)remote:Counting objects:  47% (9/19)remote:Counting objects:  52% (10/19)remote:Counting objects:  57% (11/19)remote:Counting objects:  63% (12/19)remote:Counting objects:  68% (13/19)remote:Counting objects:  73% (14/19)remote:Counting objects:  78% (15/19)remote:Counting objects:  84% (16/19)remote:Counting objects:  89% (17/19)remote:Counting objects:  94% (18/19)remote:Counting objects: 100% (19/19)remote:Counting objects: 100% (19/19), done.remote:Compressing objects:   5% (1/19)remote:Compressing objects:  10% (2/19)remote:Compressing objects:  15% (3/19)remote:Compressing objects:  21% (4/19)remote:Compressing objects:  26% (5/19)remote:Compressing objects:  31% (6/19)remote:Compressing objects:  36% (7/19)remote:Compressing objects:  42% (8/19)remote:Compressing objects:  47% (9/19)remote:Compressing objects:  52% (10/19)remote:Compressing objects:  57% (11/19)remote:Compressing objects:  63% (12/19)remote:Compressing objects:  68% (13/19)remote:Compressing objects:  73% (14/19)remote:Compressing objects:  78% (15/19)remote:Compressing objects:  84% (16/19)remote:Compressing objects:  89% (17/19)remote:Compressing objects:  94% (18/19)remote:Compressing objects: 100% (19/19)remote:Compressing objects: 100% (19/19), done.remote:Total 19 (delta 0), reused 8 (delta 0), pack-reused 0From https://github.com/python/cpython * branch                  3.13       -> FETCH_HEADNote:switching to 'db64dae74517d094da5516b9c96d3e81e7108ebf'.You are in 'detached HEAD' state. You can look around, make experimentalchanges and commit them, and you can discard any commits you make in thisstate without impacting any branches by switching back to a branch.If you want to create a new branch to retain commits you create, you maydo 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 falseHEAD is now at db64dae745 [3.13] gh-74929: PEP 667 general docs update (gh-119291)Switched to and reset branch '3.13'configure:WARNING: s390x-ibm-linux-gnu/clang is not supportedconfigure:WARNING: no system libmpdecimal found; falling back to bundled libmpdecimal (deprecated and scheduled for removal in Python 3.15)configure:WARNING:Platform "s390x-ibm-linux-gnu" with compiler "clang" is not supported by theCPython core team, see https://peps.python.org/pep-0011/ for more information.Python/import.c:1620:1: warning: unused function 'is_core_module' [-Wunused-function]is_core_module(PyInterpreterState *interp, PyObject *name, PyObject *path)^1 warning generated.Python/pystate.c:1135:1: warning: unused function 'check_interpreter_whence' [-Wunused-function]check_interpreter_whence(long whence)^1 warning generated.  WARNING: The scripts pip3 and pip3.13 are installed in '/home/dje/cpython-buildarea/3.13.edelsohn-fedora-z.clang-installed/build/target/bin' which is not on PATH.  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.

@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 Ubuntu NoGIL 3.13 has failed when building commitdb64dae.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/1422/builds/36) and take a look at the build logs.
  4. Check if the failure is related to this commit (db64dae) 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/1422/builds/36

Failed tests:

  • test_tools

Failed subtests:

  • test_map_timeout - test.test_concurrent_futures.test_process_pool.ProcessPoolSpawnProcessPoolExecutorTest.test_map_timeout

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/ubuntu/buildarea/3.13.itamaro-ubuntu-aws.nogil/build/Lib/test/test_concurrent_futures/executor.py", line71, intest_map_timeoutself.assertEqual([None,None], results)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^AssertionError:Lists differ: [None, None] != []

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@miss-islington@bedevere-bot@ncoghlan
[8]ページ先頭
©2009-2025 Movatter.jp