Message143922
| Author | skrah |
|---|---|
| Recipients | docs@python, mark.dickinson, skrah |
| Date | 2011-09-12.16:57:48 |
| SpamBayes Score | 4.317118e-05 |
| Marked as misclassified | No |
| Message-id | <1315846670.45.0.93309834122.issue12965@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think the integer objects documentation could be clearer on a
couple of points:
- Despite being listed under "Concrete Objects Layer", some
functions implicitly accept anything with an __int__()
method. Currently only the PyLong_AsLong() documentation
states this explicitly.
The patch clearly distinguishes between functions that
duck type and functions that don't.
- The patch replaces "is greater than *_MAX" instances with
"out of bounds" to include the other error condition
"is less than *_MIN".
Additionally, the patch fixes comments in longobject.c that
don't state the duck typing behavior. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-09-12 16:57:50 | skrah | set | recipients: + skrah, mark.dickinson, docs@python |
| 2011-09-12 16:57:50 | skrah | set | messageid: <1315846670.45.0.93309834122.issue12965@psf.upfronthosting.co.za> |
| 2011-09-12 16:57:49 | skrah | link | issue12965 messages |
| 2011-09-12 16:57:49 | skrah | create | |