This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description
pyBox0
======

Python binding for libbox0

Dependencies
============

* cffi
* numpy

In C:

* libbox0
* libusb

Installation
============

$ python setup.py build
$ python setup.py install

Configuration
=============
in local.properties
_binding.py, build_path variable to tell where to look for header and library

Usage
=====

lots of demo code in test/ and example/
a generic approch to opening device and module and do something with them

import box0

# open any supported usb device
dev = box0.usb.open_supported()

# open the gpio0 module (assuming the device support it)
# if you need to iterate over the supported modules using dev
gpio0 = dev.gpio(0)

# set to output mode
gpio0.dir(0, gpio0.OUTPUT)

# set value of pin 0
gpio0.value(0, gpio0.LOW)

#disable hiz mode of pin 0,
# note: all pins are in hiz mode right after opening (for protection)
gpio0.hiz(0, gpio0.DISABLE)

// wait
try:
while True:
time.sleep(.5)
except:
pass

# close resources
gpio0.close()
dev.close()

Note
====
pyBox0 uses same style as libbox0 and
much of the documentation of libbox0 is applicable to pyBox0

int b0_<section>_<func>(<section-object>, params....)

in pyBox0:
instead of int, an exception (ResultException is raised) when int-val < 0
so, now the return value is used for other tasks

"b0" tag is now replace with "box0." as python have concept of modules

<section> is replace with files.
for example: <section> = "device" , theirs device.py
and it contain Device.py


<func> these are under-scored style name in libbox0
in pyBox0, camelcasing is used
for example b0_usb_open_supported() is box0.usb.open_supported()

most of the library assumes numpy array.
numpy is good and you should always use numpy with pyBox0 as
it much better in long run

Getting help
============

get on to #box0 on IRC freenode
and report bug on https://gitlab.com/madresistor/pyBox0

Getting involved
================

get on to #box0 on IRC freenode
and report bug on https://gitlab.com/madresistor/pyBox0

Licence
=======

GNU/GPLv3 or later (see COPYING)

Credits and references
======================

http://www.madresistor.org/

Maintainer
==========

Kuldeep Singh Dhaka <kuldeepdhaka9@gmail.com>
Release History

Release History

0.2.0

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
box0-0.2.0.tar.gz (52.5 kB) Copy SHA256 Checksum SHA256 Source Sep 28, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting