Status: Accepted Owner: smichr Labels: Type-Defect Priority-Medium New issue 1614 by smichr: Real tuple argument weirdness http://code.google.com/p/sympy/issues/detail?id=1614
While working on increasing test cases to increase the coverage of core/numbers I noticed that Real can take an mpf tuple argument. I found the following strange behavior: a double negative sign appears on the number if the sign term of the tuple is not 0 or 1 and if one increase the bit count (in error of what it really is) then digits start disappearing from the result. These problems are easy to fix in Real's acceptance of these bad tuples, but the strange output is perhaps with investigating: why the double negative, and why does precision (regardless of the sign term) seem to decrease as the bitcount value is increased? >>> for bc in range(20,40): ... print Real((2,3,1,bc)),bc ... --6.0000000000000 20 --6.0000000000000 21 --6.0000000000000 22 --6.0000000000000 23 --6.0000000000000 24 --6.0000000000000 25 --6.0000000000000 26 --6.000000000000 27 --6.000000000000 28 --6.000000000000 29 --6.00000000000 30 --6.00000000000 31 --6.00000000000 32 --6.00000000000 33 --6.0000000000 34 --6.0000000000 35 --6.0000000000 36 --6.000000000 37 --6.000000000 38 --6.000000000 39 /c -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sympy-issues?hl=en -~----------~----~----~----~------~----~------~--~---
