➜
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.
Created on 2016-02-18 14:30 by florin.papa, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| decimal_csv_output.patch | florin.papa, 2016-02-18 14:30 | |||
| Messages (2) | |||
|---|---|---|---|
| msg260460 - (view) | Author: Florin Papa (florin.papa) * | Date: 2016-02-18 14:30 | |
Hi, This is Florin Papa from the Dynamic Scripting Languages Optimizations Team at Intel Corporation. This patch checks whether the benchmark measurement that will be included in the csv output has more than 3 of the first decimal places equal to 0 and outputs more decimal places. The problem is that each measurement in the csv output has only 6 decimal places (default for "%f" format), while some benchmarks, like unpack_sequence, will output values of the magnitude 0.0000xx (first four decimal places 0). This truncation of the original value can lead to incorrect results. |
|||
| msg276225 - (view) | Author: STINNER Victor (vstinner) *  |
Date: 2016-09-13 09:38 | |
Thanks for the bug report. The issue has been fixed in performance: https://github.com/python/performance/commit/2b63335248645ce7392c8cf835ef799d41beeeba |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:27 | admin | set | github: 70571 |
| 2016-09-13 09:38:47 | vstinner | set | status: open -> closed nosy: + vstinner messages: + msg276225 resolution: fixed |
| 2016-02-18 14:43:04 | vstinner | set | title: number of decimal places in csv output -> benchmarks (perf.py): number of decimal places in csv output |
| 2016-02-18 14:30:26 | florin.papa | create | |