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 musically_ut
Recipients belopolsky, musically_ut, ned.deily, serhiy.storchaka
Date 2017-07-03.08:33:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hmm, I see; I did not know that.

I had just assumed that `./python -m test test_*` was the standard command for running tests.

However, if one does run tests using standalone `datetimetester` (which only imports the _Fast C extension module), then I'll have to rewrite some of the self.skipTest conditions such that they are more defensive, i.e.:

    if '_Pure' not in self.__class__.__name__:

instead of:

    if '_Fast' in self.__class__.__name__:

because some (one?) of the tests fail otherwise.

Shall I make that change?

Also, here is an alternate fix which is a tiny bit less murky than straight up de-duplication of test-classes:

I'm not sure whether this is any clearer or less fragile, though.

Date User Action Args
2017-07-03 08:33:40musically_utsetrecipients: + musically_ut, belopolsky, ned.deily, serhiy.storchaka
2017-07-03 08:33:40musically_utsetmessageid: <>
2017-07-03 08:33:40musically_utlinkissue30822 messages
2017-07-03 08:33:40musically_utcreate