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 | rhettinger |
|---|---|
| Recipients | belopolsky, gvanrossum, rhettinger |
| Date | 2008年02月25日.22:08:24 |
| SpamBayes Score | 0.0012018051 |
| Marked as misclassified | No |
| Message-id | <1203977305.41.0.708633991219.issue2186@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
FWIW, I didn't disagree on filter(). Am taking your suggestion under advisement for a couple days. At this point, I'm leaning towards accepting the request (although with a different version of the patch). For map(None, ...), I happy to live with examples like the patch you referenced. It's important that this API be as simple and clean as possible. It's a matter of taste. I concur with Guido that we never would have created map(None, ...) if zip() had existed. The primary use case is obsolete. Also, I think the motivation behind your other use case will likey be addressed in a more general way with an identify function being added to the operator module. That is a more explicit and less hackish than having a special meaning for None. It is also more in-line with the way functional language approach the same problem. Will meditate on both of these for a couple days and get back. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年02月25日 22:08:25 | rhettinger | set | spambayes_score: 0.00120181 -> 0.0012018051 recipients: + rhettinger, gvanrossum, belopolsky |
| 2008年02月25日 22:08:25 | rhettinger | set | spambayes_score: 0.00120181 -> 0.00120181 messageid: <1203977305.41.0.708633991219.issue2186@psf.upfronthosting.co.za> |
| 2008年02月25日 22:08:24 | rhettinger | link | issue2186 messages |
| 2008年02月25日 22:08:24 | rhettinger | create | |