Message156326
| Author |
tshepang |
| Recipients |
bethard, docs@python, eric.araujo, ezio.melotti, ncoghlan, tshepang |
| Date |
2012年03月19日.11:02:10 |
| SpamBayes Score |
0.002548636 |
| Marked as misclassified |
No |
| Message-id |
<CAA77j2Dxwf=_3joe9mG63XiXfoovgHN3mb3GgVho94L7RM9y4Q@mail.gmail.com> |
| In-reply-to |
<CAA77j2AhPzLi=caR3ccQ47NeNZRgGAZ2iGhJpSPCug6VE9hL7w@mail.gmail.com> |
| Content |
> Find attached. Note that I kept some of those anti-pattern examples
> you mentioned, and then later on introduced your preferred way of
> doing things (using action="count" and ">=" checks instead of "=="
> ones).
Reason I kept those is to easily lead the reader into the "more
correct" way of doing things, by first doing them in a more obvious
but less ideal way.
For example, when the goal of one is to teach one to remove duplicates
from list, it's nice if you first do the process manually, and then
later on introduce the set() type, just so the user can appreciate
them more. Same applies to doing "for item in range(len(iterable))"
vs. "for item in iterable". |
|