Looking at #1153226, I found this:
We introduced emitting a DeprecationWarning for PyArg_ParseTuple integer arguments if a float was given. This doesn't affect functions like file.seek which use PyInt_AsLong to parse their argument. PyInt_AsLong calls the nb_int slot which silently converts floats to ints.
Is that acceptable, should PyInt_AsLong not accept other numbers or should the functions be changed?
Georg
file.seek etc. should be changed to use PyNumber_AsIndex or whatever it's called.
On 5/31/06, Georg Brandl g.brandl@gmx.net wrote:
Looking at #1153226, I found this:
We introduced emitting a DeprecationWarning for PyArg_ParseTuple integer arguments if a float was given. This doesn't affect functions like file.seek which use PyInt_AsLong to parse their argument. PyInt_AsLong calls the nb_int slot which silently converts floats to ints.
Is that acceptable, should PyInt_AsLong not accept other numbers or should the functions be changed?
Georg
Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
Guido> ... PyNumber_AsIndex or whatever it's called.
Maybe the API is getting a little fat if it doesn't fit comfortably in the BDFL's brain... Does that suggest it might need some streamlining for Py3k?
Skip
-
Georg Brandl -
Guido van Rossum -
skip＠pobox.com