jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2017-06-17 20:43:41 UTC

Browse source
This commit is contained in:
Travis CI 2017-06-17 20:43:42 +00:00
parent 933563f0be
commit 63912d6598
27 changed files with 77 additions and 41 deletions
Download patch file Download diff file Expand all files Collapse all files

7
blog/2017/06/17/release-47/index.html
View file

@ -66,7 +66,7 @@
<div class="meta clearfix">
<time datetime="2017-06-17T01:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> June 17, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 14 minutes reading time</span>
<span><i class='icon-time'></i> 15 minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
@ -100,6 +100,11 @@
<li>Restart Home Assistant to run with new IDs.</li>
<li>The old entity IDs will be available in the more info dialog to trace down any remaining errors.</li>
</ol>
<h2><a class="title-link" name="monkey-patching-python-36" href="#monkey-patching-python-36"></a> Monkey Patching Python 3.6</h2>
<p>Some people have noticed that running Home Assistant under Python 3.6 can lead to segfaults. It seems to be related to the <a href="https://github.com/home-assistant/home-assistant/issues/3453">earlier segfault issues</a> that we experienced when we released the asyncio-based core. We thought that those issues would have been fixed when <a href="https://bugs.python.org/issue26617">Python bug 26617</a> was resolved. Although we see less reports compared to the old bug, there are still users <a href="https://github.com/home-assistant/home-assistant/issues/7752">experiencing them</a> (<a href="https://github.com/home-assistant/home-assistant/issues/7752#issuecomment-305100009">gdb stacktrace points at <code class="highlighter-rouge">PyObject_GC_Del()</code></a>).</p>
<p>Since Python 3.6, the Task and Future classes have been moved to C. This gives a nice speed boost but also prevents us from monkey patching the Task class to avoid the segfault. <a href="https://github.com/bbangert">Ben Bangert</a> managed to brew up another monkey patch to stop Python 3.6 from using the C classes, falling back to the Python versions instead. This allows us to apply the original monkey patch again.</p>
<p>Both monkey patches are now active by default starting version 0.47 to avoid our users experiencing segfaults. This comes at a cost of not being able to benefit from all optimizations that were introduced in Python 3.6.</p>
<p>To run without the monkey patch, start Home Assistant with <code class="highlighter-rouge">HASS_NO_MONKEY=1 hass</code>. We will further investigate this issue and try to fix it in a future version of Python.</p>
<h2><a class="title-link" name="new-platforms" href="#new-platforms"></a> New platforms</h2>
<ul>
<li>Added a Taps Aff binary sensor (<a href="https://github.com/bazwilliams">@bazwilliams</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7880">#7880</a>) (<a href="https://home-assistant.io/components/binary_sensor.tapsaff/">binary_sensor.tapsaff docs</a>) (new-platform)</li>