<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 29 October 2014 13:18, Martin Hundebøll <span dir="ltr"><<a href="mailto:martin@hundeboll.net" target="_blank">martin@hundeboll.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I used to use a virtualenv to temporarily set Python 2 as the default<br>
for the shell in which I ran bitbake commands. That was a while ago<br>
though, all my current builds are running on Ubuntu 12.04/14.04 server<br>
instances which I access via ssh from my Arch Linux box.<br>
</blockquote>
<br></span>
Using a compatible distro-install is of course the easiest way to get going. Could also work with a virtual machine.</blockquote></div><br>Paul meant the Python tool virtualenv, <a href="http://virtualenv.readthedocs.org/en/latest/virtualenv.html" target="_blank">http://virtualenv.readthedocs.org/en/latest/virtualenv.html</a>. This can be used to create an environment where "python" on the search path is python 2, on a system where /usr/bin/ is python 3.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I admit that I'm leaning towards thinking that we just say bitbake requires "python" to be 2.7+ and if your host distribution uses python 3 by default, use virtualenv. The logic being added to the V2 series to generate symlinks and drop them into the bitbake source tree isn't very elegant.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Obviously using virtualenv means you need to use /usr/bin/env in the shebangs, so that part of the series is still needed.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>