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 neologix
Recipients neologix, rbcollins, yselivanov
Date 2015-07-23.14:05:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1oJ4Uf-eW-jPhnuPTEdtMWdqHosVkhDVDHzLhLStJNpA@mail.gmail.com>
In-reply-to <1437659998.86.0.718163513736.issue24694@psf.upfronthosting.co.za>
Content
I understand the risk of breakeage, but that's still broken, because
we break LIFO ordering.

I'd been using addCleanup() for years and never bothered looking at
the documentation - which is admitedly a mistake - because LIFO
ordering is the natural behavior: since addCleanup() is called once
the test has been entered - so after setUp, logic would expect it to
be undone before tearDown.

But I guess that ship has sailed...
History
Date User Action Args
2015-07-23 14:05:36neologixsetrecipients: + neologix, rbcollins, yselivanov
2015-07-23 14:05:36neologixlinkissue24694 messages
2015-07-23 14:05:35neologixcreate