X-Git-Url: https://git.ayoreis.com/hackapet/Adafruit_Blinka.git/blobdiff_plain/75ae0e97611f429f15c02c2b58254be6533419a0..4f258c680ca0ae5fefc416eb72a544a39289bc0d:/README.rst diff --git a/README.rst b/README.rst old mode 100644 new mode 100755 index a018d69..07266d7 --- a/README.rst +++ b/README.rst @@ -9,54 +9,51 @@ Introduction :target: https://discord.gg/nBQh6qu :alt: Discord -.. image:: https://travis-ci.org/adafruit/Adafruit_Micropython_Blinka.svg?branch=master - :target: https://travis-ci.org/adafruit/Adafruit__Micropython_Blinka +.. image:: https://travis-ci.com/adafruit/Adafruit_Blinka.svg?branch=master + :target: https://travis-ci.com/adafruit/Adafruit_Blinka :alt: Build Status -Description -=========== - This repository contains a selection of packages mirroring the CircuitPython API -on hosts running micropython. At the time of writing drafts exist for +on hosts running micropython. Working code exists to emulate the CircuitPython packages; -* board - breakout-specific pin identities -* microcontroller - chip-specific pin identities -* digitalio - digital input/output pins, using pin identities from board/microcontroller +* **board** - breakout-specific pin identities +* **microcontroller** - chip-specific pin identities +* **analogio** - analog input/output pins, using pin identities from board+microcontroller packages +* **digitalio** - digital input/output pins, using pin identities from board+microcontroller packages +* **bitbangio** - software-driven interfaces for I2C, SPI +* **busio** - hardware-driven interfaces for I2C, SPI, UART +* **time** * - substitute functions monkey-patched to time module Dependencies ============= -The CircuitPython compatibility layers described above are intended for devices which -are running Micropython. Given the top level packages should be provided by any standard -CircuitPython image, you shouldn't be trying to put those packages on any board -with CircuitPython already installed. - -However, the test suites under testing.implementation.all are by design -intended to run on either CircuitPython or the Micropython+compatibility layer, so that -conformance can be achieved. - -Similarly the test suites under testing.implementation.micropython should only be run -on Micropython and testing.implementation.circuitpython should only be run on CircuitPython +The Micropython compatibility layers described above are intended to provide a CircuitPython-like API for devices which +are running CPython or Micropython. Since corresponding packages should be built-in to any standard +CircuitPython image, they have no value on a device already running CircuitPython and would likely conflict in unhappy ways. +The test suites in the test/src folder under **testing.universal** are by design +intended to run on *either* CircuitPython *or* Micropython+compatibility layer to prove conformance. Usage Example ============= -At the time of writing `git:3b2fc268 `, -the following sequence runs through some basic testing of the digitalio compatibility layer. +At the time of writing (`git:7fc1f8ab `_), +the following sequence runs through some basic testing of the digitalio compatibility layer... .. code-block:: python - import testing - testing.main() + from testing import test_module_name + test_module_name("testing.universal.digitalio") + +An example log from running the suites is `here `_ . Contributing ============ Contributions are welcome! Please read our `Code of Conduct -`_ +`_ before contributing to help this project stay welcoming. Building locally