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

Use replacements to update versions in "Using Python on macOS"#130400

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
ned-deily merged 7 commits intopython:mainfromhugovk:3.14-doc-usemac-replacements
Jun 16, 2025

Conversation

hugovk
Copy link
Member

@hugovkhugovk commentedFeb 21, 2025
edited by github-actionsbot
Loading

So the versions inhttps://docs.python.org/3.13/using/mac.html andhttps://docs.python.org/3.14/using/mac.html aren't hardcoded to "3.13", and reflect the current version.


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

@hugovkhugovk added the needs backport to 3.13bugs and security fixes labelFeb 21, 2025
@hugovkhugovk added skip issue skip news docsDocumentation in the Doc dir labelsFeb 21, 2025
Copy link
Member

@ned-deilyned-deily left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thanks for doing this. Note there are still some hardwired 3.13 path references in the Advanced Topics section; it would be nice to address those, too.

hugovk reacted with thumbs up emoji
@hugovk
Copy link
MemberAuthor

Thanks, I've replaced some more. Unfortunately the formatting isn't as good, but I think it's acceptable from a maintenance point of view, if there's no better solution?

BeforeAfter
imageimage

But I've not replaced the hardcoded versions in this section, I don't have a good method for that:

https://docs.python.org/dev/using/mac.html#installing-using-the-command-line

ned-deily reacted with thumbs up emoji

@AA-Turner
Copy link
Member

Would an alternative be to have a test/lint ensuring that the version is current? It would be a shame to accept strictly worse aesthetics for a tooling problem.

A

ned-deily reacted with thumbs up emoji

@hugovk
Copy link
MemberAuthor

That could work, what sort of thing do you have in mind?

Of course, it would be great if Sphinx directly supported replacements in code blocks ;)


Oh, I've just discoveredparsed literal blocks:

This gives improved formatting, although no syntax highlighting:

BeforeAfter
imageimage
imageimage

@ned-deily
Copy link
Member

ned-deily commentedFeb 25, 2025
edited
Loading

I struggled with how to handle versions in formatted code when I did the rewrite for 3.13. I'm glad I'm not the only one! If it could be done without a lot of trouble, the linting solution sounds fine until (if ever) there is a better solution with Sphinx / Docutils as this only needs to be updated once a year. But I'll leave it up to you(s).

@python-cla-bot
Copy link

python-cla-botbot commentedApr 18, 2025
edited
Loading

All commit authors signed the Contributor License Agreement.

CLA signed

@serhiy-storchakaserhiy-storchaka added the needs backport to 3.14bugs and security fixes labelMay 8, 2025
@ned-deily
Copy link
Member

Getting back to this, it looks fine to me. Thanks,@hugovk! I'm going to merge it now and backport to 3.14 and 3.13 before any further editing (like removing theexperimental qualification for free-threading and potentially updating the images).

hugovk reacted with thumbs up emoji

@ned-deilyned-deily merged commit21bac3a intopython:mainJun 16, 2025
24 checks passed
@github-project-automationgithub-project-automationbot moved this fromTodo toDone inDocs PRsJun 16, 2025
@miss-islington-app
Copy link

Thanks@hugovk for the PR, and@ned-deily for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull requestJun 16, 2025
…nGH-130400)(cherry picked from commit21bac3a)Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
@bedevere-app
Copy link

GH-135586 is a backport of this pull request to the3.14 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull requestJun 16, 2025
…nGH-130400)(cherry picked from commit21bac3a)Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
@bedevere-appbedevere-appbot removed the needs backport to 3.14bugs and security fixes labelJun 16, 2025
@bedevere-app
Copy link

GH-135587 is a backport of this pull request to the3.13 branch.

@bedevere-appbedevere-appbot removed the needs backport to 3.13bugs and security fixes labelJun 16, 2025
ned-deily pushed a commit that referenced this pull requestJun 16, 2025
…GH-130400) (#135586)(cherry picked from commit21bac3a)Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
ned-deily pushed a commit that referenced this pull requestJun 16, 2025
…GH-130400) (#135587)(cherry picked from commit21bac3a)Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
@bedevere-bot
Copy link

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

Hi! The buildbotARM64 MacOS M1 Refleaks NoGIL 3.14 (tier-2) has failed when building commita2c4791.

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

Failed tests:

  • test.test_multiprocessing_spawn.test_processes

Test leaking resources:

  • test_processes: references
  • test_processes: memory blocks

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

==

Click to see traceback logs
Traceback (most recent call last):  File"<string>", line1, in<module>from multiprocessing.resource_trackerimport main;main(7)~~~~^^^  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/resource_tracker.py", line317, inmain    warnings.warn('resource_tracker:%r:%s'% (name, e))~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^UserWarning:resource_tracker: '/mp-nvkm09zy': [Errno 2] No such file or directoryTraceback (most recent call last):  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/util.py", line291, in__call__    res=self._callback(*self._args,**self._kwargs)  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/synchronize.py", line87, in_cleanup    unregister(name,"semaphore")  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/resource_tracker.py", line216, inunregisterself._send('UNREGISTER', name, rtype)  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/resource_tracker.py", line226, in_send    warnings.warn(UserWarning:ResourceTracker called reentrantly for resource cleanup, which is unsupported. The semaphore object '/mp-z615kmhc' might leak.Warning -- Unraisable exceptionException ignored while calling weakref callback <Finalize object, dead>:Traceback (most recent call last):  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/util.py", line291, in__call__    res=self._callback(*self._args,**self._kwargs)  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/synchronize.py", line87, in_cleanup    unregister(name,"semaphore")  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/resource_tracker.py", line216, inunregisterself._send('UNREGISTER', name, rtype)  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/resource_tracker.py", line226, in_send    warnings.warn(UserWarning:ResourceTracker called reentrantly for resource cleanup, which is unsupported. The semaphore object '/mp-nvkm09zy' might leak.kTraceback (most recent call last):  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/process.py", line320, in_bootstrapself.run()~~~~~~~~^^  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/process.py", line108, inrunself._target(*self._args,**self._kwargs)~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/test/_test_multiprocessing.py", line518, in_sleep_some_event    time.sleep(100)~~~~~~~~~~^^^^^KeyboardInterruptkTraceback (most recent call last):  File"/Users/ec2-user/buildbot/buildarea/3.14.itamaro-macos-arm64-aws.macos-with-brew.refleak.nogil/build/Lib/multiprocessing/resource_tracker.py", line314, inmain_CLEANUP_FUNCS[rtype](name)~~~~~~~~~~~~~~~~~~~~~^^^^^^FileNotFoundError:[Errno 2] No such file or directory

@hugovkhugovk deleted the 3.14-doc-usemac-replacements branchJune 17, 2025 11:53
lkollar pushed a commit to lkollar/cpython that referenced this pull requestJun 19, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@ned-deilyned-deilyned-deily left review comments

@AA-TurnerAA-TurnerAwaiting requested review from AA-TurnerAA-Turner is a code owner

Assignees
No one assigned
Labels
docsDocumentation in the Doc dirskip issueskip news
Projects
Status: Done
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@hugovk@AA-Turner@ned-deily@bedevere-bot@serhiy-storchaka

[8]ページ先頭

©2009-2025 Movatter.jp