Title: Documentation: 'Postive' should be 'Positive'
Type: Stage:
Components: Documentation Versions: Python 3.1, Python 3.2, Python 2.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Retro, benjamin.peterson, docs@python, georg.brandl
Priority: normal Keywords:

Created on 2010-10-12 23:05 by Retro, last changed 2010-10-13 20:01 by georg.brandl. This issue is now closed.

Messages (5)
msg118482 - (view) Author: Boštjan Mejak (Retro) Date: 2010-10-12 23:05
There's a typo in the docs. Please follow and find the below text, and fix the word 'Postive' to 'Positive', indicated between >>> and <<<:

General format. For a given precision p >= 1, this rounds the number to p significant digits and then formats the result in either fixed-point format or in scientific notation, depending on its magnitude.

The precise rules are as follows: suppose that the result formatted with presentation type 'e' and precision p-1 would have exponent exp. Then if -4 <= exp < p, the number is formatted with presentation type 'f' and precision p-1-exp. Otherwise, the number is formatted with presentation type 'e' and precision p-1. In both cases insignificant trailing zeros are removed from the significand, and the decimal point is also removed if there are no remaining digits following it.

>>>Postive<<< and negative infinity, positive and negative zero, and nans, are formatted as inf, -inf, 0, -0 and nan respectively, regardless of the precision.

A precision of 0 is treated as equivalent to a precision of 1.
msg118483 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2010-10-12 23:07
msg118484 - (view) Author: Boštjan Mejak (Retro) Date: 2010-10-12 23:19
Please commit this fix to the trunk, as well as to the Python 2.5, Python 2.6, and Python 2.7 branches. Thank you.
msg118485 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2010-10-12 23:21
Done for all branches that are maintained.
msg118572 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2010-10-13 20:01
@OP: In general, we do apply such changes to all branches they can be fixed in.  Since this is done by merging from py3k to the other branches, it can be done later than the commit to py3k, or in batches.  Please leave that branch management to us.
Date User Action Args
2010-10-13 20:01:29georg.brandlsetnosy: + georg.brandl

messages: + msg118572
versions: - Python 2.6, Python 2.5, 3rd party, Python 3.3
2010-10-13 16:10:08mark.dickinsonsetstatus: open -> closed
2010-10-12 23:21:32benjamin.petersonsetresolution: remind -> fixed
messages: + msg118485
2010-10-12 23:19:49Retrosetresolution: fixed -> remind
2010-10-12 23:19:33Retrosetstatus: closed -> open
2010-10-12 23:19:07Retrosetmessages: + msg118484
2010-10-12 23:07:38benjamin.petersonsetstatus: open -> closed

nosy: + benjamin.peterson
messages: + msg118483

resolution: fixed
2010-10-12 23:05:33Retrocreate