1. 22 Dec, 2016 1 commit
  2. 05 Dec, 2016 1 commit
    • Damien George's avatar
      travis: Build STM32 F7 and L4 boards under Travis CI. · 0db3a41f
      Damien George authored
      The STM32 F7 and L4 boards use significantly different code to the F4
      boards so it's important to test them with CI.  To keep CI build times
      within a reasonable limit the STM32F4DISC board is no longer built, it's
      anyway very similar to the standard F4 build for PYBv1.0.
      0db3a41f
  3. 25 Oct, 2016 2 commits
  4. 20 Sep, 2016 1 commit
  5. 10 Sep, 2016 1 commit
  6. 05 Sep, 2016 1 commit
  7. 09 Jul, 2016 1 commit
  8. 26 May, 2016 1 commit
  9. 03 Mar, 2016 1 commit
    • Paul Sokolovsky's avatar
      tarvis: Unbreak build by ignoring lack of i386 arch in some repos. · 701c4152
      Paul Sokolovsky authored
      For some reason, Travis now has Google Chrome PPA included in the builder
      image, that lacks i386 arch, that leads to apt-get update error. So, ignore
      it (this is not ideal as may lead to actual repo update failures to be missed,
      leading to installation of old package, leading to weird errors; let's keep
      that in mind).
      701c4152
  10. 17 Jan, 2016 1 commit
  11. 15 Jan, 2016 1 commit
  12. 19 Oct, 2015 1 commit
  13. 17 Aug, 2015 1 commit
    • 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
  14. 08 May, 2015 1 commit
  15. 07 May, 2015 1 commit
  16. 01 Mar, 2015 1 commit
  17. 27 Feb, 2015 1 commit
  18. 06 Feb, 2015 1 commit
    • danicampora's avatar
      cc3200: Add cc3200 port of MicroPython. · 8785645a
      danicampora authored
      The port currently implements support for GPIO, RTC, ExtInt and the WiFi
      subsystem. A small file system is available in the serial flash. A
      bootloader which makes OTA updates possible, is also part of this initial
      implementation.
      8785645a
  19. 14 Jan, 2015 1 commit
  20. 13 Jan, 2015 1 commit
  21. 12 Jan, 2015 1 commit
  22. 09 Jan, 2015 1 commit
  23. 30 Oct, 2014 1 commit
  24. 06 Oct, 2014 1 commit
  25. 29 Aug, 2014 1 commit
  26. 05 Aug, 2014 1 commit
  27. 25 Jun, 2014 1 commit
  28. 11 May, 2014 1 commit
  29. 21 Apr, 2014 1 commit
  30. 15 Apr, 2014 10 commits