1. 29 Aug, 2015 9 commits
  2. 28 Aug, 2015 2 commits
  3. 25 Aug, 2015 1 commit
  4. 22 Aug, 2015 2 commits
  5. 21 Aug, 2015 2 commits
  6. 19 Aug, 2015 1 commit
  7. 17 Aug, 2015 4 commits
    • Damien George's avatar
    • Paul Sokolovsky's avatar
    • tobbad's avatar
      stmhal: Fixed some typos in stm32f411_af.csv. · 1abb449d
      tobbad authored
      1abb449d
    • Damien George's avatar
      unix-cpy: Remove unix-cpy. It's no longer needed. · 65dc960e
      Damien George authored
      unix-cpy was originally written to get semantic equivalent with CPython
      without writing functional tests.  When writing the initial
      implementation of uPy it was a long way between lexer and functional
      tests, so the half-way test was to make sure that the bytecode was
      correct.  The idea was that if the uPy bytecode matched CPython 1-1 then
      uPy would be proper Python if the bytecodes acted correctly.  And having
      matching bytecode meant that it was less likely to miss some deep
      subtlety in the Python semantics that would require an architectural
      change later on.
      
      But that is all history and it no longer makes sense to retain the
      ability to output CPython bytecode, because:
      
      1. It outputs CPython 3.3 compatible bytecode.  CPython's bytecode
      changes from version to version, and seems to have changed quite a bit
      in 3.5.  There's no point in changing the bytecode output to match
      CPython anymore.
      
      2. uPy and CPy do different optimisations to the bytecode which makes it
      harder to match.
      
      3. The bytecode tests are not run.  They were never part of Travis and
      are not run locally anymore.
      
      4. The EMIT_CPYTHON option needs a lot of extra source code which adds
      heaps of noise, especially in compile.c.
      
      5. Now that there is an extensive test suite (which tests functionality)
      there is no need to match the bytecode.  Some very subtle behaviour is
      tested with the test suite and passing these tests is a much better
      way to stay Python-language compliant, rather than trying to match
      CPy bytecode.
      65dc960e
  8. 16 Aug, 2015 12 commits
  9. 15 Aug, 2015 1 commit
  10. 14 Aug, 2015 1 commit
    • stijn's avatar
      windows: Make unistd.h more posix compatible · 3179d23c
      stijn authored
      - add SEEK_XXX definitions, this fixes missing definition in py/stream.c
      - move R_OK from realpath.c and add W_OK/F_OK defintions
      - move STDXXX_FILENO definitions from mpconfigport for consistency
      3179d23c
  11. 13 Aug, 2015 1 commit
  12. 12 Aug, 2015 2 commits
  13. 11 Aug, 2015 2 commits