<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openmano-mpy/lib/upytesthelper, branch master</title>
<subtitle>MicroPython source and hardware configuration for OpenMano</subtitle>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/'/>
<entry>
<title>py: Add global default_emit_opt variable to make emit kind persistent.</title>
<updated>2019-08-28T02:47:58+00:00</updated>
<author>
<name>Damien George</name>
</author>
<published>2019-08-23T01:20:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=af20c2ead3e9bb397fdf89e316aa78b56f165013'/>
<id>af20c2ead3e9bb397fdf89e316aa78b56f165013</id>
<content type='text'>
mp_compile no longer takes an emit_opt argument, rather this setting is now
provided by the global default_emit_opt variable.

Now, when -X emit=native is passed as a command-line option, the emitter
will be set for all compiled modules (included imports), not just the
top-level script.

In the future there could be a way to also set this variable from a script.

Fixes issue #4267.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
mp_compile no longer takes an emit_opt argument, rather this setting is now
provided by the global default_emit_opt variable.

Now, when -X emit=native is passed as a command-line option, the emitter
will be set for all compiled modules (included imports), not just the
top-level script.

In the future there could be a way to also set this variable from a script.

Fixes issue #4267.
</pre>
</div>
</content>
</entry>
<entry>
<title>lib/upytesthelper: MicroPython test helper layer on top of tinytest.</title>
<updated>2017-12-13T07:07:51+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
</author>
<published>2017-12-11T17:45:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=140bbced6f270d9baf3df3b725932ecbbd5a4577'/>
<id>140bbced6f270d9baf3df3b725932ecbbd5a4577</id>
<content type='text'>
Tinytest is classical assert-style framework, but MicroPython tests work
in different way - they produce content, and that content should be matched
against expected one to see if test passes. upytesthelper exactly adds
helper functions to make that possible.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Tinytest is classical assert-style framework, but MicroPython tests work
in different way - they produce content, and that content should be matched
against expected one to see if test passes. upytesthelper exactly adds
helper functions to make that possible.
</pre>
</div>
</content>
</entry>
</feed>
