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 r.david.murray
Recipients barry, catalin.iacob, jesstess, python-dev, r.david.murray, sandro.tosi, zvyn
Date 2014-07-03.18:55:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1404413730.22.0.124604706716.issue15014@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks, Milan.

I made some tweaks...mostly documentation and code style (your code style wasn't wrong, I just have some slightly different preferences with regards to line folding).  I also eliminated the authobjects test method, since I didn't see that it added anything to duplicate the code from the login method to test them...they get tested via the login methods.  Instead I added the loop to the test for the auth method, so that we test that calling the public API with the auth objects that are documented as part of the public API work.  That is, if someone were to change login such that the method names changed but login still worked, the auth test method will throw an error because the documented method names changed.

I'm attaching the final patch here so you can look at the differences via the reitveld patch-diff function, if you want to.
History
Date User Action Args
2014-07-03 18:55:30r.david.murraysetrecipients: + r.david.murray, barry, jesstess, sandro.tosi, catalin.iacob, python-dev, zvyn
2014-07-03 18:55:30r.david.murraysetmessageid: <1404413730.22.0.124604706716.issue15014@psf.upfronthosting.co.za>
2014-07-03 18:55:30r.david.murraylinkissue15014 messages
2014-07-03 18:55:29r.david.murraycreate