This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author stutzbach
Recipients benjamin.peterson, eric.araujo, gvanrossum, rhettinger, stutzbach, terry.reedy
Date 2010-09-03.19:48:27
SpamBayes Score 6.8523985e-07
Marked as misclassified No
Message-id <1283543309.51.0.574100161542.issue9731@psf.upfronthosting.co.za>
In-reply-to
Content
I agree that my original name proposal is terrible. :-)  method_check and verify_full_api both look fine to me.

> If all collection registrations were bundled together in 
> collections.py, I think I would expect the tests to be in 
> test_collections. But I could still be presuaded that the range method
> check should be in test_range where all the individual methods are 
> (should be!) tested.

All of the registrations are bundled together in _abcoll.py, which collections.py imports into collections.py's namespace.  (It's in a separate file to get around some bootstrapping issues.)

I favor putting them in test_collections to make it slightly easier to check for a 1:1 correlation between registrations and tests, but it's not something I feel strongly about.
History
Date User Action Args
2010-09-03 19:48:29stutzbachsetrecipients: + stutzbach, gvanrossum, rhettinger, terry.reedy, benjamin.peterson, eric.araujo
2010-09-03 19:48:29stutzbachsetmessageid: <1283543309.51.0.574100161542.issue9731@psf.upfronthosting.co.za>
2010-09-03 19:48:28stutzbachlinkissue9731 messages
2010-09-03 19:48:27stutzbachcreate