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 gvanrossum
Recipients Guido.van.Rossum, gvanrossum, lukasz.langa, r.david.murray
Date 2015-07-17.14:10:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437142255.7.0.438853139063.issue24635@psf.upfronthosting.co.za>
In-reply-to
Content
You can list me as the expert for typing.py, since I wrote it. :-)  (However, until mid August I have limited availability since I'm on vacation.)

This looks indeed like a test order dependency.  The three failures are all basic failures where an empty set, dict or list is expected to be an instance of the corresponding ABC (AbstractSet, Mapping, Sequence) defined in typing.py. Those ABCs in turn derive (in a slightly sneaky way) from the corresponding ABCs in collections.abc.

My hunch is that some other test messes with the ABC registration cache and doesn't restore it -- or typing.py's sneaky way of deriving from collections.abc has a subtle bug in it.  Maybe something is calling reload(collections.abc)?

I haven't done any research to confirm or deny this theory.  It shouldn't be too hard to find the (probably only a handful of) tests that mess with the registration cache.
History
Date User Action Args
2015-07-17 14:10:55gvanrossumsetrecipients: + gvanrossum, r.david.murray, lukasz.langa, Guido.van.Rossum
2015-07-17 14:10:55gvanrossumsetmessageid: <1437142255.7.0.438853139063.issue24635@psf.upfronthosting.co.za>
2015-07-17 14:10:55gvanrossumlinkissue24635 messages
2015-07-17 14:10:54gvanrossumcreate