Aaron Maenpaa added the comment:
I can understand what was meant. You're welcome to close the issue.
Sorry for the nitpick.
--
___
Python tracker
<http://bugs.python.org/is
Aaron Maenpaa added the comment:
Here is a patch that adds an note about using Locks, RLocks, Conditions, and
Semaphores as context managers to each of their descriptions as well as a link
to the "Using locks, conditions, and semaphores in the with statement" section.
-
Aaron Maenpaa added the comment:
That's fine. I'm not particularly attached to that phrasing.
The one thing I would push for is to add a comma to "... decimal is preferred
in accounting applications which have strict equality invariants."
... since, as far as I can tell
Aaron Maenpaa added the comment:
Here's a patch that makes the WWW-Authenticate headers in howto/urllib2 agree
with rfc2617.
--
keywords: +patch
nosy: +zacherates
Added file: http://bugs.python.org/file24166/issue13587.diff
___
Python tr
New submission from Aaron Maenpaa :
The paragraph: "The exactness carries over into arithmetic. In decimal floating
point, 0.1 + 0.1 + 0.1 - 0.3 is exactly equal to zero. In binary floating
point, the result is 5.5511151231257827e-017. While near to zero, the
differences prevent rel
New submission from Aaron Maenpaa :
In the sentance: "In contrast, numbers like 1.1 and 2.2 do not have an exact
representations in binary floating point." there is a mismatch in number
between "an" and "representations". I suggest removing "an" to m
Aaron Maenpaa added the comment:
Here is a patch that adds an explination for the difference in the behaviour to
the FAQ section of the Decimal documentation.
--
keywords: +patch
nosy: +zacherates
Added file: http://bugs.python.org/file24162/issue12005.diff
Aaron Maenpaa added the comment:
Looks like the issue of the first line of utcoffsect was also raised in issue
8810.
--
___
Python tracker
<http://bugs.python.org/issue13
Aaron Maenpaa added the comment:
This patch fixes the rzinfo typo as well as the GMT2 issue (GMT +2 should
behave exactly the same as GMT +1 with regards to DST, it's base offset should
simply be +2 hours instead of +1).
This does not; however, address the comment about the first line o
