Get the sources
Developp, test, debug, test, ... :)
When your modification is functional, you are ready to submit a patch
Sync you repository :
hg pull https://code.google.com/p/python-openzwave/
hg update
Generate the patch
hgdiff > somewordstoexplainwhatthepatchdoes.patch
As the code of python-openzwave is under developpment, submit atomic patches. Otherwise, you should have merge problems when syncing your repository.
This will generate a file in the current directory. Send it to the developpers team.
Contact the developpers for more informations.
Documentation is managed with sphinx. Don’t utpdate txt files (README, INSTALL, ...) , update the sources (*.rst) in docs. Use the following commands to generate all docs files (txt, html and joomla)
./make_docs.sh
If you want to package python-openzwave for your distribution, look at the make_dist.sh script. It build a distribution directory with documentation in build/distdir.
You can also submit your script here, they will be added to the main code.
You can build python-openzwave using
Remove the old py-openzwave
find /usr -iname openzwave.so
This command show the list of files naming openzwave.so in /usr, ie /usr/local/lib/python2.7/dist-package/openzwave.so
Remove it :
sudo rm /usr/local/lib/python2.7/dist-package/openzwave.so
Install the new version of python-openzwave : look at README
Update your code :
Everywhere in your code replace :
“import openzwave” to “import libopenzwave” “from openzwave” to “from libopenzwave”
notifications :
In Maarten py-openzwave librairy, value is a string but in python-openzwave, it’s a value of the right type :
# ‘value’ : value.c_str(),
‘value’ : getValueFromType(manager,v.GetId?()),
wrapper : The wrapper is no longer supported. Now high level acces to ZWave network is provided by the API (work in progress)
The original script was from maarten damen : https://github.com/maartendamen/python-openzwave