> Could someone please offer some advice/comments on this? While > restructuring test_socket.py, I've come across the following > (limitation?) problem with the unittest module. To test socket stuff, > I really need to use two separate processes or threads. Since > fork() is much better supported, here's my attempt at porting the > _fileobject tests into unittest. I really like the structure of the > test (hopefully you guys agree) and this is how I'd like to lay it out > ideally for testing things like accept/connect, etc, using the various > layers of my inhertiance hierarchy. Please don't use fork -- that isn't supported on Windows. --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