Hi all, a bit of grep'ping and personal examination discovered the following tests in trunk/ that could be converted to unittest or doctests. Any thoughts, pro or con? (I understand from Brett that the goal is to eradicate "old-style" tests, by which I think he means tests that do not use unittest or doctest. There are some good reasons to switch to using unittests, not least of which is that you can use a variety of frameworks (nose, py.test) to do value-added wrapping and management of such tests.) Suggestions for additional things to test or tests to modify, clean up, or extend and expand are welcome. thanks, --titus --- test_select test_contains test_crypt test_dbm test_dummy_threading test_errno test_getargs test_gdbm test_pep247 test_strftime test_thread test_queue test_fcntl test_format test_curses test_descr test_funcattrs test_gdbm test_socketserver
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4