➜
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.
Created on 2002-07-11 07:52 by yitzg, last changed 2022-04-10 16:05 by admin. This issue is now closed.
| Messages (5) | |||
|---|---|---|---|
| msg11528 - (view) | Author: Yitz Gale (yitzg) | Date: 2002-07-11 07:52 | |
In Library Refernce, 2.2.1 Truth Value Testing: In current text "...when that method returns zero." and the associated footnote, the word "zero" should be replaced with "a false value". |
|||
| msg11529 - (view) | Author: Fred Drake (fdrake)  |
Date: 2002-07-12 17:16 | |
Logged In: YES user_id=3066 Clarified in Doc/lib/libstdtypes.tex revisions 1.99 and 1.80.6.10. __nonzero__() *must* return an integer. |
|||
| msg11530 - (view) | Author: Yitz Gale (yitzg) | Date: 2002-07-13 23:02 | |
Logged In: YES user_id=576391 Hmm - in that case, there is also a bug in Ref. Guide 3.3.1 which says that __nonzero__() is allowed to return boolean. But that would be really quirky, are you sure boolean is not allowed? |
|||
| msg11531 - (view) | Author: Fred Drake (fdrake) |
Date: 2002-08-06 21:51 | |
Logged In: YES user_id=3066 I'll add a clarification that returning an integer includes returns a boolean. The True and False values are integers in 2.2.1 and instances of bool in 2.3, but bool is a subclass of the integer type, so returning False from __nonzero__ really is returning an integer. I'll check this into CVS once SourceForge clears a stale lock; leaving it open until then so I don't forget. |
|||
| msg11532 - (view) | Author: Fred Drake (fdrake) |
Date: 2002-08-07 15:41 | |
Logged In: YES user_id=3066 Checked in as Doc/lib/libstdtypes.tex revisions 1.104, 1.80.6.11. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:05:29 | admin | set | github: 36875 |
| 2002-07-11 07:52:59 | yitzg | create | |