Changes between Initial Version and Version 1 of Ticket #15775, comment 1
- Timestamp:
- Apr 20, 2011, 3:11:04 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15775, comment 1
initial v1 1 The validation issue is a bug in `DecimalField`. `DecimalField` calls `value.as_tuple()` and unconditionally takes the absolute value of the third argument (`exponent`) as the number of decimal places. This is just wrong, because it's perfectly valid for exponent to be positive, and in that case it doesn't represent a number of decimal places at all, it represents trailing zeros.1 The validation issue is a bug in `DecimalField`. `DecimalField` calls `value.as_tuple()` and unconditionally takes the absolute value of the third element (`exponent`) as the number of decimal places. This is just wrong, because it's perfectly valid for exponent to be positive, and in that case it doesn't represent a number of decimal places at all, it represents trailing zeros. 2 2 3 3 The other issue (quantize error) I can't reproduce and I don't think is related. Please open as a separate ticket with full reproduction instructions (including version of Python, since that's an error coming directly from Python's decimal module).