Mailman 3 December 2016 - docs

[issue28771] Update documented signatures of tp_get/setattr
by Martin Panter Dec. 10, 2016

Dec. 10, 2016

New submission from Martin Panter: https://docs.python.org/3.7/c-api/typeobj.html#c.PyTypeObject.tp_getattr tp_getattr and tp_setattr take a non-const char pointer in their signatures, but the documentation points to PyObject_GetAttrString() etc which were changed to take const char pointers a long time ago: revision 2f19b981ac24. This patch fixes the documentation of those two methods for Python 3. There could be more fixes needed for Python 2. ---------- assignee: docs@python components: Documentation files: typeobj-sigs.patch keywords: patch messages: 281468 nosy: docs@python, martin.panter priority: normal severity: normal stage: patch review status: open title: Update documented signatures of tp_get/setattr versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 Added file: http://bugs.python.org/file45600/typeobj-sigs.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28771> _______________________________________

3 6

[issue28755] Rework syntax highlighing in howto/clinic.rst
by Julien Palard Dec. 10, 2016

Dec. 10, 2016

New submission from Julien Palard: I was reading `howto/clinic.html` and though I'll fix syntax highlighting. ---------- assignee: docs@python components: Argument Clinic, Documentation messages: 281304 nosy: docs@python, larry, mdk priority: normal severity: normal status: open title: Rework syntax highlighing in howto/clinic.rst versions: Python 2.7, Python 3.6, Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28755> _______________________________________

4 8

[issue26483] docs unclear on difference between str.isdigit() and str.isdecimal()
by Martin Panter Dec. 10, 2016

Dec. 10, 2016

Martin Panter added the comment: I’m okay with this version unless anyone has any more improvements. ---------- stage: patch review -> commit review _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26483> _______________________________________

1 0

[issue1446619] extended slice behavior inconsistent with docs
by Martin Panter Dec. 10, 2016

Dec. 10, 2016

Martin Panter added the comment: Patch ruling out the len(s) corner case. I use a modified version of Fumihiro’s suggestion. ---------- versions: +Python 3.6, Python 3.7 -Python 3.4 Added file: http://bugs.python.org/file45827/extended_slicing_docs.v2.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue1446619> _______________________________________

1 0

[issue28753] Clinic: Converting Your First Function is not up to date
by Roundup Robot Dec. 10, 2016

Dec. 10, 2016

Roundup Robot added the comment: New changeset 7a93d1a0a1cf by Martin Panter in branch '3.5': Issue 28753: Argument Clinic howto docfix, courtesy Julien Palard. https://hg.python.org/cpython/rev/7a93d1a0a1cf New changeset d0859a11322c by Martin Panter in branch '3.6': Issues #28755, #28753: Merge Arg Clinic howto from 3.5 https://hg.python.org/cpython/rev/d0859a11322c ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28753> _______________________________________

1 0

[issue28424] pkgutil.get_data() doesn't work with namespace packages
by Douglas Greiman Dec. 10, 2016

Dec. 10, 2016

Douglas Greiman added the comment: Patch attached. Feel free to wordsmith. ---------- keywords: +patch Added file: http://bugs.python.org/file45825/issue28424.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28424> _______________________________________

1 0

[issue28882] Slice confusing with negative stop and strides and the 0th element.
by Martin Panter Dec. 10, 2016

Dec. 10, 2016

Martin Panter added the comment: See also Issue 11842 about the behaviour of slice.indices() in this situation, and Issue 1446619 about fixing the documentation for reverse slices regarding positive out-of-range indexes. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28882> _______________________________________

1 0

[issue1446619] extended slice behavior inconsistent with docs
by Martin Panter Dec. 10, 2016

Dec. 10, 2016

Martin Panter added the comment: Fumihiro’s suggestion seems reasonable to me (assuming it still applies to the current text) ---------- nosy: +martin.panter _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue1446619> _______________________________________

1 0

[issue28882] Slice confusing with negative stop and strides and the 0th element.
by Martin Panter Dec. 9, 2016

Dec. 9, 2016

Martin Panter added the comment: I think Steven’s main complaint is that it is hard to make a reversed slice extend to the start of the original sequence, unless you omit (or use None as) the endpoint: >>> "01234567"[4:0:-1] # Includes index [4], stops before reaching index [0] '4321' >>> "01234567"[3::-1] # Includes index [3], stop omitted for start of string '3210' >>> "01234567"[3:None:-1] # None means the same '3210' >>> "01234567"[3:-1:-1] # Negative means len(...) - 1, i.e. index [7] '' This is a consequence of (a) the stop parameter meaning “stop _before_ reaching this index”, and (b) negative indexes are interpreted specially as being relative to the end. ---------- nosy: +martin.panter _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28882> _______________________________________

1 0

[issue28882] Slice confusing with negative stop and strides and the 0th element.
by Terry J. Reedy Dec. 9, 2016

Dec. 9, 2016

Terry J. Reedy added the comment: Steven, your initial 'sentence' is missing something needed to make it a proper English sentence, and I cannot exactly guess what you meant. But your later confusion is clear enough. This tracker is for patching the Python docs and CPython code. I believe the entry for the slice function/class, https://docs.python.org/3/library/functions.html#slice, could be improved. First the word 'slice' is linked to the Glossary entry for 'slice'. However, the latter is about subsequences, not about slice objects. It should instead link to the entry that contains the method description as https://docs.python.org/3/reference/datamodel.html#slice.indices. (This is the target for the Index entry 'indices (slice method)'. The 'slick objects' label needs to be made a target. Second, the description "representing the set of indices specified by range(start, stop, step)" is only true when start and stop are valid non-negative indexes when applied to a particular sequence. It is never true for negative values and not true when greater to or equal to the length of a particular sequence. As the slice.indices entry says, 'Missing or out-of-bounds indices are handled in a manner consistent with regular slices." In the example above, the issue is the negative stop, not the negative step. Steven's problem was expecting the description to be true (whether or not he read it.) It is worth noting, nowever, that reversed() was added because people had trouble using negative steps. The following is much clearer than the corrected code above that the object is to separately reverse two haves of a list. >>> n = 8 >>> a = range(8) >>> [list(reversed(a[:n//2])), list(reversed(a[n//2:]))] [[3, 2, 1, 0], [7, 6, 5, 4]] As the Library Function entry hints, slice() is mainly intended for use internally and by 3rd-party extensions. The description is even more wrong because the three arguments/attributes 'can have any type' (from the Data model slice object entry) whereas range arguments must be int-like. (Allowing non-int-like arguments is for external extension use.) In particular, slice(None) == slice(None, None) == slice(None, None, None) 'represents' all the indices of a particular sequence, in normal order, whereas None is not a valid argument for range(). I am not sure what replacement to propose. I'd like to see if there is any previous discussion on the tracker. A third and minor issue is that 'Numerical Python' should? be updated to "Numpy'. ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python, terry.reedy stage: -> needs patch title: RFC: Slice confusing with negative strides and the 0th element. -> Slice confusing with negative stop and strides and the 0th element. type: behavior -> versions: +Python 3.6, Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28882> _______________________________________

1 0