Mailman 3 May 2016 - docs

[issue26889] Improve Doc/library/xmlrpc.client.rst
by Serhiy Storchaka May 6, 2016

May 6, 2016

Serhiy Storchaka added the comment: Thank you for your review Terry. Updated patch addresses most of your comments. But I'm unable to expand ServerProxy description as you suggest. May you can do this? My purpose was modest. Just fix some incorrect and outdated sentences. Then I fixed some formatting. I was not going and is not able to do anything besides this. I will take all that you offer. ---------- Added file: http://bugs.python.org/file42763/docs_xmlrpc_client_2.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26889> _______________________________________

1 0

Re: [docs] Improve Doc/library/xmlrpc.client.rst (issue 26889)
by storchaka＠gmail.com May 6, 2016

May 6, 2016

https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… File Doc/library/xmlrpc.client.rst (right): https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… Doc/library/xmlrpc.client.rst:17: XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP as a On 2016/05/06 20:36:41, terry.reedy wrote: > HTTP(S) better? Done. Or may be HTTP/HTTPS? https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… Doc/library/xmlrpc.client.rst:49: On 2016/05/06 20:36:41, terry.reedy wrote: > New blank line separates instance construction parameters above from instance > use parameters. Good. I think you could even something like "The following > parameters govern the use of the returned proxy instance." Done. https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… Doc/library/xmlrpc.client.rst:53: all clients and servers; see http://ontosys.com/xml-rpc/extensions.php for a On 2016/05/06 20:36:41, terry.reedy wrote: > New link displays page with "Wayback Machine doesn't have that page archived." > Is any more description really needed? Can you just incorporate it? > Rietveld included closing parenthesis in the link. Correct link: https://web.archive.org/web/20130120074804/http://ontosys.com/xml-rpc/exten… All resources (including Wikipedia) refer to this link. There is no more "official" document. Apache provided longer list of extension types (see issue26885), but this project is half-dead too. https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… Doc/library/xmlrpc.client.rst:76: On 2016/05/06 20:36:41, terry.reedy wrote: > Not sure that deletion of sentence is an improvement. See tracker post. This sentence just looks tautological or wrong to me. In Python 3 there is no difference between types and classes (I suppose user-defined classic classes were meant here). ServerProxy instance methods can't take or return types. They work with instances of specific types. And if we left just "Python objects", what other this can be? In Python everything is an object, and every value is a Python object. I was unable to reformulate this sentence correctly and preferred to remove it. https://bugs.python.org/review/26889/

1 0

[issue26889] Improve Doc/library/xmlrpc.client.rst
by Terry J. Reedy May 6, 2016

May 6, 2016

Terry J. Reedy added the comment: This is my first reading of this doc. The formatting improvements look good. A definite enhancement. Review contains a few comments. My main difficulty is separating creation of a proxy instance from use of a proxy instance. Some of the creation parameters govern the use, and hence do not make must sense until one reads the instance description a few paragraphs further on. Perhaps the initial sentence "A :class:`ServerProxy` instance is an object that manages communication with aremote XML-RPC server." should be expanded into a paragraph with some of the description given later. ---------- nosy: +terry.reedy _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26889> _______________________________________

1 0

Re: [docs] Improve Doc/library/xmlrpc.client.rst (issue 26889)
by tjreedy＠udel.edu May 6, 2016

May 6, 2016

https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… File Doc/library/xmlrpc.client.rst (right): https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… Doc/library/xmlrpc.client.rst:17: XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP as a HTTP(S) better? https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… Doc/library/xmlrpc.client.rst:49: New blank line separates instance construction parameters above from instance use parameters. Good. I think you could even something like "The following parameters govern the use of the returned proxy instance." https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… Doc/library/xmlrpc.client.rst:53: all clients and servers; see http://ontosys.com/xml-rpc/extensions.php for a New link displays page with "Wayback Machine doesn't have that page archived." Is any more description really needed? Can you just incorporate it? https://bugs.python.org/review/26889/diff/17111/Doc/library/xmlrpc.client.r… Doc/library/xmlrpc.client.rst:76: Not sure that deletion of sentence is an improvement. See tracker post. https://bugs.python.org/review/26889/

1 0

[issue18841] math.isfinite fails with Decimal sNAN
by Steven D'Aprano May 6, 2016

May 6, 2016

New submission from Steven D'Aprano: math.isfinite currently raises ValueError when given a Decimal sNAN (signalling NAN). I've run into a situation where I'm calling isfinite() on a numeric value which may be a Decimal sNAN, and it would be nice if it returned False. On the other hand, see the discussion on issue 15544, which possibly leads to the conclusion that raising ValueError is the right thing to do. http://bugs.python.org/issue15544 Either way, behaviour should be documented. ---------- assignee: docs@python components: Documentation, Library (Lib) messages: 196213 nosy: docs@python, stevenjd priority: normal severity: normal status: open title: math.isfinite fails with Decimal sNAN type: behavior versions: Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18841> _______________________________________

6 5

[issue26962] curses documenation- keys for Page Up and Page Down are reversed
by Nathan Kerr May 5, 2016

May 5, 2016

New submission from Nathan Kerr: In the documentation for the curses module- 15.11 in Python 2.7 (https://docs.python.org/2.7/library/curses.html), the given key values for Page Up and Page Down are "KEY_NPAGE" and "KEY_PPAGE" respectively. These should be reversed. This has been fixed in the documentation for 3.5 and 3.6 but not in the previous versions. See this bug report: http://bugs.python.org/issue26679 ---------- assignee: docs@python components: Documentation messages: 264884 nosy: docs@python, nkerr priority: normal severity: normal status: open title: curses documenation- keys for Page Up and Page Down are reversed type: behavior versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26962> _______________________________________

3 3

[issue26957] Docs: remove duplicate "the" in description of `%z` in datetime docs
by Alex Chan May 4, 2016

May 4, 2016

New submission from Alex Chan: The description of the `%z` format code in the datetime docs reads: > UTC offset in the form +HHMM or -HHMM (empty string if the the object is naive). This tiny patch removes the second "the". The current wording goes at least as far back as Python 2.6; see https://docs.python.org/2.6/library/datetime.html?highlight=datetime#strfti…. ---------- assignee: docs@python components: Documentation files: oneword.patch keywords: patch messages: 264848 nosy: alexwlchan, docs@python priority: normal severity: normal status: open title: Docs: remove duplicate "the" in description of `%z` in datetime docs type: enhancement Added file: http://bugs.python.org/file42719/oneword.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26957> _______________________________________

3 2

[issue26951] Unintuitive error when using generator expression in class property
by Mark Dickinson May 4, 2016

May 4, 2016

Mark Dickinson added the comment: The outer for loop in a generator expression is evaluated immediately; everything after that is evaluated lazily. This was a deliberate design choice: see https://www.python.org/dev/peps/pep-0289/#early-binding-versus-late-binding for some rationale. This explains why you're able to access "B". The inability to access "C" is due to the usual rule for Python scope resolution: class scopes are skipped when examining nested scopes. The early evaluation of the outermost for is covered in the docs, here: https://docs.python.org/2/reference/expressions.html#generator-expressions """ However, the leftmost for clause is immediately evaluated, so that an error produced by it can be seen before any other possible error in the code that handles the generator expression. """ So this behaviour is by design, though there may be a doc issue here. Changing components and versions accordingly. ---------- assignee: -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python, mark.dickinson versions: +Python 3.6 -Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26951> _______________________________________

1 0

[issue26696] Document collections.abc.ByteString
by Brett Cannon May 4, 2016

May 4, 2016

Changes by Brett Cannon <brett(a)python.org>: ---------- assignee: docs@python -> brett.cannon _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26696> _______________________________________

1 0

[issue26950] Typo in unittest.mock > Autospeccing documentation
by Joni Bekenstein May 4, 2016

May 4, 2016

New submission from Joni Bekenstein: In several code examples from unittest.mock > Autospeccing documentation you will find "assret_called_with" instead of "assert_called_with". ---------- assignee: docs@python components: Documentation messages: 264815 nosy: Joni Bekenstein, docs@python priority: normal severity: normal status: open title: Typo in unittest.mock > Autospeccing documentation type: enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue26950> _______________________________________

2 2