Message206326
| Author | skrah |
|---|---|
| Recipients | eric.smith, ethan.furman, gvanrossum, mark.dickinson, pitrou, rhettinger, serhiy.storchaka, skrah, vstinner |
| Date | 2013-12-16.16:17:58 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <20131216161756.GA12598@sleipnir.bytereef.org> |
| In-reply-to | <1387209659.99.0.89294447009.issue19995@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> Did I mention __index__ is an unfortunate name for the current trend for this method? Yes, but it's probably too late to change that now. Also, a fully precise name would be something like: __to_int_exact_iff_object_has_integer_nature__ :) > When you say "accept __index__" do you mean for use as indices, or for use as > values in the data structure itself? The latter, see Lib/test/test_buffer.py:2489 . |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-12-16 16:17:58 | skrah | set | recipients: + skrah, gvanrossum, rhettinger, mark.dickinson, pitrou, vstinner, eric.smith, ethan.furman, serhiy.storchaka |
| 2013-12-16 16:17:58 | skrah | link | issue19995 messages |
| 2013-12-16 16:17:58 | skrah | create | |