Mailman 3 August 2014 - docs

[issue18588] timeit examples should be consistent
by Clay McClure Aug. 4, 2014

Aug. 4, 2014

New submission from Clay McClure: The timeit module documentation includes examples of command-line and programmatic invocation, but the results between the two sets of examples don't agree. This patch brings the results into agreement with each other. ---------- keywords: +patch Added file: http://bugs.python.org/file31076/18588.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18588> _______________________________________

6 8

Could the difference between a function and a macro be stressed in Python C API documentation?
by drekin Aug. 4, 2014

Aug. 4, 2014

Could the difference between a function and a macro be stressed in Python C API documentation? I wanted to call PyObject_CheckBuffer via ctypes, but ctypes.pythonapi.PyObject_CheckBuffer raised AttributeError. It took me some time to find out that it's because PyObject_CheckBuffer is a macro. Regards, Drekin

1 0

[issue20135] FAQ need list mutation answers
by Francis MB Aug. 3, 2014

Aug. 3, 2014

Francis MB added the comment: A) On the example: +Also note that some operations (e.g. ``y.append(10)``/``y += [10]`` or +``y.sort()``) mutate are you saying: 1) "y.append(10)" divided by "y += [10]" or 2) "y.append(10)" and "y += [10]" I don't want to split hairs but reading it fast confused me a bit B) The paragraph: + etc.), we can use some specific operations to mutate it and all the variables + that refer to it will see + the change; Couldn't be (one newline less): + etc.), we can use some specific operations to mutate it and all the variables + that refer to it will see the change; ---------- nosy: +francismb _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20135> _______________________________________

1 0

[issue20135] FAQ need list mutation answers
by Ezio Melotti Aug. 3, 2014

Aug. 3, 2014

Ezio Melotti added the comment: Here is a new patch that includes an additional paragraph about mutation and non-mutation operations. ---------- Added file: http://bugs.python.org/file36236/issue20135-2.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20135> _______________________________________

1 0

[issue22122] turtle module examples should all begin "from turtle import *"
by Mark Summerfield Aug. 3, 2014

Aug. 3, 2014

New submission from Mark Summerfield: The turtle module is aimed primarily at young beginners to Python. Making them type turtle.this and turtle.that all over the place is tedious and unhelpful. At the start of the turtle docs there's a nice example that begins from turtle import * and the following code is all the better for it. But none of the other examples do this. I realise that this would make the module's docs inconsistent, but given the target audience and given that we surely want to lower the barrier to entry, it would be a reasonable concession to make? ---------- assignee: docs@python components: Documentation messages: 224538 nosy: docs@python, mark priority: normal severity: normal status: open title: turtle module examples should all begin "from turtle import *" type: enhancement versions: Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22122> _______________________________________

3 3

float display in python 3.4
by Philippe Moreau Aug. 2, 2014

Aug. 2, 2014

Hi, I don't know if this is the good place for this metaphysic question...But, I read python docs in each version, but can't find the real answer. 2 days I'm on it :( Here is the question: In python docs 3.4 it is written: "Historically, the Python prompt and built-in repr() function would choose the one with 17 significant digits, 0.10000000000000001. Starting with Python 3.1, Python (on most systems) is now able to choose the shortest of these and simply display 0.1." The question is HOW python choose it? Here are examples I put in the shell: >>>0.1 Out[1]: 0.1 >>>0.2 Out[2]: 0.2 >>>0.3 Out[3]: 0.3 No problem here... Now: >>>0.1+0.2 Out[4]: 0.30000000000000004 The problem is NOT the number 4 that appears at the end. I know it deals with IEEE754 representation and that python displays the 17 first digits as tells in the doc. The problem is why it appears and why not for 0.2.... Let's see why it is a problem for me: >>>Decimal(0.1) Out[10]: Decimal('0.1000000000000000055511151231257827021181583404541015625') >>>Decimal(0.2) Out[11]: Decimal('0.200000000000000011102230246251565404236316680908203125') >>>Decimal(0.1+0.2) Out[12]: Decimal('0.3000000000000000444089209850062616169452667236328125') >>>Decimal(0.3) Out[13]: Decimal('0.299999999999999988897769753748434595763683319091796875') SO: the first 17 digits for 0.1 python's display are: 0.10000000000000000 so ok for 0.1 as display the first 17 digits for 0.1+0.2 python's display are: 0.30000000000000004 so, ok for the display. BUT: the first 17 digits for 0.2 python's display are: 0.20000000000000001 so, why just only 0.2 displayed? and the same for the 17 first digits for 0.3: 0.29999999999999998 so, why python only displayed 0.3? How python choose the correct display please? Thank you so much!!!!!!!!!! Philippe MOREAU

1 0

turtle speed does not work
by Tom O'Brien Aug. 1, 2014

Aug. 1, 2014

Hello In Python 2, an animation in turtle could be turned off, slowed down, or sped up with turtle.speed(). In python 3.4, this isn't the case. The documentation claims turtle.speed should work, but it doesn't change the speed of the animation. It doesn't give an error, but no matter the integer set inside turtle.speed, the speed won't change. Sent from my iPhone

1 1

[issue20466] Example in Doc/extending/embedding.rst fails to compile cleanly
by Zachary Ware Aug. 1, 2014

Aug. 1, 2014

New submission from Zachary Ware: Reported by Riccardo Rossi on docs@: The Very High Level Embedding example fails to compile cleanly, due to Py_SetProgramName expecting a wchar_t * argument, while the example passes a char *. ---------- assignee: docs@python components: Documentation messages: 209837 nosy: docs@python, zach.ware priority: normal severity: normal stage: needs patch status: open title: Example in Doc/extending/embedding.rst fails to compile cleanly type: behavior versions: Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20466> _______________________________________

2 2

[issue19055] Regular expressions: * does not match as many repetitions as possible.
by Serhiy Storchaka Aug. 1, 2014

Aug. 1, 2014

Serhiy Storchaka added the comment: I think this issue can be closed. Behavior and documentation are correct and match one other. Nothing to do with it. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19055> _______________________________________

1 0