<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openmano-mpy/docs/differences, 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>docs/differences: Clarify the differences are against Python 3.4.</title>
<updated>2019-01-11T01:11:02+00:00</updated>
<author>
<name>stijn</name>
</author>
<published>2019-01-10T09:07:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=5064df2074dfd8bdc61f16ab3cbc2d695c10c3a6'/>
<id>5064df2074dfd8bdc61f16ab3cbc2d695c10c3a6</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>reference/index: Rewrite introduction paragraph to avoid confusion.</title>
<updated>2017-07-01T19:09:40+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
</author>
<published>2017-07-01T19:09:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=8b7d31159506d1708c18704f4c8bda69dddcfdb8'/>
<id>8b7d31159506d1708c18704f4c8bda69dddcfdb8</id>
<content type='text'>
The old intro talked about "differences", but there were hardly any
sections describing differences, mostly MicroPython specific features.
On the other hand, we now have real "differences" chapter, though it's
mostly concerned with stdlib differences.

So, try to avoid confusion by changing wording and linking to the other
chapters and contrasting them with what is described in "MicroPython
language".
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The old intro talked about "differences", but there were hardly any
sections describing differences, mostly MicroPython specific features.
On the other hand, we now have real "differences" chapter, though it's
mostly concerned with stdlib differences.

So, try to avoid confusion by changing wording and linking to the other
chapters and contrasting them with what is described in "MicroPython
language".
</pre>
</div>
</content>
</entry>
<entry>
<title>docs/differences/index_template: Use consistent heading casing.</title>
<updated>2017-07-01T18:15:43+00:00</updated>
<author>
<name>Paul Sokolovsky</name>
</author>
<published>2017-07-01T18:15:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=50eea2614510b87031fed60bdab40e5b878fef70'/>
<id>50eea2614510b87031fed60bdab40e5b878fef70</id>
<content type='text'>
And in our case, "consistent" is where each word in the heading is *not*
capitalized.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
And in our case, "consistent" is where each word in the heading is *not*
capitalized.
</pre>
</div>
</content>
</entry>
<entry>
<title>tools: Add gen-cpydiff.py to generate docs differences.</title>
<updated>2017-02-20T06:14:34+00:00</updated>
<author>
<name>Rami Ali</name>
</author>
<published>2017-02-07T05:43:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/openmano-mpy/commit/?id=b7fa63c7ced460fd2d3aceb35257a62ff08831c1'/>
<id>b7fa63c7ced460fd2d3aceb35257a62ff08831c1</id>
<content type='text'>
This patch introduces the a small framework to track differences between
uPy and CPython.  The framework consists of:

- A set of "tests" which test for an individual feature that differs between
  uPy and CPy.  Each test is like a normal uPy test in the test suite, but
  has a special comment at the start with some meta-data: a category (eg
  syntax, core language), a human-readable description of the difference, a
  cause, and a workaround.  Following the meta-data there is a short code
  snippet which demonstrates the difference.  See tests/cpydiff directory
  for the initial set of tests.

- A program (this patch) which runs all the tests (on uPy and CPy) and
  generates nicely-formated .rst documenting the differences.

- Integration into the docs build so that everything is automatic, and the
  differences appear in a way that is easy for users to read/reference (see
  latter commits).

The idea with using this new framework is:

- When a new difference is found it's easy to write a short test for it,
  along with a description, and add it to the existing ones.  It's also easy
  for contributors to submit tests for differences they find.

- When something is no longer different the tool will give an error and
  difference can be removed (or promoted to a proper feature test).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch introduces the a small framework to track differences between
uPy and CPython.  The framework consists of:

- A set of "tests" which test for an individual feature that differs between
  uPy and CPy.  Each test is like a normal uPy test in the test suite, but
  has a special comment at the start with some meta-data: a category (eg
  syntax, core language), a human-readable description of the difference, a
  cause, and a workaround.  Following the meta-data there is a short code
  snippet which demonstrates the difference.  See tests/cpydiff directory
  for the initial set of tests.

- A program (this patch) which runs all the tests (on uPy and CPy) and
  generates nicely-formated .rst documenting the differences.

- Integration into the docs build so that everything is automatic, and the
  differences appear in a way that is easy for users to read/reference (see
  latter commits).

The idea with using this new framework is:

- When a new difference is found it's easy to write a short test for it,
  along with a description, and add it to the existing ones.  It's also easy
  for contributors to submit tests for differences they find.

- When something is no longer different the tool will give an error and
  difference can be removed (or promoted to a proper feature test).
</pre>
</div>
</content>
</entry>
</feed>
