Mailman 3 August 2013 - docs

printing unicode strings
by Chuck Simmons Aug. 9, 2013

Aug. 9, 2013

Context: I'm getting UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in position 7: ordinal not in range(128) from the code print '%s%s%s' % (prefix, value, suffix), [Here, 'value' contains unicode characters, while prefix and suffix contain 7-bit characters.] So I went to http://docs.python.org/2/howto/unicode.html#reading-and-writing-unicode-data to determine what I should do to fix my bug. I saw the section "Reading and Writing Unicode Data<http://docs.python.org/2/howto/unicode.html#reading-and-writing-unicode-data>", which seemed relevant. That section doesn't seem to discuss printing to stdout. No doubt I got confused and didn't read carefully enough, but it might be the case that if the Reading and Writing section had an example of printing a unicode string to stdout that it would have helped me find a solution faster. g'luck, Chuck

1 0

Error in heapq documentation
by Tristan Naumann Aug. 9, 2013

Aug. 9, 2013

The current heapq documentation states that: - heapq.nlargest(n, iterable[, key]) is "Equivalent to: sorted(iterable, key=key, reverse=True)[:n]" - heapq.nsmallest(n, iterable[, key]) is "Equivalent to: sorted(iterable, key=key)[:n]" However, this does not hold true when n = None. Specifically, heapq throws an exception while slicing appears to produce a shallow copy of the sorted list. Thanks! --Tristan

1 0

[issue18445] Tools/Script/Readme is outdated
by Ezio Melotti Aug. 8, 2013

Aug. 8, 2013

Changes by Ezio Melotti <ezio.melotti(a)gmail.com>: ---------- keywords: +easy nosy: +ezio.melotti _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18445> _______________________________________

1 0

[issue18267] xmlrpc.client documentation multicall example missleading for division behaviour of python3
by Bernhard Reiter Aug. 8, 2013

Aug. 8, 2013

New submission from Bernhard Reiter: http://docs.python.org/3.4/library/xmlrpc.client.html as of 2013-06-19 20:35 UTC has a divide example and the output can misslead the learning reader towards the new behaviour of python3 with the '/' binary operator for division. server code: def divide(x, y): return x/y client code: multicall.divide(7,3) [..] print("7+3=%d, 7-3=%d, 7*3=%d, 7/3=%d" % tuple(result)) The client call results into: python3 client.py 7+3=10, 7-3=4, 7*3=21, 7/3=2 This is missleading because '7/3' is now resulting to a float in python3 (see PEP238).The example probably was copied over from the python2 documentation where '7/3' result to int. The implicit conversion from float to int is done in the string formatting. Proposal replace the print line with print("7+3=%d, 7-3=%d, 7*3=%d, 7/3=%g" % tuple(result)) to get 7+3=10, 7-3=4, 7*3=21, 7/3=2.33333 or print(repr(tuple(result))) to get (10, 4, 21, 2.3333333333333335) ---------- assignee: docs@python components: Documentation messages: 191495 nosy: ber, docs@python priority: normal severity: normal status: open title: xmlrpc.client documentation multicall example missleading for division behaviour of python3 versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18267> _______________________________________

3 4

[issue18676] Queue: document that zero is accepted as timeout value
by Zhongyue Luo Aug. 7, 2013

Aug. 7, 2013

Changes by Zhongyue Luo <zhongyue.luo(a)gmail.com>: Added file: http://bugs.python.org/file31189/queue_timeout_docstring.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18676> _______________________________________

1 0

[issue18676] Queue: document that zero is accepted as timeout value
by Zhongyue Luo Aug. 7, 2013

Aug. 7, 2013

Changes by Zhongyue Luo <zhongyue.luo(a)gmail.com>: Added file: http://bugs.python.org/file31188/queue_timeout_docstring.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18676> _______________________________________

1 0

[issue18676] Queue: document that zero is accepted as timeout value
by Zhongyue Luo Aug. 7, 2013

Aug. 7, 2013

Changes by Zhongyue Luo <zhongyue.luo(a)gmail.com>: ---------- keywords: +patch Added file: http://bugs.python.org/file31187/queue_timeout_docstring.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18676> _______________________________________

1 0

[issue18676] Queue: document that zero is accepted as timeout value
by R. David Murray Aug. 7, 2013

Aug. 7, 2013

R. David Murray added the comment: Exactly. 0 means "Don't wait, just raise an error immediately if the queue is empty/full". ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18676> _______________________________________

1 0

[issue18676] Queue: document that zero is accepted as timeout value
by Richard Oudkerk Aug. 7, 2013

Aug. 7, 2013

Richard Oudkerk added the comment: > IMHO it just doesn't make sense passing 0.0 as a timeout value. I have written lots of code that looks like timeout = max(deadline - time.time(), 0) some_function(..., timeout=timeout) This makes perfect sense. Working code should not be broken -- it is the docsting that should be changed. I can't think of *any* function taking a timeout which rejects a zero timeout. See select(), poll(), Condition.wait(), Lock.acquire(), Thread.join(). In each case a zero timeout causes a non-blocking call. Also, note that the implementation does not contradict the docstring or documentation: they say nothing about what happens it timeout is zero (or negative). ---------- nosy: +sbt _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18676> _______________________________________

1 0

[issue18676] Queue: document that zero is accepted as timeout value
by Zhongyue Luo Aug. 7, 2013

Aug. 7, 2013

Zhongyue Luo added the comment: David, How about like below? elif timeout < sys.float_info.epsilon: raise ValueError("'timeout' must be a positive number") The docstring has been there for quite a while and IMHO it just doesn't make sense passing 0.0 as a timeout value. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18676> _______________________________________

1 0