[issue12782] Multiple context expressions do not support parentheses for continuation across lines

Changes by Atsuo Ishimoto : -- nosy: +ishimoto ___ Python tracker <http://bugs.python.org/issue12782> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue19977] Use "surrogateescape" error handler for sys.stdin and sys.stdout on UNIX for the C locale

Changes by Atsuo Ishimoto : -- nosy: +ishimoto ___ Python tracker <http://bugs.python.org/issue19977> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12782] Multiple context expressions do not support parentheses for continuation across lines

Atsuo Ishimoto added the comment: In Python 3.3, we have contextlib.ExitStack() for multiple contexts. So, perhaps we can close this issue? -- ___ Python tracker <http://bugs.python.org/issue12

[issue9949] os.path.realpath on Windows does not follow symbolic links

Changes by Atsuo Ishimoto : Removed file: http://bugs.python.org/file26487/issue9949.patch ___ Python tracker <http://bugs.python.org/issue9949> ___ ___ Python-bugs-list m

[issue9949] os.path.realpath on Windows does not follow symbolic links

Atsuo Ishimoto added the comment: I have unlinked my patch since it doesn't looks correct now. Sorry for disturbing. -- ___ Python tracker <http://bugs.python.org/i

[issue5640] Wrong print() result when unicode error handler is not 'strict'

New submission from Atsuo Ishimoto : In Python 3(both 3.0.1 and SVN repo), if I set PYTHONIOENCODING=ShiftJIS:backslashreplace, print() outputs wrong result. >>> print("\xff") \xff\xff Obviously, '\xff' should be printed instead of '\xff\xff'. Following

[issue5110] Printing Unicode chars from the interpreter in a non-UTF8 terminal raises an error (Py3)

Atsuo Ishimoto added the comment: My proposal to make backslashreplace a default error handler for interactive session was rejected by Guido [1]. Does something like PYTHONIOENCODING=ascii:backslashreplace work for you? With PYTHONIOENCODING, you can effectively make backslashreplace a

[issue5640] Wrong print() result when unicode error handler is not 'strict'

Atsuo Ishimoto added the comment: I tested with py3k branch and worked fine. Thank you. -- versions: +Python 2.6, Python 2.7 ___ Python tracker <http://bugs.python.org/issue5

[issue1079] decode_header does not follow RFC 2047

Atsuo Ishimoto added the comment: +1 for Tony's patch. This patch reverts fix for Issue1582282 filed by tkikuchi. I cannot understand the rationale for solution proposed in Issue1582282. How does the fix make easier to read mails from Entourage? -- nosy: +ishimoto, tki

[issue3665] Support \u and \U escapes in regexes

Atsuo Ishimoto added the comment: Here's an updated patch for py3k branch. As per Georg's comment, I added to check codepoint in the character ranges, conversion to the surrogate pairs. I also added check to raise exception if codepoint > 0x10. I with to English speakers

[issue10952] Don't normalize module names to NFKC?

Changes by Atsuo Ishimoto : -- nosy: +ishimoto ___ Python tracker <http://bugs.python.org/issue10952> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10952] Don't normalize module names to NFKC?

Atsuo Ishimoto added the comment: Converting identifiers to NFKC is problematic to work with FULLWIDTH letters such as 'ａ'(FULLWIDTH LATIN SMALL LETTER A). We can create module named 'ａａａ.py', but this module could not be imported on all platforms I know. >>&g

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler

New submission from Atsuo Ishimoto: I expect following code prints '\x1c' when I resize terminal window on Linix/Mac terminal. import select, os, signal rfd, wfd = os.pipe() os.set_blocking(wfd, False) signal.set_wakeup_fd(wfd) select.s

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler

Atsuo Ishimoto added the comment: Okay, so I think this needed to be documented in signal.set_wakeup_fd(). IMO this reduces usefulness of set_wakeup_fd(). If I need to install custom handler by my self, I can write to fd in my own custom handler. And, installing custom handler omits

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler

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&#x

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler

Atsuo Ishimoto added the comment: Thank you for good sample. This should be written in PEP 475. But installing new signal handler can cause different behavior. As in my previous example, if other 3rd party libraries(ncurses in my case) need to handle the signal, signal is consumed by Python

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler

Atsuo Ishimoto added the comment: Yes, I can. So, for my custom text editor, problem have solved already. But I still think it is desirable for Python to have something like signalfd(), because not all functions used in the signal handler of third party library can be called from user&#

[issue25482] signal.set_wakeup_fd() doesn't work if the signal don't have handler

Atsuo Ishimoto added the comment: Ah, I didn't know it. Thank you for clarification. -- ___ Python tracker <http://bugs.python.org/issue25482> ___ ___ Pytho

<    1   2