docstring in test_denied_DELETE_of_versioned_object confuses test output

Docstring confuses nose and produces atypical test output:

% nosetests -v test_server.py:TestObjectController.test_denied_DELETE_of_versioned_object
Verify that a request with read access to a versions container … ok

this looks really odd when mixed with other tests - and becomes somewhat harder to trace down to a specific file and test:
<snip>
test_copy_with_spaces_in_x_copy_from_and_account (test.unit.proxy.test_server.TestObjectController) ... ok
test_cross_policy_DELETE_versioning (test.unit.proxy.test_server.TestObjectController) ... ok
test_custom_mime_types_files (test.unit.proxy.test_server.TestObjectController) ... ok
Verify that a request with read access to a versions container ... ok
test_error_limiting (test.unit.proxy.test_server.TestObjectController) ... ok
test_error_limiting_survives_ring_reload (test.unit.proxy.test_server.TestObjectController) ... ok
test_expirer_DELETE_on_versioned_object (test.unit.proxy.test_server.TestObjectController) ... ok
test_iter_nodes (test.unit.proxy.test_server.TestObjectController) ... ok
<snip>

Because of a docstring introduced in the new unit test we get the abnormal test output:

+ def test_denied_DELETE_of_versioned_object(self):
+ """
+ Verify that a request with read access to a versions container
+ is unable to cause any write operations on the versioned container.
+ """
+ methods = set()
+ authorize_call_count = [0]
+

While it is great to have the test description it might be better to make it a pure comment and not a docstring to
get standard typical test output that the other tests produce:

% nosetests -v test_server.py:TestObjectController.test_denied_DELETE_of_versioned_object
test_denied_DELETE_of_versioned_object (test.unit.proxy.test_server.TestObjectController) … ok