Hi, Jeremy Hylton: > Modified Files: > test_userstring > Log Message: > expect message "no regression test case for method 'encode' [...] > test_userstring > + no regression test case for method 'encode' > + no regression test case for method 'isalnum' > + no regression test case for method 'isalpha' Hmmmm..... Wouldn't it be better to actually write some simple test cases for these methods and add them to 'Lib/test/test_string.py' (if not already done)? My initial idea to put this check into 'test_userstring.py' was to discover missing test cases for new methods that should be copied from test_string.py in order to keep UserString in sync with new functionality added to the builtin string types. Regards, Peter
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