| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
SF bug #1400822, Extended version of _curses over{lay,write} does not work
Fix signatures to conform to doc (also fixed ungetmouse()).
|
|
|
|
|
| |
Bug #1400115, Fix segfault when calling curses.panel.userptr()
without prior setting of the userptr.
|
|
|
|
|
|
|
|
|
|
|
|
| |
initscr() will exit if there's an error. Try to catch the obvious failure
cases if TERM isn't set or is unknown (perhaps we should only check if
unset or empty?)
Skip the test if TERM isn't set. This seems to occur when running under
buildbot and presumably cron.
For some more info check here:
http://mail.python.org/pipermail/python-checkins/2006-January/048704.html
|
|
|
|
| |
buildbot).
|
| |
|
|
|
|
|
|
|
| |
[ 1005123 ] test_curses fails on MacOS X 10.3
Be a bit more guarded about what we expect a terminal to be capable
of.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
imports e.g. test_support must do so using an absolute package name
such as "import test.test_support" or "from test import test_support".
This also updates the README in Lib/test, and gets rid of the
duplicate data dirctory in Lib/test/data (replaced by
Lib/email/test/data).
Now Tim and Jack can have at it. :)
|
|
the curses module. It's not run automatically; '-u curses' must be
specified as an argument to regrtest
|