<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/windows, branch v1.6</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.6</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.6'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2016-01-29T00:13:42+00:00</updated>
<entry>
<title>py/runtime: mp_stack_ctrl_init() should be called immediately on startup.</title>
<updated>2016-01-29T00:13:42+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2016-01-28T23:05:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=d3b1f0b627ccc6705d9fe958549badb87a74ded1'/>
<id>urn:sha1:d3b1f0b627ccc6705d9fe958549badb87a74ded1</id>
<content type='text'>
Calling it from mp_init() is too late for some ports (like Unix), and leads
to incomplete stack frame being captured, with following GC issues. So, now
each port should call mp_stack_ctrl_init() on its own, ASAP after startup,
and taking special precautions so it really was called before stack variables
get allocated (because if such variable with a pointer is missed, it may lead
to over-collecting (typical symptom is segfaulting)).
</content>
</entry>
<entry>
<title>windows/msvc: Add modurandom.c to list of source files.</title>
<updated>2016-01-26T19:38:59+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2016-01-26T19:38:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=e713222fabe1c3987364870ed592db38529bc4a3'/>
<id>urn:sha1:e713222fabe1c3987364870ed592db38529bc4a3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>windows: Enable urandom module.</title>
<updated>2016-01-26T15:27:00+00:00</updated>
<author>
<name>Damien George</name>
<email>damien.p.george@gmail.com</email>
</author>
<published>2016-01-24T19:48:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=d22bdad6ddd53f690a8c27b9493e6531cb59f0a2'/>
<id>urn:sha1:d22bdad6ddd53f690a8c27b9493e6531cb59f0a2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>windows: Propagate MICROPY_PY_OS_DUPTERM handling from unix port.</title>
<updated>2015-12-27T23:30:58+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2015-12-27T23:30:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=1e06e81b3d32b3f0bc775e0e4ed2d0251a95f53e'/>
<id>urn:sha1:1e06e81b3d32b3f0bc775e0e4ed2d0251a95f53e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>windows/msvc: Nicer handling of asserts and 'invalid' parameters</title>
<updated>2015-12-26T22:14:16+00:00</updated>
<author>
<name>stijn</name>
<email>stijn@ignitron.net</email>
</author>
<published>2015-12-24T14:48:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=1aa4599ddd7ad9ea28bf4dd7a9a5d813f93584be'/>
<id>urn:sha1:1aa4599ddd7ad9ea28bf4dd7a9a5d813f93584be</id>
<content type='text'>
The default bahaviour for debug builds is to show dialog boxes for asserts
and invalid parameter handling. This is not so nice in general and causes
the Appveyor debug builds to hang because the io\file_seek.py test passes
a closed file descriptor to lseek. Disable this behaviour by printing
assert messages to the output instead of showing the dialog, and by
disabling 'invalid' parameter handling which causes the affected functions
to just return an error and set errno appropriately.
</content>
</entry>
<entry>
<title>windows: Better handling of Ctrl-C</title>
<updated>2015-12-21T18:51:27+00:00</updated>
<author>
<name>stijn</name>
<email>stijn@ignitron.net</email>
</author>
<published>2015-12-21T09:17:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=a5aa03acaff46aaaac0d0c3462cbd968b0a1df59'/>
<id>urn:sha1:a5aa03acaff46aaaac0d0c3462cbd968b0a1df59</id>
<content type='text'>
This builds upon the changes made in 2195046365c. Using signal() does not
produce reliable results so SetConsoleCtrlHandler is used, and the handler
is installed only once during initialization instead of removing it in
mp_hal_set_interrupt_char when it is not strictly needed anymore, since
removing it might lead to Ctrl-C events being missed because they are
fired on a seperate thread which might only become alive after the handler
was removed.
</content>
</entry>
<entry>
<title>windows: Add Appveyor CI builds for msvc port.</title>
<updated>2015-12-18T21:49:35+00:00</updated>
<author>
<name>stijn</name>
<email>stijn@ignitron.net</email>
</author>
<published>2015-12-17T09:24:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=da199e4407f38c170179c33aef862fd5109145e2'/>
<id>urn:sha1:da199e4407f38c170179c33aef862fd5109145e2</id>
<content type='text'>
Appveyor is like Travis, but for Windows builds. The appveyor.yml configuration
will build the msvc port in all configuration/platform conbinations,
and run the tests for each of those.
</content>
</entry>
<entry>
<title>msvc: Add dirent.h/.c implementation</title>
<updated>2015-12-18T20:10:51+00:00</updated>
<author>
<name>stijn</name>
<email>stijn@ignitron.net</email>
</author>
<published>2015-12-16T11:25:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=c5f52b845b62e1562ca48943f1bab03a8da99059'/>
<id>urn:sha1:c5f52b845b62e1562ca48943f1bab03a8da99059</id>
<content type='text'>
This fixes the build after adding directory iteration in d874702
</content>
</entry>
<entry>
<title>windows/windows_mphal: Add basic support for raising KeyboardInterrupt.</title>
<updated>2015-12-17T23:12:59+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2015-12-17T23:10:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=2195046365c661551c30d4156cecafa603214375'/>
<id>urn:sha1:2195046365c661551c30d4156cecafa603214375</id>
<content type='text'>
Compiles with mingw32, tested to work erratically under Wine due to
not fully implemented emulation in it.
</content>
</entry>
<entry>
<title>windows: Make keyboard_interrupt_obj available, it's standard feature.</title>
<updated>2015-12-17T23:07:27+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
<email>pfalcon@users.sourceforge.net</email>
</author>
<published>2015-12-17T22:47:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=5efd3f0dcac6e2f3f33c3edce7d3f2974bbf8e78'/>
<id>urn:sha1:5efd3f0dcac6e2f3f33c3edce7d3f2974bbf8e78</id>
<content type='text'>
</content>
</entry>
</feed>
