suspect-devices/circuitpython/tests/float, branch mainCircuitPython - a Python implementation for teaching coding with microcontrollershttps://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=main2021-03-15T13:57:36+00:00run code formatting script2021-03-15T13:57:36+00:00microDev70126934+microDev1@users.noreply.github.com2021-03-15T13:57:36+00:00urn:sha1:a52eb88031620a81521b937f2a0651dbac2bb350Fix up end of file and trailing whitespace.2020-06-03T09:56:35+00:00Diego Elio Pettenòflameeyes@flameeyes.com2020-05-30T09:44:13+00:00urn:sha1:dd5d7c86d22807c021dd1711eb7dd3daebc5cfcf
This can be enforced by pre-commit, but correct it separately to make it easier to review.
py/lexer: Add support for underscores in numeric literals.2018-06-12T02:17:43+00:00Damien Georgedamien.p.george@gmail.com2018-06-01T14:21:46+00:00urn:sha1:6a445b60fad87c94a1d00ce3a043b881a1f7a5a4
This is a very convenient feature introduced in Python 3.6 by PEP 515.
tests: Add some tests for bigint hash, float hash and float parsing.2018-05-21T03:05:40+00:00Damien Georgedamien.p.george@gmail.com2018-05-21T03:05:40+00:00urn:sha1:1ad0013decb42418ca667c2d9994198b537fa778
Following outcome of recent fuzz testing and sanitizing by @jepler.
tests/float/float_parse: Allow test to run on 32-bit archs.2018-05-11T03:51:18+00:00Damien Georgedamien.p.george@gmail.com2018-05-11T03:51:18+00:00urn:sha1:d2c1db1e5cca03c9a34614af6d12045aefe3d719
Printing of uPy floats can differ by the floating-point precision on
different architectures (eg 64-bit vs 32-bit x86), so it's not possible to
using printing of floats in some parts of this test. Instead we can just
check for equivalence with what is known to be the correct answer.
py/formatfloat: Fix case where floats could render with negative digits.2018-03-01T06:00:02+00:00Damien Georgedamien.p.george@gmail.com2018-03-01T06:00:02+00:00urn:sha1:955ee6477f4b1d3a70bfe97a1e7727848bf2d06d
Prior to this patch, some architectures (eg unix x86) could render floats
with "negative" digits, like ")". For example, '%.23e' % 1e-80 would come
out as "1.0000000000000000/)/(,*0e-80". This patch fixes the known cases.
py/formatfloat: Fix case where floats could render with a ":" character.2018-03-01T05:02:59+00:00Damien Georgedamien.p.george@gmail.com2018-03-01T05:02:59+00:00urn:sha1:7b050fa76c6a763043739d40c82dde839d7f8fd9
Prior to this patch, some architectures (eg unix x86) could render floats
with a ":" character in them, eg 1e+39 would come out as ":e+38" (":" is
just after "9" in ASCII so this is like 10e+38). This patch fixes some of
these cases.
py/formatfloat: Fix rounding of %f format with edge-case FP values.2018-03-01T04:51:03+00:00Damien Georgedamien.p.george@gmail.com2018-03-01T04:47:17+00:00urn:sha1:bc12eca461a317df842ce2e616afa97670cd0ce3
Prior to this patch the %f formatting of some FP values could be off by up
to 1, eg '%.0f' % 123 would return "122" (unix x64). Depending on the FP
precision (single vs double) certain numbers would format correctly, but
others wolud not. This patch should fix all cases of rounding for %f.
tests/float: Adjust float-parsing tests to pass with only a small error.2018-02-26T04:54:03+00:00Damien Georgedamien.p.george@gmail.com2018-02-26T04:54:03+00:00urn:sha1:6dad0885692f8d1e743873fb4be241f1fd1cb91a
Float parsing (both single and double precision) may have a relative error
of order the floating point precision, so adjust tests to take this into
account by not printing all of the digits of the answer.
py/objfloat: Fix case of raising 0 to -infinity.2018-02-08T03:35:43+00:00Damien Georgedamien.p.george@gmail.com2018-02-08T03:35:43+00:00urn:sha1:bbb08431f3c45d94c1e6aa0762b8f13ccce1fe8e
It was raising an exception but it should return infinity.