semvec/pypi-packages huggingface dataset:
xinabox-SL01 0.0.7
Light Sensor
Requires Python: >=3.6

[![GitHub Issues](https://img.shields.io/github/issues/xinabox/Python-SL01.svg)](https://github.com/xinabox/Python-SL01/issues)
![GitHub Commit](https://img.shields.io/github/last-commit/xinabox/Python-SL01)
![Maintained](https://img.shields.io/maintenance/yes/2020)
![Build status badge](https://github.com/xinabox/Python-SL01/workflows/Python/badge.svg)
![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)

# Python-SL01

The SL01 xChip is a UV radiation and ambient light level sensor. It is based on the VEML6075 and TSL4531. VEML6075 on the SL01 is capable of measuring UVA and UVB radiation, in turn, providing an acccurate UV Index. TSL4531 is a light sensor that is capable of measuring the luminosity (Wide Dynamic Range â€” 3 lux to 220k lux) (visual brightness).

# Usage

## Mu-editor
Download [Mu-editor](https://github.com/xinabox/mu-editor/releases/tag/v1.1.0a2)

### CW01 and CW02
- Use [XinaBoxUploader](https://github.com/xinabox/XinaBoxUploader/releases/latest) and flash MicroPython to the CW01/CW02.
- Download Python packages from the REPL with the following code:
    ```python
    import network
    import upip
    sta_if = network.WLAN(network.STA_IF)
    sta_if.active(True)
    sta_if.connect("ssid", "password")
    upip.install("xinabox-SL01")
    ```

### CC03, CS11 and CW03
- Download the .UF2 file for CC03/CS11/CW03 [CircuitPython](https://circuitpython.org/board/xinabox_cs11/) and flash it to the board.
- TO DO

### MicroBit
- TO DO

## Raspberry Pi

Requires Python 3
```
pip3 install xinabox-SL01
```

# Example
```python
from xCore import xCore
from xSL01 import xSL01

SL01 = xSL01()

while True:
    print(SL01.getUVA())
    print(SL01.getUVB())
    print(SL01.getUVIndex())
    print(SL01.getLUX())
    xCore.sleep(1000)
```
fetchai-ledger-api 1.1.0
Tools and utilities for interacting with the ledger on the fetch network
Requires Python: >=3.5

# Ledger Python API
![](https://github.com/fetchai/ledger-api-py/workflows/CI/badge.svg)
![](https://img.shields.io/pypi/v/fetchai-ledger-api)
![](https://img.shields.io/github/release-date/fetchai/ledger-api-py)
![](https://img.shields.io/pypi/pyversions/fetchai-ledger-api)

Python library code for interacting with the Fetch.ai ledger platform.

## Installation

    $ pip3 -U fetchai-ledger-api

## Examples

The project is a component of a larger ecosystem of projects for developing on the Fetch.ai's platform. Please check out some of the links below:

- [Developer Portal](https://developer.fetch.ai/)
- [Repo Examples](https://github.com/fetchai/ledger-api-py/tree/master/examples)

## Developing with the library

Make sure that the library is uninstalled from the system (or use a virtualenv) then use the following commnad:

    $ python3 setup.py develop

## Running the unit tests

The project uses pytest for running the unit tests. Simple run the following command to exectute all the of tests

    $ pytest

## License

This application is licensed under the Apache software license (see LICENSE file). Unless required by
applicable law or agreed to in writing, software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

Fetch.AI makes no representation or guarantee that this software (including any third-party libraries)
will perform as intended or will be free of errors, bugs or faulty code. The software may fail which
could completely or partially limit functionality or compromise computer systems. If you use or
implement the ledger, you do so at your own risk. In no event will Fetch.ai be liable to any party
for any damages whatsoever, even if it had been advised of the possibility of damage.
xinabox-SL06 0.0.9
Proximity, gesture, light and colour sensor
Requires Python: >=3.6

[![GitHub Issues](https://img.shields.io/github/issues/xinabox/Python-SL06.svg)](https://github.com/xinabox/Python-SL06/issues)
![GitHub Commit](https://img.shields.io/github/last-commit/xinabox/Python-SL06)
![Maintained](https://img.shields.io/maintenance/yes/2020)
![Build status badge](https://github.com/xinabox/Python-SL06/workflows/Python/badge.svg)
![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)

# Python-SL06

The SL06 xChip features advanced Gesture detection, Proximity detection, Digital Ambient Light Sense (ALS) and Colour Sense (RGBC). It is based on the popular APDS9960 manufactured by Avago Technologies.

# Usage

## Mu-editor
Download [Mu-editor](https://github.com/xinabox/mu-editor/releases/tag/v1.1.0a2)

### CW01 and CW02
- Use [XinaBoxUploader](https://github.com/xinabox/XinaBoxUploader/releases/latest) and flash MicroPython to the CW01/CW02.
- Download Python packages from the REPL with the following code:
    ```python
    import network
    import upip
    sta_if = network.WLAN(network.STA_IF)
    sta_if.active(True)
    sta_if.connect("ssid", "password")
    upip.install("xinabox-SL06")
    ```

### CC03, CS11 and CW03
- Download the .UF2 file for CC03/CS11/CW03 [CircuitPython](https://circuitpython.org/board/xinabox_cs11/) and flash it to the board.
- TO DO

### MicroBit
- TO DO

## Raspberry Pi

Requires Python 3
```
pip3 install xinabox-SL06
```

# Example
```python
from xCore import xCore
from xSL06 import xSL06

# SL06 instance
SL06 = xSL06()

# configure SL06
SL06.init()

# enable SL06 for gesture sensing
SL06.enableGestureSensor()

while True:
    if SL06.isGestureAvailable():   # check for gesture
        dir = SL06.getGesture()     # read direction
        print(dir)                  # print direction on console

    xCore.sleep(100)
```
ya-client-payment 0.1.0
Yagna Payment API
Keywords: OpenAPI,OpenAPI-Generator,Yagna Payment API

Invoicing and Payments is a fundamental area of Yagna Ecosystem functionality. It includes aspects of communication between Requestor, Provider and a selected Payment Platform, which becomes crucial when Activities are executed in the context of negotiated Agreements. Yagna applications must be able to exercise various payment models, and the Invoicing/Payment-related communication is happening in parallel to Activity control communication. To define functional patterns of Requestor/Provider interaction in this area, Payment API is specified.  An important principle of the Yagna Payment API is that the actual payment transactions are hidden behind the Invoice flow. In other words, a Yagna Application on Requestor side isn’t expected to trigger actual payment transactions. Instead it is expected to receive and accept Invoices raised by the Provider - based on Application’s Invoice Accept notifications, the Payment API implementation orchestrates the payment via a configured Payment platform.  **NOTE: This specification is work-in-progress.**   # noqa: E501