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 r.david.murray
Recipients r.david.murray, rhettinger
Date 2011-01-31.21:42:15
SpamBayes Score 4.8891026e-05
Marked as misclassified No
Message-id <1296510136.44.0.0155616076581.issue11085@psf.upfronthosting.co.za>
In-reply-to
Content
Hmm.  OK, so it is just Callable that is the odd man out.

But in that case, shouldn't the pattern be adopted by the other modules that define abcs as well?  And if the distinction isn't sharp enough in those other modules to justify that, then I question whether it is a good idea to special-case collections.  The docs already make the distinction pretty clear.

My "flat is better than nested" alarm is going off here :)
History
Date User Action Args
2011-01-31 21:42:16r.david.murraysetrecipients: + r.david.murray, rhettinger
2011-01-31 21:42:16r.david.murraysetmessageid: <1296510136.44.0.0155616076581.issue11085@psf.upfronthosting.co.za>
2011-01-31 21:42:15r.david.murraylinkissue11085 messages
2011-01-31 21:42:15r.david.murraycreate