Mailman 3 October 2015 - docs

[issue25501] Use async/await through asyncio docs
by Brett Cannon 29 Oct '15

29 Oct '15

New submission from Brett Cannon: The asyncio docs still use `yield from` and @asyncio.coroutine all over the place instead of async/await. It would be best to update the docs to follow best practices (unless there is some reason I can't think of as to why this hasn't happened yet). ---------- assignee: docs@python components: Documentation messages: 253636 nosy: brett.cannon, docs@python, giampaolo.rodola, gvanrossum, haypo, pitrou, yselivanov priority: normal severity: normal stage: needs patch status: open title: Use async/await through asyncio docs versions: Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25501> _______________________________________

4 7

[issue24778] mailcap.findmatch: document shell command Injection danger in filename parameter
by Bernd Dietzel 29 Oct '15

29 Oct '15

Bernd Dietzel added the comment: My patch for mailcap.py. Please check and apply my patch please. 1) I have removed the os.system() calls for security reasons. 2) New "findmtach_list()" function witch returns the commandline as a [list] witch can be passed to subprocess instead of passing it to os.system(). 3) New run() function to execute the cmd_list with subprocess. 4) The test() function now uses findmatch_list() and run() instead of the old findmatch() and os.system() calls. 5) The subst() function is now shorter an does a quote(filename) when its replacing %s with a filename. 6) The "old" findmatch() function is still there if the user still likes to have the commandline as a "string". Attention ! With this old findmatch() function it's still possible that a shell command in the filename like '$(ls).txt' will be executed when the users passes the string to os.system() outside the mailcap script. Use findmatch() only for backwards compatibility. 7) Use the new findmatch_list() an run() for future projects. 8) Add 1)-7) to the docs Thank you. ---------- Added file: http://bugs.python.org/file40897/mailcap patch.zip _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24778> _______________________________________

1 0

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler
by Atsuo Ishimoto 29 Oct '15

29 Oct '15

Atsuo Ishimoto added the comment: > Benjamin Peterson added the comment: > > The OP probably wants something like the Linux-specific signalfd() syscall. Yes. Long explanation: I have an console text editor written in Python/curses(http://kaaedit.github.io/). This editor didn't work with Python 3.5 because select.select() stop raising InterruptedError. Following is sample code to reproduce. This code displays size of terminal. If you resize your terminal, screen is updated and new size is displayed. --------------------------- import curses, select, sys def main(stdscr): i=0 while True: y, x = stdscr.getmaxyx() stdscr.addstr(i % 10, 0, "%d x:%d y:%d" % (i, x, y)) i+=1 stdscr.refresh() try: s=select.select([sys.stdin], [], []) # wait for user input and some sockets. except InterruptedError: stdscr.addstr(i % 10, 0, "%d InterruptedError" % i) i+=1 continue try: c=stdscr.get_wch() except curses.error: stdscr.addstr(i % 10, 0, "%d curses.error" % i) i+=1 continue if c == 'q': break curses.wrapper(main) --------------------------- Resizing terminal generates SIGIWNCH signal. In Python 3.4, select.select() raises InterruptedError when the signal sent. Also, Ncurses library catches the signal and update internal data to reflect new terminal size. To detect resizing in Python 3.5, I had to set signal handler for SIGWINCH as following sample. --------------- import curses, select, sys, signal, os rfd, wfd = os.pipe() os.set_blocking(wfd, False) def f(*args): pass signal.signal(signal.SIGWINCH, f) signal.set_wakeup_fd(wfd) def main(stdscr): i=0 while True: y, x = stdscr.getmaxyx() stdscr.addstr(i, 0, "%d x:%d y:%d" % (i, x, y)) i+=1 stdscr.refresh() try: s=select.select([sys.stdin, rfd], [], []) except InterruptedError: stdscr.addstr(i, 0, "%d InterruptedError" % i) i+=1 continue try: c=stdscr.get_wch() except curses.error: stdscr.addstr(i, 0, "%d curses.error" % i) i+=1 continue if c == 'q': break curses.wrapper(main) ------------- This code doesn't display updated size of terminal because SIGWINCH signal is not sent to nurses library. I have to call curses.resizeterm() manually to tell new terminal size to nurses. I don't know this is common situation or not, but In general, it is not safe to set signal handler when the signal is used by third-party library. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25482> _______________________________________

1 0

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler
by Benjamin Peterson 29 Oct '15

29 Oct '15

Benjamin Peterson added the comment: The OP probably wants something like the Linux-specific signalfd() syscall. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25482> _______________________________________

1 0

[issue25496] tarfile: Default value for compresslevel is not documented
by Sworddragon 29 Oct '15

29 Oct '15

Sworddragon added the comment: At tarfile, but the compresslevel argument is mentioned there but not its default value. ---------- title: Default value for compresslevel is not documented -> tarfile: Default value for compresslevel is not documented _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25496> _______________________________________

1 0

[issue25496] Default value for compresslevel is not documented
by Stéphane Wirtel 28 Oct '15

28 Oct '15

Stéphane Wirtel added the comment: Hi Sworddragon, Where compresslevel is not mentioned in the doc ? Thank you ---------- nosy: +matrixise _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25496> _______________________________________

1 0

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler
by STINNER Victor 28 Oct '15

28 Oct '15

STINNER Victor added the comment: > IMO this reduces usefulness of set_wakeup_fd(). (...) Sorry, I don't understand your use case. Could you elaborate. What do you need? -- According to the GNU libc doc, the signal SIGWINCH is *ignored* by default: "Window size change. This is generated on some systems (including GNU) when the terminal driver’s record of the number of rows and columns on the screen is changed. The default action is to ignore it." https://www.gnu.org/software/libc/manual/html_node/Miscellaneous-Signals.ht… For signal.set_wakeup_fd() I agree that the doc can be enhanced. It's not explicit that only signals with a *Python* signal handler (at least, a signal handler registered by signal.signal) write into the "wakeup FD". ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25482> _______________________________________

1 0

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler
by Berker Peksag 28 Oct '15

28 Oct '15

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

1 0

[issue25496] Default value for compresslevel is not documented
by Berker Peksag 28 Oct '15

28 Oct '15

Changes by Berker Peksag <berker.peksag(a)gmail.com>: ---------- assignee: -> docs@python components: +Documentation keywords: +easy nosy: +berker.peksag, docs@python stage: -> needs patch versions: +Python 3.4, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25496> _______________________________________

1 0

[issue25432] isinstance documentation doesn't explain what happens when type is tuple
by Michael Crouch 28 Oct '15

28 Oct '15

New submission from Michael Crouch: In the section on isinstance() in the Python Standard Library documentation Chapter 2 (https://docs.python.org/3.6/library/functions.html#isinstance) , it says that classinfo "may be a tuple of type objects", but it doesn't explain what the semantics are in that case (e.g., that it will return true iff it is an instance of any of the types in the tuple). ---------- assignee: docs@python components: Documentation messages: 253130 nosy: Michael Crouch, docs@python priority: normal severity: normal status: open title: isinstance documentation doesn't explain what happens when type is tuple versions: Python 2.7, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25432> _______________________________________

8 12