Mailman 3 April 2016 - docs

[issue25496] tarfile: Default value for compresslevel is not documented
by Zachary Ware April 12, 2016

April 12, 2016

Changes by Zachary Ware <zachary.ware(a)gmail.com>: ---------- hgrepos: -330 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25496> _______________________________________

1 0

[issue24557] Refactor LibreSSL / EGD detection
by SilentGhost April 12, 2016

April 12, 2016

Changes by SilentGhost <ghost.adh(a)runbox.com>: ---------- Removed message: http://bugs.python.org/msg263251 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24557> _______________________________________

1 0

[issue24557] Refactor LibreSSL / EGD detection
by Berker Peksag April 12, 2016

April 12, 2016

Changes by Berker Peksag <berker.peksag(a)gmail.com>: ---------- components: -2to3 (2.x to 3.x conversion tool), Argument Clinic, Benchmarks, Build, Cross-Build, Demos and Tools, Devguide, Distutils, Documentation, Extension Modules, IDLE, IO, Installation, Interpreter Core, Macintosh, Regular Expressions, Tests, Tkinter, Unicode, Windows, XML, asyncio, ctypes, email stage: -> patch review versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24557> _______________________________________

1 0

[issue24557] Refactor LibreSSL / EGD detection
by supriyanto maftuh,st April 12, 2016

April 12, 2016

supriyanto maftuh,st added the comment: Easy to review with issues phyton, maintenanca by supriyanto maftuh ---------- assignee: -> docs@python components: +2to3 (2.x to 3.x conversion tool), Argument Clinic, Benchmarks, Cross-Build, Demos and Tools, Devguide, Distutils, Documentation, Extension Modules, IDLE, IO, Installation, Interpreter Core, Macintosh, Regular Expressions, Tests, Tkinter, Unicode, Windows, XML, asyncio, ctypes, email hgrepos: +337 nosy: +Alex.Willmer, barry, brett.cannon, docs@python, dstufft, eric.araujo, ezio.melotti, gvanrossum, haypo, larry, mrabarnett, ned.deily, paul.moore, pitrou, r.david.murray, ronaldoussoren, steve.dower, supriyanto maftuh, supriyanto maftuh,st, tim.golden, willingc, yselivanov, zach.ware versions: +Python 3.2, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24557> _______________________________________

1 0

[issue20699] Document that binary IO classes work with bytes-likes objects
by Martin Panter April 12, 2016

April 12, 2016

Martin Panter added the comment: After thinking about Issue 26720 (see also Issue 15994), I think it might be worth documenting not only that bytes-like objects may be passed, but in some cases the class should not be access the object after the method returns. This applies to at least RawIOBase.readinto() and especially RawIOBase.write(). If you want to save the write() data in memory, you have to make a copy, because the original may be lost when BufferedWriter overwrites its internal buffeer. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20699> _______________________________________

1 0

possible doc bug: 6.2.1. Regular Expression Syntax, *?, +?, ??
by John Gordon April 12, 2016

April 12, 2016

I'm a Python newbie and am very reluctant to submit a doc bug since I don't know what I'm doing yet. But I'm trying to learn to use re.search and am using your doc. I can't figure out how the text I colored red below can be accurate. Besides its logic not making sense to me, I tried running it and it doesn't work: .*? doesn't match <H1> . If I'm wrong I need to understand why. ============ DOC BUG (maybe): https://docs.python.org/3/library/re.html 6.2.1. Regular Expression Syntax > > > **?, +?, ?? *The '*', '+', and '?' qualifiers are all greedy; they match > as much text as possible. Sometimes this behaviour isn’t desired; if the RE > <.*> is matched against '<H1>title</H1>', it will match the entire string, > and not just '<H1>'. Adding '?' after the qualifier makes it perform the > match in non-greedy or minimal fashion; as few characters as possible will > be matched. *Using .*? in the previous expression will match only '<H1>'.* > > I tried the following and none returned <H1>: >>> ttt = re.search('.*?','<H1>title</H1>') >>> ttt = re.search('(.*?)','<H1>title</H1>') >>> ttt = re.search(r'(.*?)','<H1>title</H1>') Thank you for your time! John Gordon

2 1

Fwd: possible doc bug: 6.2.1. Regular Expression Syntax, *?, +?, ??
by John Gordon April 12, 2016

April 12, 2016

Never mind. I figured it out. I see that the last sentence about using .*? is meant to be used inside the RE <.*> mentioned in the second sentence. Confusing but another website explained it then I reread your paragraph and understood what you meant. - John Gordon ---------- Forwarded message ---------- From: John Gordon <john23gordon(a)gmail.com> Date: Mon, Apr 11, 2016 at 12:34 PM Subject: possible doc bug: 6.2.1. Regular Expression Syntax, *?, +?, ?? To: docs(a)python.org I'm a Python newbie and am very reluctant to submit a doc bug since I don't know what I'm doing yet. But I'm trying to learn to use re.search and am using your doc. I can't figure out how the text I colored red below can be accurate. Besides its logic not making sense to me, I tried running it and it doesn't work: .*? doesn't match <H1> . If I'm wrong I need to understand why. ============ DOC BUG (maybe): https://docs.python.org/3/library/re.html 6.2.1. Regular Expression Syntax > > > **?, +?, ?? *The '*', '+', and '?' qualifiers are all greedy; they match > as much text as possible. Sometimes this behaviour isn’t desired; if the RE > <.*> is matched against '<H1>title</H1>', it will match the entire string, > and not just '<H1>'. Adding '?' after the qualifier makes it perform the > match in non-greedy or minimal fashion; as few characters as possible will > be matched. *Using .*? in the previous expression will match only '<H1>'.* > > I tried the following and none returned <H1>: >>> ttt = re.search('.*?','<H1>title</H1>') >>> ttt = re.search('(.*?)','<H1>title</H1>') >>> ttt = re.search(r'(.*?)','<H1>title</H1>') Thank you for your time! John Gordon

1 0

[issue11205] Evaluation order of dictionary display is different from reference manual.
by Nick Coghlan April 12, 2016

April 12, 2016

Nick Coghlan added the comment: Temporarily reopening this as a docs bug - I think it's worth mentioning in the "Porting to Python 3.5" section of the What's New docs and as a "version changed" note in the dis module docs, as even though it's obscure, anyone that was inadvertently relying on the prior deviation from the spec is going to be confused by the behavioural change in 3.5. (The specific case where this came up was Russell Keith-Magee encountering the semantic change in BUILD_MAP's expectations for argument order on the stack for his VOD bytecode transpiler) ---------- assignee: -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python priority: high -> normal resolution: fixed -> stage: resolved -> needs patch status: closed -> open versions: +Python 3.5 -Python 2.7, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11205> _______________________________________

1 0

'namereplace'
by Freely-Given.org April 11, 2016

April 11, 2016

https://docs.python.org/3/library/functions.html doesn't warn that 'namereplace' was new in Python 3.5 (it seems). Thanks, Robert.

2 1

A typo in the unittest.mock docs
by Alex April 11, 2016

April 11, 2016

https://docs.python.org/3/library/unittest.mock.html#magic-mock ... > Methods and their defaults: > ... > __len__:1 > ... Should be __len__:0

2 1