Message291666
| Author |
r.david.murray |
| Recipients |
jdemeyer, r.david.murray, scoder, steven.daprano |
| Date |
2017年04月14日.14:50:54 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1492181455.26.0.234290892987.issue30071@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The python standard library makes extensive use of duck typing. Duck typing is a pretty fundamental part of the design of Python, IMO. Even the ABC module does a bunch of duck typing, rather than requiring strict subclassing or registration.
I think the request is valid, and it is mostly a matter of agreeing on the best way to identify function ducks. (I agree that Steven's example is intentionally trying to quack like a duck and so is not, IMO, a valid counter argument against using __code__). I doubt we would make such a change in anything except a feature release, though.
Let's see what other devs besides Steven and I think. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2017年04月14日 14:50:55 | r.david.murray | set | recipients:
+ r.david.murray, scoder, steven.daprano, jdemeyer |
| 2017年04月14日 14:50:55 | r.david.murray | set | messageid: <1492181455.26.0.234290892987.issue30071@psf.upfronthosting.co.za> |
| 2017年04月14日 14:50:55 | r.david.murray | link | issue30071 messages |
| 2017年04月14日 14:50:54 | r.david.murray | create |
|