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 serhiy.storchaka
Recipients abarnert, gvanrossum, martin.panter, ncoghlan, r.david.murray, rhettinger, serhiy.storchaka
Date 2016-01-05.22:57:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452034655.13.0.578820880323.issue25958@psf.upfronthosting.co.za>
In-reply-to
Content
Without tests you can't be sure that there is no special case in some abstract classes or operators, or that it can't be introduced in future. To decrease the copy-pasting you can use code generation for testing.

But I don't know what is the best place for tests. Tests for special methods are scattered though different files: test_binop, test_class, test_compare, test_descr, test_richcmp, test_augassign, test_contains, test_iter, etc.
History
Date User Action Args
2016-01-05 22:57:35serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, rhettinger, ncoghlan, r.david.murray, martin.panter, abarnert
2016-01-05 22:57:35serhiy.storchakasetmessageid: <1452034655.13.0.578820880323.issue25958@psf.upfronthosting.co.za>
2016-01-05 22:57:35serhiy.storchakalinkissue25958 messages
2016-01-05 22:57:34serhiy.storchakacreate