➜

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 pitrou
Recipients eric.araujo, ods, pitrou, pje, r.david.murray, riffm
Date 2011-01-19.16:52:32
SpamBayes Score 0.0033900498
Marked as misclassified No
Message-id <1295455973.84.0.301286307596.issue10935@psf.upfronthosting.co.za>
In-reply-to
Content 
> OK.  So he is saying that when the spec says "an object of type str" he 
> means 'type(x) is str' as opposed to 'isinstance(x, str)'.  I would
> naively have expected the latter, as other people clearly do as well.

+1 with RDM here.

> Doesn't matter how unpythonic it is: the spec calls for exact types

Can you clarify why it does?
History
Date User Action Args
2011-01-19 16:52:53pitrousetrecipients: + pitrou, pje, ods, eric.araujo, r.david.murray, riffm
2011-01-19 16:52:53pitrousetmessageid: <1295455973.84.0.301286307596.issue10935@psf.upfronthosting.co.za>
2011-01-19 16:52:33pitroulinkissue10935 messages
2011-01-19 16:52:33pitroucreate