Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue11445>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ed Campbell added the comment:
I think this is a real improvement. Thanks. I have a few comments:
I suspect you know this, but the rendering problem occurs because of the call
to curses.endwin() in tearDown(). I experimented with delaying this until
teadDownClass() but this led to even more
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue15730>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue17128>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue10544>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue16848>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue15663>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ed Campbell :
--
nosy: +esc24
___
Python tracker
<http://bugs.python.org/issue16773>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ed Campbell added the comment:
I'd suggest using unittest.TestCase.assertRaises() as a context manager to
remove some try-excepts. For example I think function
test_userptr_without_set() on line 245 could use:
with self.assertRaises(curses.panel.error):
p.userptr()
I could create a