Most curses.ascii predicates corresponds C functions declared in <ctype.h>. But there are some differences:1. isblank() returns True for space and backspace instead of space and tab.2. ispunct() returns True for non-ASCII and control characters.3. iscntrl() returns False for '\x7f'. Note that there is different function isctrl().These differences look as bugs. Proposed patch fixes them and adds tests for all curses.ascii functions.

Committed with wrong commit message (damn two clipboards on X11) inac8338546ca8,d7b6c07bc713,d03c8d0a6a73.

There is an overlapping issue from 2010: "curses.ascii.isblank() function is broken. It confuses backspace (BS 0x08) with tab (0x09)"http://bugs.python.org/issue9770 Your patch fixes it too (it should be closed). Note: the patch does not pass tests fromLib/test/test_curses_ascii.py attached toissue9770 (even if the code: `if char_class_name in ('cntrl', 'punct') test = unittest.expectedFailure(test)` is removed) e.g., iscntrl(-1) should be False but it returns True:  $ ./python  >>> import curses.ascii  >>> curses.ascii.iscntrl(-1) #XXX expected False  TrueIf we ignore negative ints then isblank, ispunct, iscntrl provided in the curses_ascii.patch are ok.

Since screen.getch() can return -1, it looks reasonable to make curses.ascii predicates to work with negative integers.Do you want to open a new issue and write a patch Akira?

I'm not sure anything should be done (e.g., it is "undefined behavior" to pass a negative value such as CHAR_MIN (if *char* type is signed) to a character classification function in C. Though EOF value (-1 traditionally) should be handled).If you want to explore it further; I've enumerated open questions in 2014 (inconsistent TypeError, ord(c) > 0x100, negative ints handling, etc)http://bugs.python.org/issue9770#msg221008