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 | ocean-city |
|---|---|
| Recipients | facundobatista, ocean-city |
| Date | 2007年09月23日.18:47:50 |
| SpamBayes Score | 0.070917964 |
| Marked as misclassified | No |
| Message-id | <1190573270.96.0.3765331284.issue1182@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I tracked down, and I noticed following code was invoked. Lib/decimal.py (release-maint25 Decimal#_rescale) 1912: if watchexp and digits > context.prec: 1913: return context._raise_error(InvalidOperation, 'Rescale > prec') from decimal import * d = Decimal("23.08589694291355371979265447") print d % Decimal("2.302585092994045640179914546844") # NaN print Decimal("0.060046012973097317993509001560")._rescale(-30) # error Length of decimal seems to be important, so I changed length and it seemed working. print d % Decimal("2.302585092994045640179914547") # 0.060046012973097317993509000 Maybe is this intended behavior? Still I feel 2.6's behavior is less suprising though... |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月23日 18:47:51 | ocean-city | set | spambayes_score: 0.070918 -> 0.070917964 recipients: + ocean-city, facundobatista |
| 2007年09月23日 18:47:50 | ocean-city | set | spambayes_score: 0.070918 -> 0.070918 messageid: <1190573270.96.0.3765331284.issue1182@psf.upfronthosting.co.za> |
| 2007年09月23日 18:47:50 | ocean-city | link | issue1182 messages |
| 2007年09月23日 18:47:50 | ocean-city | create | |