Kálmán Gergely wrote: > Since I am not a python core developer the patch might still be in a > pretty outdated state. I'd like someone to look it over > and direct me to some documentation (the ones I've found so far were > pretty sketchy), for it to be acceptable for inclusion. > The sanity of the code is what matters to me the most. I've looked it > over though and found it in a sound state, but I guess > you guys might have a different opinion about that ;) > > With writing the test cases, some documentation would be nice.
Most unit tests these days are written based on either doctest or unittest. When adding new features to an existing module, it is usually best to follow the testing style already used for the rest of that module (in this case, that should be test/test_socket.py). The relevant question in the dev FAQ gives good pointers: http://www.python.org/dev/faq/#how-to-test-a-patch > I've attached the patch generated with svn diff for revision 73434, and > the test code that I use to pass a file descriptor > between processes. It works just fine :). Uploading files to the tracker is generally the best option - patches tend to get lost if they're just sent to the mailing list. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
