-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-93573: Replace wrong example domains in configparser doc #93574
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Maybe, |
Documentation should use reserved TLDs from https://datatracker.ietf.org/doc/html/rfc2606, e.g. |
topsecret.server.com domain is not controled by PSF. It's replaced by invalid topsecret.server.example domain. It follows RFC 2606, which advise .example as TLD for documentation.
I replaced I don't think news are needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're changing to .example
, it might also be worth changing the bitbucket.org
ones? I know the domain is currently active, but extra safety doesn't hurt.
A
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
A
IMHO |
The bytebong.com domain is now available to everyone:
Should I ping a core reviewer for the merge? |
Thanks @sblondon for the PR, and @JulienPalard for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. |
GH-101953 is a backport of this pull request to the 3.11 branch. |
…thonGH-93574) * Replace bitbucket.org domain by forge.example * Update example to python.org * Use explicitly invalid domain topsecret.server.com domain is not controled by PSF. It's replaced by invalid topsecret.server.example domain. It follows RFC 2606, which advise .example as TLD for documentation. (cherry picked from commit 924a3bf) Co-authored-by: sblondon <stephane.blondon@gmail.com>
GH-101954 is a backport of this pull request to the 3.10 branch. |
…thonGH-93574) * Replace bitbucket.org domain by forge.example * Update example to python.org * Use explicitly invalid domain topsecret.server.com domain is not controled by PSF. It's replaced by invalid topsecret.server.example domain. It follows RFC 2606, which advise .example as TLD for documentation. (cherry picked from commit 924a3bf) Co-authored-by: sblondon <stephane.blondon@gmail.com>
* Replace bitbucket.org domain by forge.example * Update example to python.org * Use explicitly invalid domain topsecret.server.com domain is not controled by PSF. It's replaced by invalid topsecret.server.example domain. It follows RFC 2606, which advise .example as TLD for documentation. (cherry picked from commit 924a3bf) Co-authored-by: sblondon <stephane.blondon@gmail.com>
* Replace bitbucket.org domain by forge.example * Update example to python.org * Use explicitly invalid domain topsecret.server.com domain is not controled by PSF. It's replaced by invalid topsecret.server.example domain. It follows RFC 2606, which advise .example as TLD for documentation. (cherry picked from commit 924a3bf) Co-authored-by: sblondon <stephane.blondon@gmail.com>
…thonGH-93574) * Replace bitbucket.org domain by forge.example * Update example to python.org * Use explicitly invalid domain topsecret.server.com domain is not controled by PSF. It's replaced by invalid topsecret.server.example domain. It follows RFC 2606, which advise .example as TLD for documentation.
This minor PR replaces bytebong.com to python.org in configparser example in order to use a domain the PSF controls.
topsecret.server.com
is obviously an example and I don't thinkbitbucket.org
is a risk currently so they are not modified.