> So should I go on with this? Do we want to change all tests before 2.3 > is finished, or start changing them after 2.3 is released > (or something in between)? I'd say something in between. It's probably good if someone (not me) reviews your patches. It's never good to rush these things, and I've said before that there's no reason to insist on all tests being PyUnit tests. (Definitely don't touch anything that's using doctest.) In particular, I *don't* want you to literally translate existing tests to PyUnit idiom. Try to improve on the tests -- think about end cases, etc. There are coverage tools (ask Skip) -- when testing Python modules, see if the test covers all code in the module! --Guido van Rossum (home page: http://www.python.org/~guido/)
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