Message108538
| Author |
mark.dickinson |
| Recipients |
drkirkby, mark.dickinson |
| Date |
2010年06月24日.18:13:44 |
| SpamBayes Score |
0.0010244573 |
| Marked as misclassified |
No |
| Message-id |
<1277403226.17.0.330256853689.issue9069@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
David, please could you also tell me whether HAVE_COPYSIGN is defined for those builds of Python? It should be in pyconfig.h in the top level of the build directory, if it is.
And (just to double check), at configure time, there should be a line in the output of the configure script that looks like
checking for copysign... yes
Do you get 'yes' or 'no' there?
If I had to guess, I'd say that it's the float -> hex conversion that's going wrong (so that (-0.0).hex() produces '0x0.0p+0' instead of '-0x0.0p+0'), and that this is caused by either a buggy system copysign function, or by the system copysign function not being found and Python using a buggy workaround. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年06月24日 18:13:46 | mark.dickinson | set | recipients:
+ mark.dickinson, drkirkby |
| 2010年06月24日 18:13:46 | mark.dickinson | set | messageid: <1277403226.17.0.330256853689.issue9069@psf.upfronthosting.co.za> |
| 2010年06月24日 18:13:44 | mark.dickinson | link | issue9069 messages |
| 2010年06月24日 18:13:44 | mark.dickinson | create |
|