Mailman 3 August 2014 - docs

property doc fixes (issue 22174)
by ezio.melotti＠gmail.com Aug. 10, 2014

Aug. 10, 2014

http://bugs.python.org/review/22174/diff/12675/Doc/library/functions.rst File Doc/library/functions.rst (right): http://bugs.python.org/review/22174/diff/12675/Doc/library/functions.rst#ne… Doc/library/functions.rst:1111: value. And *doc* creates a docstring for the attribute. Having 3 small and similar sentences separated by a full stop doesn't sound too well to me, and neither does starting the last with "And". What about: """ *fget*, *fset*, and *fdel* are functions used respectively to get, set, and delete an attribute value. *doc* is used to define the docstring of the attribute. """ http://bugs.python.org/review/22174/

1 0

Found repeated content
by tcstory Aug. 10, 2014

Aug. 10, 2014

In page https://docs.python.org/3/library/socket.html?highlight=socket#module-socket the repeated content is "If addr_type is TIPC_ADDR_ID, then v1 is the node, v2 is the reference, and v3 should be set to 0."

1 0

[issue22170] Typo in iterator doc
by Susan Tan Aug. 8, 2014

Aug. 8, 2014

New submission from Susan Tan: Typo in last line: for line in open("myfile.txt"): print line, Instead there should be no extra "," character in "print line," ---------- assignee: docs@python components: Documentation messages: 225056 nosy: Susan, docs@python priority: normal severity: normal status: open title: Typo in iterator doc type: enhancement versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22170> _______________________________________

5 5

[issue15428] add "Name Collision" section to argparse docs
by Steven Bethard Aug. 7, 2014

Aug. 7, 2014

New submission from Steven Bethard <steven.bethard(a)gmail.com>: Several bugs (e.g. Issue 15327 and Issue 15271) have been filed suggesting that people aren't really clear on how argparse handles argument name collisions or how they can get it to do what they want. I think these problems could probably be solved by a "Name Collision" section (or something like that) in the argparse documentation. It would give a few example problems and show how to resolve them. Some things to include: * What happens when two arguments have the same dest (Issue 15271), with solutions including action='append' or different dest= values combined with identical metavar= values. * What happens when a parser and a sub-parser share some of the same argument names (Issue 15327), with solutions including specifying different dest= values for the parser and sub-parser * A brief mention and cross-reference to the "conflict_handler" section. ---------- assignee: docs@python components: Documentation messages: 166185 nosy: bethard, docs@python priority: normal severity: normal status: open title: add "Name Collision" section to argparse docs versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15428> _______________________________________

3 3

[issue22162] Actiavting a venv - Dash doesn't understand source
by Daniel Lintott Aug. 7, 2014

Aug. 7, 2014

New submission from Daniel Lintott: In the documentation for venv (https://docs.python.org/3.5/library/venv.html) it gives examples for activating the venv under bash/zsh. For a long time under both Debian and Ubuntu the default shell has been Dash (https://wiki.ubuntu.com/DashAsBinSh) Dash doesn't undertsand the command 'source' so instead the venv must be activated using the . command (as is done for Fish, but using the bash activate file instead) ---------- assignee: docs@python components: Documentation messages: 225001 nosy: dlintott, docs@python priority: normal severity: normal status: open title: Actiavting a venv - Dash doesn't understand source type: enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22162> _______________________________________

4 6

[issue22142] PEP 465 operators not described in lexical_analysis
by Roundup Robot Aug. 7, 2014

Aug. 7, 2014

Roundup Robot added the comment: New changeset 0bc58b4c0562 by Benjamin Peterson in branch 'default': add matrix multiplication operator to correct lists (closes #22142) http://hg.python.org/cpython/rev/0bc58b4c0562 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22142> _______________________________________

1 0

[issue16399] argparse: append action with default list adds to list instead of overriding
by paul j3 Aug. 6, 2014

Aug. 6, 2014

paul j3 added the comment: In my suggestion I used if 'current_value is default': without going into detail. The use of an 'is' test for integer values is tricky, as discussed in http://bugs.python.org/issue18943 int("42") is 42 # True int("257") is 257 # False As with your 'self.reset_dest', in 18943 I suggested using a boolean flag instead of the 'is' test. ---------- _______________________________________ 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 Yclept Nemo Aug. 6, 2014

Aug. 6, 2014

Yclept Nemo added the comment: Well that won't work. Example: import argparse class TestAction(argparse.Action): def __call__(self, parser, namespace, values, option_string=None): print("default: {}({})\tdest: {}({})".format(self.default, type(self.default), getattr(namespace, self.dest), type(getattr(namespace, self.dest)))) if getattr(namespace, self.dest) is self.default: print("Replacing with: ", values) setattr(namespace, self.dest, values) # extra logical code not necessary for testcase parser = argparse.ArgumentParser() parser.add_argument\ ( "-o", "--output" , type=int , action=TestAction , default=42 ) args = parser.parse_args() $ ./argparse_test -o 42 -o 100 default: 42(<class 'int'>) dest: 42(<class 'int'>) Replacing with: 42 default: 42(<class 'int'>) dest: 42(<class 'int'>) Replacing with: 100 100 Use this approach: class ExtendAction(argparse.Action): def __init__(self, *args, **kwargs): super().__init__(*args, **kwargs) if not isinstance(self.default, collections.abc.Iterable): self.default = [self.default] self.reset_dest = False def __call__(self, parser, namespace, values, option_string=None): if not self.reset_dest: setattr(namespace, self.dest, []) self.reset_dest = True getattr(namespace, self.dest).extend(values) Anyway, this should be properly documented... ---------- nosy: +Yclept.Nemo _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16399> _______________________________________

1 0

asyncio: example for shield and readexactly
by Dietmar Schwertberger Aug. 6, 2014

Aug. 6, 2014

Hi! I've recently started using asyncio. My usage includes code which reads two bytes, but with a timeout. My naive approach was: rx = yield from asyncio.wait_for( reader.readexactly(2), 2.0) But of course this does not work as it could lose a byte if exactly one byte hasbeen received when the timeout was met. For asyncio beginners it's not obvious how to fix that and especially how to use shield(). My code now looks something like that: readexactly_task = None while True: try: if readexactly_task is None: # create a task to receive two bytes readexactly_task = asyncio.Task( reader.readexactly(2) ) # give the task two seconds to complete # shield it not to be canceled on timeout rx = yield from asyncio.wait_for( asyncio.shield(readexactly_task), 2.0) readexactly_task = None # task has finished if not rx: break # EOF met except asyncio.TimeoutError: # asyncio.wait_for was canceled # the task readexactly_task is still alive rx = None if rx: # process the received bytes print(rx) I think that it would be helpful to have such an example in the documentation for both StreamReader and shield. Of course, if readexactly had an argument 'timeout' things would have been easier... Regards, Dietmar

1 0

[issue22154] ZipFile.open context manager support
by Serhiy Storchaka Aug. 6, 2014

Aug. 6, 2014

Serhiy Storchaka added the comment: May be. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) keywords: +easy nosy: +docs@python priority: normal -> low resolution: out of date -> stage: resolved -> needs patch status: closed -> open type: enhancement -> behavior _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22154> _______________________________________

1 0