Message188500
| Author | neologix |
|---|---|
| Recipients | Trundle, abacabadabacaba, benhoyt, brian.curtin, christian.heimes, eric.araujo, giampaolo.rodola, gregory.p.smith, loewis, ncoghlan, neologix, nvetoshkin, pitrou, rhettinger, serhiy.storchaka, socketpair, terry.reedy, tim.golden, torsten, twouters, vstinner |
| Date | 2013-05-06.09:36:29 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAH_1eM3S+HakCTj9BoifrWV8nqBs4x24NmD7MTO1sb0DDrAspw@mail.gmail.com> |
| In-reply-to | <1367831336.15.0.223604857326.issue11406@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> I don't think that's true in general, or true of how other Python APIs work. For instance, many APIs return a "file-like object", and you can only do certain things on that object, depending on what the documentation says, or what EAFP gets you. Some file-like object don't support seek/tell, some don't support close, etc. I've seen plenty of walk-like-a-duck checks like this: Yes, I'm fully aware duck-typing ;-) But here, you're saying that "a duck has a beak, but it *may* have legs, a tail, etc". It's just looks wrong to me on so many levels. Please bring this up on python-dev. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-05-06 09:36:30 | neologix | set | recipients: + neologix, loewis, twouters, rhettinger, terry.reedy, gregory.p.smith, ncoghlan, pitrou, vstinner, giampaolo.rodola, christian.heimes, tim.golden, eric.araujo, Trundle, brian.curtin, benhoyt, torsten, nvetoshkin, abacabadabacaba, socketpair, serhiy.storchaka |
| 2013-05-06 09:36:30 | neologix | link | issue11406 messages |
| 2013-05-06 09:36:29 | neologix | create | |