diff options
author | Serhiy Storchaka <storchaka@gmail.com> | 2021-09-28 20:40:57 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-09-28 20:40:57 (GMT) |
commit | 4f05f15d7b25ef8b690cb94fdc4c8cb5521a4e27 (patch) | |
tree | da653177934ecf5a2dc4a6c5efa3e25452ead2b7 /Doc/whatsnew | |
parent | 0c50b8c0b8274d54d6b71ed7bd21057d3642f138 (diff) | |
download | cpython-4f05f15d7b25ef8b690cb94fdc4c8cb5521a4e27.zip cpython-4f05f15d7b25ef8b690cb94fdc4c8cb5521a4e27.tar.gz cpython-4f05f15d7b25ef8b690cb94fdc4c8cb5521a4e27.tar.bz2 |
[docs] Improve the markup of powers (GH-28598)
Diffstat (limited to 'Doc/whatsnew')
-rw-r--r-- | Doc/whatsnew/2.0.rst | 2 | ||||
-rw-r--r-- | Doc/whatsnew/2.7.rst | 8 | ||||
-rw-r--r-- | Doc/whatsnew/3.1.rst | 8 | ||||
-rw-r--r-- | Doc/whatsnew/3.11.rst | 10 |
4 files changed, 14 insertions, 14 deletions
diff --git a/Doc/whatsnew/2.0.rst b/Doc/whatsnew/2.0.rst index c0a6692..0e1cf1f 100644 --- a/Doc/whatsnew/2.0.rst +++ b/Doc/whatsnew/2.0.rst @@ -791,7 +791,7 @@ Previously the Python virtual machine used 16-bit numbers in its bytecode, limiting the size of source files. In particular, this affected the maximum size of literal lists and dictionaries in Python source; occasionally people who are generating Python code would run into this limit. A patch by Charles G. -Waldman raises the limit from ``2^16`` to ``2^{32}``. +Waldman raises the limit from ``2**16`` to ``2**32``. Three new convenience functions intended for adding constants to a module's dictionary at module initialization time were added: :func:`PyModule_AddObject`, diff --git a/Doc/whatsnew/2.7.rst b/Doc/whatsnew/2.7.rst index d19c8e0..abb6522 100644 --- a/Doc/whatsnew/2.7.rst +++ b/Doc/whatsnew/2.7.rst @@ -953,12 +953,12 @@ Several performance enhancements have been added: considered and traversed by the collector. (Contributed by Antoine Pitrou; :issue:`4688`.) -* Long integers are now stored internally either in base 2**15 or in base - 2**30, the base being determined at build time. Previously, they - were always stored in base 2**15. Using base 2**30 gives +* Long integers are now stored internally either in base ``2**15`` or in base + ``2**30``, the base being determined at build time. Previously, they + were always stored in base ``2**15``. Using base ``2**30`` gives significant performance improvements on 64-bit machines, but benchmark results on 32-bit machines have been mixed. Therefore, - the default is to use base 2**30 on 64-bit machines and base 2**15 + the default is to use base ``2**30`` on 64-bit machines and base ``2**15`` on 32-bit machines; on Unix, there's a new configure option :option:`!--enable-big-digits` that can be used to override this default. diff --git a/Doc/whatsnew/3.1.rst b/Doc/whatsnew/3.1.rst index 919fbee..f1e6d0c 100644 --- a/Doc/whatsnew/3.1.rst +++ b/Doc/whatsnew/3.1.rst @@ -474,12 +474,12 @@ Build and C API Changes Changes to Python's build process and to the C API include: -* Integers are now stored internally either in base 2**15 or in base - 2**30, the base being determined at build time. Previously, they - were always stored in base 2**15. Using base 2**30 gives +* Integers are now stored internally either in base ``2**15`` or in base + ``2**30``, the base being determined at build time. Previously, they + were always stored in base ``2**15``. Using base ``2**30`` gives significant performance improvements on 64-bit machines, but benchmark results on 32-bit machines have been mixed. Therefore, - the default is to use base 2**30 on 64-bit machines and base 2**15 + the default is to use base ``2**30`` on 64-bit machines and base ``2**15`` on 32-bit machines; on Unix, there's a new configure option ``--enable-big-digits`` that can be used to override this default. diff --git a/Doc/whatsnew/3.11.rst b/Doc/whatsnew/3.11.rst index 7121bbe..484aad7 100644 --- a/Doc/whatsnew/3.11.rst +++ b/Doc/whatsnew/3.11.rst @@ -243,14 +243,14 @@ time ---- * On Unix, :func:`time.sleep` now uses the ``clock_nanosleep()`` or - ``nanosleep()`` function, if available, which has a resolution of 1 ns (10^-9 - sec), rather than using ``select()`` which has a resolution of 1 us (10^-6 - sec). + ``nanosleep()`` function, if available, which has a resolution of 1 ns + (10\ :sup:`-9` sec), rather than using ``select()`` which has a resolution + of 1 us (10\ :sup:`-6` sec). (Contributed by Livius and Victor Stinner in :issue:`21302`.) * On Windows, :func:`time.sleep` now uses a waitable timer which has a - resolution of 100 ns (10^-7 sec). Previously, it had a solution of 1 ms - (10^-3 sec). + resolution of 100 ns (10\ :sup:`-7` sec). Previously, it had a solution of 1 ms + (10\ :sup:`-3` sec). (Contributed by Livius and Victor Stinner in :issue:`21302`.) unicodedata |