Mailman 3 October 2018 - docs

[issue33729] Hashlib/blake2* missing 'data' keyword argument
by Ned Deily Oct. 7, 2018

Oct. 7, 2018

Ned Deily <nad(a)python.org> added the comment: The question remains if Christian's and Victor's concern with 3.7 compatibility have been satisfied by Serihy's response in msg322798. While there is plenty of time to resolve concerns about what was merged into master by PR 8346, we shouldn't release the PR 8581 changes in 3.7.1 if there are still valid compatibility concerns. Since PR 9657 for 3.6 hasn't been reviewed or merged, the only pressing issue for 3.6.7 is ensuring the segfault documented in Issue34922 is blocked, correct? And PR 8581 prevents the segfault for 3.7 so we would only need a similar fix for it if the PR were reverted, correct? ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue33729> _______________________________________

1 0

[issue33729] Hashlib/blake2* missing 'data' keyword argument
by Ned Deily Oct. 7, 2018

Oct. 7, 2018

Ned Deily <nad(a)python.org> added the comment: OK. This is now blocking the release of 3.7.1rc2 and 3.6.7rc2. See also Issue34922. ---------- priority: normal -> release blocker _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue33729> _______________________________________

1 0

[issue22232] str.splitlines splitting on non-\r\n characters
by Steven D'Aprano Oct. 7, 2018

Oct. 7, 2018

Steven D'Aprano <steve+python(a)pearwood.info> added the comment: I don't like the idea of adding a second bool parameter to splitlines. Guido has a rough rule of thumb (which I agree with) of "no constant bool parameters". If people will typically call a function with some sort of "mode" parameter using a hard-coded bool, then we should usually prefer to split the two modes into distinct functions. As an example, we have statistics.stdev and pstdev rather than stdev(data, population=False). Obviously this is a guideline, not a hard rule, and there are exceptions. Such as str.splitlines :-) In any case, I suggest a separate string method. Even though the name is slightly inaccurate, I suggest "ascii_splitlines" which I think is accurate enough to capture the spirit of what we intend (split on *only* \n \r and \r\n) and we can leave the details in the docs. ---------- nosy: +steven.daprano _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue22232> _______________________________________

1 0

[issue33729] Hashlib/blake2* missing 'data' keyword argument
by Christian Heimes Oct. 6, 2018

Oct. 6, 2018

Christian Heimes <lists(a)cheimes.de> added the comment: Ned, I'm currently travelling until next weekend. The PR is rather large and I don't have any means or time to review it properly. Perhaps Gregory or Dmitry Chestnykh (original author of pyblake2) are able to assist. ---------- nosy: +gregory.p.smith _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue33729> _______________________________________

1 0

[issue32174] nonASCII punctuation characters can not display in python363.chm.
by Steve Dower Oct. 6, 2018

Oct. 6, 2018

Steve Dower <steve.dower(a)python.org> added the comment: Until someone creates and enables a Sphinx extension/option to only generate ASCII output, it will remain. Volunteers are welcome ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue32174> _______________________________________

1 0

[issue34891] Multi-processing example inaccurate warning
by Anthony Flury Oct. 6, 2018

Oct. 6, 2018

New submission from Anthony Flury <anthony.flury(a)btinternet.com>: On the Multi-processing page <https://docs.python.org/3/library/multiprocessing.html> (just above the reference section) there is a warning that the examples wont work from the interpreter. This is not entirely accurate in that the examples do work, in the interpreter within Linux (and Mac OS I think), where the O/S supports processes being forked. In fact it is only in Windows, where a brand new process needs to be started and the source is effectively re-imported is there an issue running the examples in the interpreter. Should the documentation make this clearer ? ---------- assignee: docs@python components: Documentation messages: 327046 nosy: anthony-flury, docs@python priority: normal severity: normal status: open title: Multi-processing example inaccurate warning versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34891> _______________________________________

2 2

[issue29341] Missing accepting path-like object in docstrings of os module functions
by Vinodhini Oct. 6, 2018

Oct. 6, 2018

Vinodhini <me.vinob(a)gmail.com> added the comment: This is now carried forward in 3.8 also. Is anyone working on this issue ? It needs to be corrected in doc-string for all method where its applicable ---------- nosy: +Vinu2003 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue29341> _______________________________________

1 0

[issue33729] Hashlib/blake2* missing 'data' keyword argument
by Ned Deily Oct. 6, 2018

Oct. 6, 2018

Ned Deily <nad(a)python.org> added the comment: What's the status of this issue for 3.7 and for 3.6? Is everyone OK with what is currently in 3.7, i.e. no revert needed or has it already been reverted elsewhere? Also, there is the open PR for 3.6. ---------- nosy: +ned.deily _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue33729> _______________________________________

1 0

[issue22232] str.splitlines splitting on non-\r\n characters
by Neil Schemenauer Oct. 5, 2018

Oct. 5, 2018

Neil Schemenauer <nas-python(a)arctrix.com> added the comment: > Why not simply add a new parameter, to make people who want ASCII linebreaks continue to use .splitlines() ? That could work but I think in nearly every case you don't want to use splitlines() without supplying the parameter. So, it seems like a bit of trap for new users. Worse, because in Python 2, str.splitlines() does what they want, they will do the simple thing which is likely wrong. If we do stick with just splitlines(), perhaps it should get a 'newline' parameter that mostly matches io.open (i.e. it controls universal newline behavior). So if you don't want to change behavior, str.splitlines(newline=None) would split as it currently does. To make it split like io files do, you would have to do newline='\n'. To me, it seems attractive that: fp.readlines() == fp.read().iterlines() You suggestion would make it something like: fp.readlines() == fp.read().splitlines(newline='\n') I guess I could live with that but it seems unnecessarily ugly and verbose for what is the most common usage. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue22232> _______________________________________

1 0

[issue26005] Denial of Service in SimpleHTTPServer and BaseHTTPServer
by Felipe Rodrigues Oct. 5, 2018

Oct. 5, 2018

Change by Felipe Rodrigues <felipe(a)felipevr.com>: ---------- pull_requests: +9104 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue26005> _______________________________________

1 0