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 Anthony Sottile
Recipients Anthony Sottile, asottile, cjw296, michael.foord, xtreak
Date 2018-12-11.06:55:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544511345.65.0.788709270274.issue26704@psf.upfronthosting.co.za>
In-reply-to
Content
to be honest, I don't recall exactly given it's been 2 and a half years since the original report with no activity.

if I recall correctly, this was encountered while upgrading the `mock` backport in yelp's monolithic repository.

I want to say the reason this was hard to "fix" properly was due to some blanket patches being applied in a base test case and then other test cases re-patching those methods to add more specific behaviour.  This worked fine in python2.7 and all the way until python3.3 but then was broken by changes in python3.4

Fortunately, they've been fixed in python3.7.  I guess I've been encouraged to write a patch with a test so it does not regress in the future
History
Date User Action Args
2018-12-11 06:55:45Anthony Sottilesetrecipients: + Anthony Sottile, cjw296, michael.foord, asottile, xtreak
2018-12-11 06:55:45Anthony Sottilesetmessageid: <1544511345.65.0.788709270274.issue26704@psf.upfronthosting.co.za>
2018-12-11 06:55:45Anthony Sottilelinkissue26704 messages
2018-12-11 06:55:45Anthony Sottilecreate