Ben Finney wrote: > "Stephen J. Turnbull" <stephen at xemacs.org> writes: > >> Terry Reedy writes: >> >> > For the community as a whole, all stdlib modules are suggestions >> > and examples, not commands. >> >> Well, even if "standard" is too strong a word, the DeprecationWarnings >> and eventual removal of the methods surely constitute an imposition. > > I understood Terry's statement as meaning that there is no commandment > to use the standard library 'unittest' module at all. If a user > doesn't like the behaviour of a module (such as 'unittest') in the > standard library, they can accept the burden of implementing one that > behaves the way they like. I have written the few specialized test functions that I need my current project. I did this after considering (and taking ideas from) py.test. I will also use doctest as a supplement. I also meant that one who does use something is free to rename it. I commonly import xskjfl as x;-)
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