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.
| Author | richyk |
|---|---|
| Recipients | mark.dickinson, richyk |
| Date | 2008年07月15日.19:06:11 |
| SpamBayes Score | 0.01779131 |
| Marked as misclassified | No |
| Message-id | <1216148773.01.0.251599849233.issue3360@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Some additional information: My original report was with an x86 system. Now, I'm sitting in front of an x86_64 system running Python 2.4.4 (from Debian stable) and Python 2.5.2 (from Debian testing), both 64 bit userland. On these systems, the behavior I described does not exist: Assignment always appears to result in an IEEE754 double-precision float. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月15日 19:06:13 | richyk | set | spambayes_score: 0.0177913 -> 0.01779131 recipients: + richyk, mark.dickinson |
| 2008年07月15日 19:06:13 | richyk | set | spambayes_score: 0.0177913 -> 0.0177913 messageid: <1216148773.01.0.251599849233.issue3360@psf.upfronthosting.co.za> |
| 2008年07月15日 19:06:12 | richyk | link | issue3360 messages |
| 2008年07月15日 19:06:11 | richyk | create | |