Message339705
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 | xtreak |
|---|---|
| Recipients | Peter de Blanc, ezio.melotti, michael.foord, rbcollins, xtreak |
| Date | 2019-04-09.06:14:12 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1554790453.08.0.683141703146.issue36569@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
The use case of setUpClass and tearDownClass is to run once during class setup and teardown where a class variable might be mutated. It's not a strict requirement [0] but rather maybe a common use case. There is at least one test case where setUpClass is used with @staticmethod at [1] [0] https://github.com/python/cpython/blob/5909ad1217aad200c69ffa794fcab285bacb609e/Lib/unittest/suite.py#L159 [1] https://github.com/python/cpython/blob/5909ad1217aad200c69ffa794fcab285bacb609e/Lib/test/test_dbm_gnu.py#L12 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-04-09 06:14:13 | xtreak | set | recipients: + xtreak, rbcollins, ezio.melotti, michael.foord, Peter de Blanc |
| 2019-04-09 06:14:13 | xtreak | set | messageid: <1554790453.08.0.683141703146.issue36569@roundup.psfhosted.org> |
| 2019-04-09 06:14:13 | xtreak | link | issue36569 messages |
| 2019-04-09 06:14:12 | xtreak | create | |