➜

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.

classification
Title: Coercion rules incomplete
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: gvanrossum Nosy List: fdrake, gvanrossum, hinsen
Priority: low Keywords:

Created on 2001-05-07 09:39 by hinsen, last changed 2022-04-10 16:04 by admin. This issue is now closed.

Messages (3)
msg4656 - (view) Author: Konrad Hinsen (hinsen) Date: 2001-05-07 09:39 
The description of the coercion rules for numeric types
at
http://www.python.org/doc/current/ref/numeric-types.html
is incomplete. Step 3 says "We only get here if neither
x nor y is a class instance. " But step 2a also refers
to step 3 for the case that an explicit coercion
function returns None. It is not clear what happens in
that case.
msg4657 - (view) Author: Fred Drake (fdrake) (Python committer) Date: 2001-05-09 18:04 
Logged In: YES 
user_id=3066

Guido, can you correct this?  I'm afraid I might get it
wrong.  The coercion rules are strange turf for me.  ;-(
msg4658 - (view) Author: Guido van Rossum (gvanrossum) * (Python committer) Date: 2002-06-03 19:07 
Logged In: YES 
user_id=6380

I've "fixed" this by a rewrite of the subsection on coercion
rules.
History
Date User Action Args
2022-04-10 16:04:02adminsetgithub: 34465
2001-05-07 09:39:44hinsencreate