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
unittest.mock has wrong heading levels #61311
Comments
If you look at http://docs.python.org/dev/library/development.html, you'll see the following outline (stripped for brevity): 26.4. unittest.mock — mock object library
26.5. The patchers 26.6. MagicMock and magic method support 26.7. Helpers 26.8. unittest.mock — getting started 26.9. Further Examples 26.10. 2to3 - Automated Python 2 to 3 code translation Instead, it should be: 26.4. unittest.mock — mock object library
26.5. unittest.mock — getting started
26.6. 2to3 - Automated Python 2 to 3 code translation (I'm also not sure the reference document should come before the getting started document) |
New changeset 72aee7ee2299 by Georg Brandl in branch '3.3': |
unittest.mock-examples.rst also needs fixing. |
New changeset 9040b3714207 by Georg Brandl in branch '3.3': |
How does the "+" level relate to the convention described here? |
Never mind :) |
I see why I was confused. The ~'s are different from -'s. The tilde level isn't listed in our devguide conventions. |
I think the conventions are just conventions, and docutils / sphinx |
Antoine is right. It's probably ok to remove that suggestion completely. |
I think the guidance is still helpful. I have referred to it often. It can just be changed to being a suggestion as opposed to "the convention that we use." |
I created bpo-17270 for this. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: