Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34k
GH-115986 Fix pprint documentation#116019
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
Privat33r-dev commented Feb 28, 2024 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
36ff421 to 1745629Compare1745629 to 70b93acComparePrivat33r-dev commented Feb 28, 2024
Sorry for assignments, git acted a bit funny, likely due to the fact the I pulled locally, but haven't updated repo on github, so it decided to include some other changes as part of the PR. Looks like it was resolved. |
70b93ac to 935b04aCompareEnsure `pp` and `pprint` are positioned prominently at the top of the page.
Before links pointed out to the module `pprint` instead of the `pprint.pprint` function.
935b04a to 7f5be79Comparehugovk commented Feb 28, 2024
Please don't force-push PRs, it can make things harder to review, and everything will be squash-merged at the end. Thanks! https://devguide.python.org/getting-started/pull-request-lifecycle/ |
As `pprint` might have unintended consequences with dict sorting.
Privat33r-dev commented Feb 28, 2024
Thanks for the advice. Earlier I worked on projects with different workflow where rebase was a standard procedure. |
erlend-aasland commented Feb 28, 2024
Thanks; it is better to do multiple PRs of atomic changes, than one giant PR with lots of changes. This holds both for code and docs changes. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
erlend-aasland commented Feb 28, 2024 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
One more thing: please do not mention GitHub accounts in commit messages (such as 6f4cf93); they turn up as notifications and thus end up as noise. |
Privat33r-dev commented Feb 28, 2024
Should I rebase now or is it just for the future? |
erlend-aasland commented Feb 28, 2024
For the future. Also, do a |
erlend-aasland left a comment
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.
LGTM; thanks!
This comment was marked as outdated.
This comment was marked as outdated.
…GH-116019) Introduce a new subsubsection, 'Functions', for module level functions, and place it before the PrettyPrinter class reference. Also: - Fix pprint.pprint() references so they properly link to the module level function. - Add links to sys.stdout. (cherry picked from commit 6c1c94d) Co-authored-by: Kerim Kabirov <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
GH-116061 is a backport of this pull request to the 3.12 branch. |
GH-116064 is a backport of this pull request to the 3.11 branch. |
…6019) (#116061) GH-115986 Reorder pprint docs and amend some references (GH-116019) Introduce a new subsubsection, 'Functions', for module level functions, and place it before the PrettyPrinter class reference. Also: - Fix pprint.pprint() references so they properly link to the module level function. - Add links to sys.stdout. (cherry picked from commit 6c1c94d) Co-authored-by: Kerim Kabirov <[email protected]>
…) (#116064) (cherry picked from commit 6c1c94d) Introduce a new subsubsection, 'Functions', for module level functions, and place it before the PrettyPrinter class reference. Also: - Fix pprint.pprint() references so they properly link to the module level function. - Add links to sys.stdout. Co-authored-by: Kerim Kabirov <[email protected]>
…#116019) Introduce a new subsubsection, 'Functions', for module level functions, and place it before the PrettyPrinter class reference. Also: - Fix pprint.pprint() references so they properly link to the module level function. - Add links to sys.stdout.
Amend wording after pythongh-116019 was merged. (cherry picked from commit e205c5c) Co-authored-by: Kerim Kabirov <[email protected]>
Amend wording after pythongh-116019 was merged. (cherry picked from commit e205c5c) Co-authored-by: Kerim Kabirov <[email protected]>
…#116019) Introduce a new subsubsection, 'Functions', for module level functions, and place it before the PrettyPrinter class reference. Also: - Fix pprint.pprint() references so they properly link to the module level function. - Add links to sys.stdout.
Amend wording after pythongh-116019 was merged.
…#116019) Introduce a new subsubsection, 'Functions', for module level functions, and place it before the PrettyPrinter class reference. Also: - Fix pprint.pprint() references so they properly link to the module level function. - Add links to sys.stdout.
Amend wording after pythongh-116019 was merged.
I decided to separate the solution in 2 PRs. One PR is for fixing positions, references and including information that
pprint.pprintfunction is unintuitive. And the other one would include setting upppas default.At first I thought that message about
pprint.pprintbeing unintuitive might be divisive/hard to write, but later I figured out that it's a small change and fits current PR. Examples withpprint.ppmight be divisive though, so once this PR is accepted, another PR is going to be introduced with the change.pprintmodule #115986📚 Documentation preview 📚: https://cpython-previews--116019.org.readthedocs.build/