Zack Williams | 50b6e9e | 2019-07-17 15:18:08 -0700 | [diff] [blame^] | 1 | PyVOLTHA |
| 2 | ======== |
| 3 | |
| 4 | PyVOLTHA is a collection of shared Python libraries that are use to |
| 5 | create Python-based |
| 6 | `VOLTHA <https://wiki.opencord.org/display/CORD/VOLTHA>`__ Device |
| 7 | Adapters and other Python utilities (CLI, …) that need to work with the |
| 8 | VOLTHA v2.0 and later Golang core. |
| 9 | |
| 10 | Initially PyVOLTHA will target only Python 2.7, but contributors are |
| 11 | encouraged to write or refactor any library methods to eventually |
| 12 | support Python 3.6.x or later. |
| 13 | |
| 14 | Installation instruction |
| 15 | ------------------------ |
| 16 | |
| 17 | .. code:: bash |
| 18 | |
| 19 | pip install pyvoltha |
| 20 | |
| 21 | Release History |
| 22 | --------------- |
| 23 | |
| 24 | +---------+------------+-----------------------------------------------+ |
| 25 | | Version | Date | Notes | |
| 26 | +=========+============+===============================================+ |
| 27 | | v0.1.0 | 2019-02-01 | Initial pypy release available. This is | |
| 28 | | | | primarily for testing out pip install support | |
| 29 | | | | and is not expected to be useful outside of | |
| 30 | | | | that. | |
| 31 | +---------+------------+-----------------------------------------------+ |
| 32 | |
| 33 | Detailed Release History |
| 34 | ~~~~~~~~~~~~~~~~~~~~~~~~ |
| 35 | |
| 36 | v0.1.0 (2019-02-01) |
| 37 | ^^^^^^^^^^^^^^^^^^^ |
| 38 | |
| 39 | - Experimental release of pyvoltha to test pip install capabilities. |
| 40 | This version has manually created protobuf definitions and will |
| 41 | probably not be very usable by any device adapters. |
| 42 | - This version is not under source control management at this time. |
| 43 | Initial VCS support is anticipated in the very near future when |
| 44 | portions of this project can be consumed by a device adapter |
| 45 | developer. |
| 46 | - Protobuf files in the ‘proto’ directory were hand copied over from |
| 47 | the voltha-go repository. These will eventually be in a separate repo |
| 48 | that developers will need to include. |
| 49 | - Most all import paths fixed but that does not mean everything works |
| 50 | - A fair number of original unit tests are working after import |
| 51 | changes. Others need work. |