iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 564: fix typos (#435)

This commit is contained in:
Jakub Wilk 2017-11-01 23:33:19 +01:00 committed by Łukasz Langa
parent 875153046a
commit 3ab7b4fa9e
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0564.rst
View File

@ -31,7 +31,7 @@ Rationale
Float type limited to 104 days
------------------------------
The clocks resolution of desktop and latop computers is getting closer
The clocks resolution of desktop and laptop computers is getting closer
to nanosecond resolution. More and more clocks have a frequency in MHz,
up to GHz for the CPU TSC clock.
@ -216,7 +216,7 @@ Sub-nanosecond resolution
resolutions continue to increase below the nanosecond level, new Python
functions may be needed.
In practive, the 1 nanosecond resolution is currently enough for all
In practice, the 1 nanosecond resolution is currently enough for all
structures returned by all common operating systems functions.
Hardware clocks with a resolution better than 1 nanosecond already
@ -245,7 +245,7 @@ It was proposed to modify ``time.time()`` to return a different number
type with better precision.
The PEP 410 proposed to return ``decimal.Decimal`` which already exists and
supports arbitray precision, but it was rejected. Apart from
supports arbitrary precision, but it was rejected. Apart from
``decimal.Decimal``, no portable real number type with better precision
is currently available in Python.
@ -334,7 +334,7 @@ the internal structure used by the operating system.
Script
------
Example of script ot measure the smallest difference between two
Example of script to measure the smallest difference between two
``time.time()`` and ``time.time_ns()`` reads ignoring differences of zero::
import math