New submission from Stefan Krah <[email protected]>:
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.
----------
assignee: docs@python
components: Documentation
files: longobject-doc.diff
keywords: patch
messages: 143922
nosy: docs@python, mark.dickinson, skrah
priority: normal
severity: normal
stage: patch review
status: open
title: longobject: documentation improvements
type: feature request
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file23133/longobject-doc.diff
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue12965>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
