<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/tests/unix/extra_coverage.py.exp, branch 6.0.x</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.0.x</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.0.x'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2019-05-06T21:19:07+00:00</updated>
<entry>
<title>Update tests for new autocomplete behavior</title>
<updated>2019-05-06T21:19:07+00:00</updated>
<author>
<name>Kathryn Lingel</name>
<email>kathryn@lingel.net</email>
</author>
<published>2019-05-06T21:19:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=77f177be9c52deea63de544701fa476239249dcd'/>
<id>urn:sha1:77f177be9c52deea63de544701fa476239249dcd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tests/unix/extra_coverage: Don't test stream objs with NULL write fun.</title>
<updated>2018-06-18T02:35:56+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-06-13T02:47:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=a5f5552a0a52cfd37f1db4d6df2194a4090561f5'/>
<id>urn:sha1:a5f5552a0a52cfd37f1db4d6df2194a4090561f5</id>
<content type='text'>
This behaviour of a NULL write C method on a stream that uses the write
adaptor objects is no longer supported.  It was only ever used by the
coverage build for testing the fail path of mp_get_stream_raise().
</content>
</entry>
<entry>
<title>tests/unix: Add coverage test for uio.resource_stream from frozen str.</title>
<updated>2018-03-03T12:58:03+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-03-03T12:58:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=512f4a6ad1c495760b50eca1bdee60314814b077'/>
<id>urn:sha1:512f4a6ad1c495760b50eca1bdee60314814b077</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tests: Move heap-realloc-while-locked test from C to Python.</title>
<updated>2018-03-01T23:59:09+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-03-01T23:59:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=c607b58efe9333ab92e1b721dcd974e35a9d393e'/>
<id>urn:sha1:c607b58efe9333ab92e1b721dcd974e35a9d393e</id>
<content type='text'>
This test for calling gc_realloc() while the GC is locked can be done in
pure Python, so better to do it that way since it can then be tested on
more ports.
</content>
</entry>
<entry>
<title>tests/unix: Add coverage tests for various GC calls.</title>
<updated>2018-03-01T11:49:15+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-03-01T11:49:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=c3f1b2233865f4e7f3016ca22a65ef9f4d4ec4db'/>
<id>urn:sha1:c3f1b2233865f4e7f3016ca22a65ef9f4d4ec4db</id>
<content type='text'>
</content>
</entry>
<entry>
<title>py/formatfloat: Fix rounding of %f format with edge-case FP values.</title>
<updated>2018-03-01T04:51:03+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-03-01T04:47:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=bc12eca461a317df842ce2e616afa97670cd0ce3'/>
<id>urn:sha1:bc12eca461a317df842ce2e616afa97670cd0ce3</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>tests/unix: Add coverage test for VM executing invalid bytecode.</title>
<updated>2018-02-27T05:18:11+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-02-27T05:17:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=d3cac18d4914af4549437ef3fd0d62f1fc05ff27'/>
<id>urn:sha1:d3cac18d4914af4549437ef3fd0d62f1fc05ff27</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tests/unix: Add coverage tests for mpz_set_from_float, mpz_mul_inpl.</title>
<updated>2018-02-25T12:43:16+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-02-25T12:43:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=62be14d77c1c61c7636e9ffe6b7e0c744ace58c6'/>
<id>urn:sha1:62be14d77c1c61c7636e9ffe6b7e0c744ace58c6</id>
<content type='text'>
These new tests cover cases that can't be reached from Python and get
coverage of py/mpz.c to 100%.

These "unreachable from Python" pieces of code could be removed but they
form an integral part of the mpz C API and may be useful for non-Python
usage of mpz.
</content>
</entry>
<entry>
<title>py/repl: Generalise REPL autocomplete to use qstr probing.</title>
<updated>2018-02-19T05:12:44+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-02-15T07:12:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=165aab12a3918004325238c794e27e7f4adbb401'/>
<id>urn:sha1:165aab12a3918004325238c794e27e7f4adbb401</id>
<content type='text'>
This patch changes the way REPL autocomplete finds matches.  It now probes
the target object for all qstrs via mp_load_method_maybe to look for a
match with the given input string.  Similar to how the builtin dir()
function works, this new algorithm now find all methods and instances of
user-defined classes including attributes of their parent classes.  This
helps a lot at the REPL prompt for user-discovery and to autocomplete names
even for classes that are derived.

The downside is that this new algorithm is slower than the previous one,
and in particular will be slower the more qstrs there are in the system.
But because REPL autocomplete is primarily used in an interactive way it is
not that important to make it fast, as long as it is "fast enough" compared
to human reaction.

On a slow microcontroller (CPU running at 16MHz) the autocomplete time for
a list of 35 names in the outer namespace (pressing tab at a bare prompt)
takes about 160ms with this algorithm, compared to about 40ms for the
previous implementation (this time includes the actual printing of the
names as well).  This time of 160ms is very reasonable especially given the
new functionality of listing all the names.

This patch also decreases code size by:

   bare-arm:    +0
minimal x86:  -128
   unix x64:  -128
unix nanbox:  -224
      stm32:   -88
     cc3200:   -80
    esp8266:   -92
      esp32:   -84
</content>
</entry>
<entry>
<title>tests/unix: Add coverage test for calling mp_obj_new_bytearray.</title>
<updated>2018-02-08T00:14:30+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2018-02-08T00:14:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=923ebe767d2ba8c4534560dc21d3533c37a3f831'/>
<id>urn:sha1:923ebe767d2ba8c4534560dc21d3533c37a3f831</id>
<content type='text'>
</content>
</entry>
</feed>
