-
-
Notifications
You must be signed in to change notification settings - Fork 795
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
Add big O notation to the style guide #1261
Conversation
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.
In this case a regular reST table (compact form) would probably be more readable then a list table (and save a few lines).
Somewhat unrelated, but I was wondering whether using (and recommending) ²
instead of :sup:`2`
would be better, especially since the latter tends to become a regular 2
once copy-pasted.
Hmm, could be. We'd need to check epub/PDF/accessibility etc. |
This feels wrong to me: The "O" isn't an emphasized "O". This is a mathematical formula, so IMHO the
This should work in both the PDF/TeX and the HTML output. |
|
I did some research but I didn't find anything too conclusive. MDN says:
Wikipedia says:
and links to a Unicode document. Some screen readers seem to have options to handle |
https://stackoverflow.com/a/12224471/724176 says to use the Unicode version where available instead of Similarly https://stackoverflow.com/a/76931597/724176 says ² is better for accessibility and mentions some screen readers that have problems with It also links to https://adrianroselli.com/2022/09/brief-note-on-super-and-subscript-text.html by an a11y expert, showing problems some screen readers have with |
Let's merge this, it reflects what we're using now. If we update the docs to Unicode ² instead of |
Following python/cpython#113695, document how to add big O notation.
📚 Documentation preview 📚: https://cpython-devguide--1261.org.readthedocs.build/documentation/style-guide/#big-o-notation