Mailman 3 October 2016 - docs

[issue2897] Deprecate structmember.h
by Berker Peksag 04 Oct '16

04 Oct '16

Changes by Berker Peksag <berker.peksag(a)gmail.com>: ---------- nosy: +berker.peksag stage: -> patch review _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue2897> _______________________________________

1 0

Re: [docs] Suggest PyCharm Community as an editor for Unix platforms (issue 26149)
by berker.peksag＠gmail.com 04 Oct '16

04 Oct '16

http://bugs.python.org/review/26149/diff/18598/Doc/using/unix.rst File Doc/using/unix.rst (right): http://bugs.python.org/review/26149/diff/18598/Doc/using/unix.rst#newcode141 Doc/using/unix.rst:141: Please go to https://wiki.python.org/moin/PythonEditors and We don't usually add raw URLs to prose in Python documentation. It would be nice to convert them to named URLs: Spam `eggs <https://www.python.org/eggs/>`_ instead of Spam https://www.python.org/eggs/ http://bugs.python.org/review/26149/

1 0

[issue2897] Deprecate structmember.h
by Alexander Belopolsky 03 Oct '16

03 Oct '16

Alexander Belopolsky added the comment: Changed the title to reflect the way forward and added affected versions to remember to update the documentation. See #28349 and #24065 for details. ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python title: include structmember.h in Python.h -> Deprecate structmember.h versions: +Python 2.7, Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue2897> _______________________________________

1 0

[issue28349] Issues with PyMemberDef flags
by Serhiy Storchaka 03 Oct '16

03 Oct '16

New submission from Serhiy Storchaka: As documented in Doc/extending/newtypes.rst, the flags field of PyMemberDef must be bitwise-or-ed combination of flag constants READONLY, READ_RESTRICTED, WRITE_RESTRICTED and RESTRICTED. There are problems with this: 1. Actually WRITE_RESTRICTED was renamed to PY_WRITE_RESTRICTED in 2.6 (a8dd8874ff2d). I didn't find mention of this backward incompatible change in Misc/NEWS and whatsnew files. 2. Since the support of restricted mode was removed in 3.x, only READONLY flag has effect. Other flags are still documented and used in CPython sources. I think we should get rid of using these flags and undocument them or document as outdated. 3. As noted by Skip Montanaro on the Python-Dev mailing list, these flags (as well as T_* type tags in Include/structmember.h) should have the PY_ prefix. ---------- assignee: docs@python components: Documentation messages: 277972 nosy: christian.heimes, docs@python, serhiy.storchaka, skip.montanaro priority: normal severity: normal status: open title: Issues with PyMemberDef flags versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28349> _______________________________________

2 6

[issue16399] argparse: append action with default list adds to list instead of overriding
by paul j3 02 Oct '16

02 Oct '16

paul j3 added the comment: One thing that this default behavior does is allow us to append values to any object, just so long as it has the `append` method. The default does not have to be a standard list. For example, in another bug/issue someone asked for an `extend` action. I could provide that with `append` and a custom list class class MyList(list): def append(self,arg): if isinstance(arg,list): self.extend(arg) else: super(MyList, self).append(arg) This just modifies `append` so that it behaves like `extend` when given a list argument. parser = argparse.ArgumentParser() a = parser.add_argument('-f', action='append', nargs='*',default=[]) args = parser.parse_args('-f 1 2 3 -f 4 5'.split()) produces a nested list: In [155]: args Out[155]: Namespace(f=[['1', '2', '3'], ['4', '5']]) but if I change the `default`: a.default = MyList([]) args = parser.parse_args('-f 1 2 3 -f 4 5'.split()) produces a flat list: In [159]: args Out[159]: Namespace(f=['1', '2', '3', '4', '5']) I've tested this idea with an `array.array` and `set` subclass. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16399> _______________________________________

1 0

[issue16399] argparse: append action with default list adds to list instead of overriding
by paul j3 02 Oct '16

02 Oct '16

paul j3 added the comment: It may help to know something about how defaults are handled - in general. `add_argument` and `set_defaults` set the `default` attribute of the Action (the object created by `add_argument` to hold all of its information). The default `default` is `None`. At the start of `parse_args`, a fresh Namespace is created, and all defaults are loaded into it (I'm ignoring some details). The argument strings are then parsed, and individual Actions update the Namespace with their values, via their `__call__` method. At the end of parsing it reviews the Namespace. Any remaining defaults that are strings are evaluated (passed through `type` function that converts a commandline string). The handling of defaults threads a fine line between giving you maximum power, and keeping things simple and predictable. The important thing for this issue is that the defaults are loaded into the Namespace at the start of parsing. The `append` call fetches the value from the Namespace, replaces it with `[]` if it is None, appends the new value(s), and puts it back on the Namespace. The first `--foo` append is handled in just the same way as the 2nd and third (fetch, append, and put back). The first can't tell that the list it fetches from the namespace came from the `default` as opposed to a previous `append`. The `__call__` for `append` was intentionally kept simple, and predictable. As I demonstrated earlier it is possible to write an `append` that checks the namespace value against some default, and does something different. But that is more complicated. The simplest alternative to this behavior is to leave the default as None. If after parsing the value is still None, put the desired list (or any other object) there. The primary purpose of the parser is to parse the commandline - to figure out what the user wants to tell you. There's nothing wrong with tweaking (and checking) the `args` Namespace after parsing. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16399> _______________________________________

1 0

[issue8145] Documentation about sqlite3 isolation_level
by Mariatta Wijaya 02 Oct '16

02 Oct '16

Changes by Mariatta Wijaya <mariatta.wijaya(a)gmail.com>: ---------- nosy: +Mariatta _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8145> _______________________________________

1 0

[issue16399] argparse: append action with default list adds to list instead of overriding
by Michał Klich 02 Oct '16

02 Oct '16

Michał Klich added the comment: The documentation for argparse still does not mention this behaviour. I decided to make a patch based no the optparse issue. Hopefully it is good enough to be merged. ---------- keywords: +patch nosy: +michal.klich Added file: http://bugs.python.org/file44934/append_to_default.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16399> _______________________________________

1 0

[issue28089] Document TCP_NODELAY by default
by Mariatta Wijaya 01 Oct '16

01 Oct '16

Changes by Mariatta Wijaya <mariatta.wijaya(a)gmail.com>: ---------- nosy: +Mariatta _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28089> _______________________________________

1 0

[issue28088] Document Transport.set_protocol and get_protocol
by Mariatta Wijaya 01 Oct '16

01 Oct '16

Changes by Mariatta Wijaya <mariatta.wijaya(a)gmail.com>: ---------- nosy: +Mariatta _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28088> _______________________________________

1 0