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 | rhettinger |
|---|---|
| Recipients | davin, mark.dickinson, rhettinger, serhiy.storchaka, tim.peters |
| Date | 2017年10月01日.17:53:44 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1506880424.68.0.213398074469.issue31630@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I would have thought this would be a straight pass-through to the underlying hardware FPU tan() instruction so that it would give the same answer for the same hardware regardless of O/S. Perhaps we're seeing a software-only implementation (using CORDIC or somesuch). If so, inputs close to a singularity are the place where the implementation is likely to fall apart (the relative error in this example is 1.000004001955473). * https://www.gnu.org/software/libc/manual/html_node/Errors-in-Math-Functions.html * https://stackoverflow.com/questions/16880376/sin-cos-tan-not-accurate * http://code.activestate.com/recipes/576792-polar-to-rectangular-conversions-using-cordic/ |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017年10月01日 17:53:44 | rhettinger | set | recipients: + rhettinger, tim.peters, mark.dickinson, serhiy.storchaka, davin |
| 2017年10月01日 17:53:44 | rhettinger | set | messageid: <1506880424.68.0.213398074469.issue31630@psf.upfronthosting.co.za> |
| 2017年10月01日 17:53:44 | rhettinger | link | issue31630 messages |
| 2017年10月01日 17:53:44 | rhettinger | create | |