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 barry
Recipients barry, ncoghlan, r.david.murray
Date 2013-03-17.15:19:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20130317081927.45b3e799@anarchist>
In-reply-to <1363533040.75.0.542978231536.issue17445@psf.upfronthosting.co.za>
Content
On Mar 17, 2013, at 03:10 PM, R. David Murray wrote:

>There was a long thread about this on python-dev that might be worth going
>back over, where I had the same misconception (that functions should always
>return the same type as their arguments).  While I think that should be the
>default design, it isn't always the best API.  (The real rule, if I recall
>correctly, is that functions should never accept *mixed* argument types for
>input data.)

Totally agree about the mixed type rule.

But this is something different, and I know it's been discussed, and is a
difficult problem.  It's causing real-world pain for people though, so it's
worth thinking about again.
History
Date User Action Args
2013-03-17 15:19:32barrysetrecipients: + barry, ncoghlan, r.david.murray
2013-03-17 15:19:32barrylinkissue17445 messages
2013-03-17 15:19:32barrycreate