Message109698
| Author |
pitrou |
| Recipients |
benjamin.peterson, eric.araujo, georg.brandl, paddy3118, pitrou, terry.reedy |
| Date |
2010年07月09日.09:25:50 |
| SpamBayes Score |
0.0014446451 |
| Marked as misclassified |
No |
| Message-id |
<1278667547.3178.0.camel@localhost.localdomain> |
| In-reply-to |
<1278650471.65.0.420532701961.issue3214@psf.upfronthosting.co.za> |
| Content |
> I actually would challenge the first sentence "A pythonic programming
> style which determines an object’s type by inspection of its method or
> attribute signature ". To me, and at least some usage on python-list,
> duck-typing means determining the interface (not type) by calling
> methods and catching exceptions if not present. This is the EAFP
> rather than inspection/LBYL style of duck typing.
Indeed. I would also remove "pythonic", because it will only confuse the
beginner. |
|