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 oscarbenjamin
Recipients gregory.p.smith, larry, ncoghlan, oscarbenjamin, steven.daprano, wolma
Date 2014-02-04.14:46:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20140204144607.GA2333@gmail.com>
In-reply-to <1391512536.52.0.204327973152.issue20481@psf.upfronthosting.co.za>
Content
I was working on the basis that we were talking about Python 3.5.

But now I see that it's a 3.4 release blocker. Is it really that urgent?

I think the current behaviour is very good at handling a wide range of types.
It would be nice to consistently report errors for incompatible types but it
can also just be documented as a thing that users shouldn't do.

If there were a situation where it silently returned a highly inaccurate
value I would consider that urgent but I don't think there is.
History
Date User Action Args
2014-02-04 14:46:13oscarbenjaminsetrecipients: + oscarbenjamin, gregory.p.smith, ncoghlan, larry, steven.daprano, wolma
2014-02-04 14:46:13oscarbenjaminlinkissue20481 messages
2014-02-04 14:46:13oscarbenjamincreate