Skip to content

Latest commit

 

History

History
 
 

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
	
  <div class="section" id="python-openzwave">
<h1>python-openzwave</h1>
<p>python-openzwave is a python wrapper for the openzwave c++ library : <a class="reference external" href="https://github.com/OpenZWave/open-zwave">https://github.com/OpenZWave/open-zwave</a></p>
<blockquote>
<div><ul class="simple">
<li>full manager implementation with options</li>
<li>an API to map the ZWave network in Python objects</li>
<li>a command line manager to manage / debug your ZWave network</li>
<li>a full-event webapp example : flask + socket.io + jquery</li>
<li>a suite of tests</li>
<li>many examples</li>
</ul>
</div></blockquote>
<div class="section" id="python-openzwave-0-3-0-b7-is-out">
<h2>python-openzwave 0.3.0-b7 is out !!!</h2>
<p>Look at CHANGELOG to see new features and release notes.</p>
<p>Look at INSTALL_REPO to test it now</p>
<p>Look at INSTALL_ARCH to install from archive : no need to install cython anymore</p>
</div>
<div class="section" id="support">
<h2>Support</h2>
<p>You can ask for support on the google group : <a class="reference external" href="http://groups.google.com/d/forum/python-openzwave-discuss">http://groups.google.com/d/forum/python-openzwave-discuss</a>.</p>
<p>Please don&#8217;t ask for support in github issues or by email.</p>
</div>
<div class="section" id="pull-requests">
<h2>Pull requests</h2>
<p>Please read DEVEL documentation before submitting pull request.
A lot of project tasks are done automatically or with makefile, so they must be done in a certain place or in a special order.</p>
</div>
<div class="section" id="migrating-from-python-openzwave-0-2-x-to-0-3-0">
<h2>Migrating from python-openzwave 0.2.X to 0.3.0</h2>
<p>I need to update source tree of python-openzwave and modules&#8217;s names because of a bug in setuptools : <a class="reference external" href="https://bitbucket.org/pypa/setuptools/issue/230/develop-mode-does-not-respect-src">https://bitbucket.org/pypa/setuptools/issue/230/develop-mode-does-not-respect-src</a> .
Sorry for that.</p>
<p>Update your sources:</p>
<div class="highlight-bash"><div class="highlight"><pre>git pull
</pre></div>
</div>
<p>Before building python-openzwave 0.3.0, you must uninstall the old version :</p>
<div class="highlight-bash"><div class="highlight"><pre>sudo make uninstall
</pre></div>
</div>
<p>About cython : I&#8217;ve made many tests using cython installed via pip : (0.20, 0.21 and 0.22).
Compilation is ok but a segfault appears when launching the tests. Please remove it.</p>
<div class="highlight-bash"><div class="highlight"><pre>sudo pip uninstall Cython
</pre></div>
</div>
<p>You also need to make some minor updates in you code, look at CHANGELOG</p>
<p>If you have problems, please submit an issue with :</p>
<blockquote>
<div><ul class="simple">
<li>cython -V</li>
<li>the content of the directory /usr/local/lib/python2.7/dist-packages/ (for python2.7)</li>
<li>the content of /usr/local/lib/python2.7/dist-packages/easy-install.pth (for python 2.7)</li>
</ul>
</div></blockquote>
</div>
<div class="section" id="ubuntu-64bits-and-the-others">
<h2>Ubuntu 64bits ... and the others</h2>
<p>If you&#8217;re using Ubuntu 64 bits (and mayde others) and keep your distribution up to date,
you certainly have the segfault problem.</p>
<p>It appears with the last update of python :</p>
<div class="highlight-bash"><div class="highlight"><pre><span class="nv">$ </span>python
Python 2.7.6 <span class="o">(</span>default, Jun 22 2015, 17:58:13<span class="o">)</span>
<span class="o">[</span>GCC 4.8.2<span class="o">]</span> on linux2
Type <span class="s2">&quot;help&quot;</span>, <span class="s2">&quot;copyright&quot;</span>, <span class="s2">&quot;credits&quot;</span> or <span class="s2">&quot;license&quot;</span> <span class="k">for </span>more information.
</pre></div>
</div>
<p>I&#8217;ve open a discussion on cython-users here : <a class="reference external" href="https://groups.google.com/forum/#!topic/cython-users/mRsviGuCFOk">https://groups.google.com/forum/#!topic/cython-users/mRsviGuCFOk</a></p>
<p>The only way I found to avoid this is to rebuild and reinstall the old release of python :</p>
<div class="highlight-bash"><div class="highlight"><pre>wget https://launchpad.net/ubuntu/+archive/primary/+files/python2.7_2.7.6-8.dsc https://launchpad.net/ubuntu/+archive/primary/+files/python2.7_2.7.6.orig.tar.gz https://launchpad.net/ubuntu/+archive/primary/+files/python2.7_2.7.6-8.diff.gz

dpkg-source -x python2.7_2.7.6-8.dsc

sudo apt-get build-dep python2.7

<span class="nb">cd </span>python2.7-2.7.6

dpkg-buildpackage
</pre></div>
</div>
<p>Wait, wait and await again :)</p>
<div class="highlight-bash"><div class="highlight"><pre><span class="nb">cd</span> ..

sudo dpkg -i *.deb
</pre></div>
</div>
<p>To prevent future updates of python, you could mark its packages. For example, if you use apt to update your distribution, use the following command :</p>
<div class="highlight-bash"><div class="highlight"><pre>sudo apt-mark hold idle-python2.7 libpython2.7-minimal python2.7-dbg python2.7-minimal libpython2.7 libpython2.7-stdlib python2.7-dev libpython2.7-dbg  libpython2.7-testsuite python2.7-doc libpython2.7-dev python2.7 python2.7-examples
</pre></div>
</div>
<p>Some users have reported that building python-openzwave using the archive (INSTALL_ARCH) can also do the trick. Let me know if it works for you.</p>
</div>
</div>