GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||
GeezerVison is showing github.com — GH-115986 Fix `pprint` documentation by Privat33r-dev · Pull Request #116019 · python/cpython Conversation
|
|
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. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
70b93ac to
935b04a
Compare
Ensure `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
7f5be79
Compare
|
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/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
As `pprint` might have unintended consequences with dict sorting.
Thanks for the advice. Earlier I worked on projects with different workflow where rebase was a standard procedure. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
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. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
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. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Should I rebase now or is it just for the future? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
For the future. Also, do a |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
LGTM; thanks!
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…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]>
|
GH-116061 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-116064 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…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.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.