<p>As most operation systems are coming with Python3 installed by default. So it is time for searx to support Python3. But don’t worry support of Python2.7 won’t be dropped.</p>
<h2>How to run searx using Python3<aclass="headerlink"href="#how-to-run-searx-using-python3"title="Permalink to this headline">¶</a></h2>
<p>Please make sure that you run at least Python3.5.</p>
<p>To run searx, first a Python3 virtualenv should be created. After entering the virtualenv,
dependencies must be installed. Then run searx with python3 instead of the usual python command.</p>
<divclass="code sh highlight-default"><divclass="highlight"><pre><span></span><spanclass="n">virtualenv</span><spanclass="o">-</span><spanclass="n">p</span><spanclass="n">python3</span><spanclass="n">venv3</span>
<h2>Fun facts<aclass="headerlink"href="#fun-facts"title="Permalink to this headline">¶</a></h2>
<ulclass="simple">
<li>115 files were changed when implementing the support for both Python versions.</li>
<li>All of the dependencies was compatible except for the robotframework used for browser tests. Thus, these tests were migrated to splinter. So from now on both versions are being tested on Travis and can be tested locally.</li>
<h2>If you found bugs…<aclass="headerlink"href="#if-you-found-bugs"title="Permalink to this headline">¶</a></h2>
<p>…please open an issue on <aclass="reference external"href="https://github.com/asciimoo/searx/issues">GitHub</a>. Make sure that you mention your Python version in your issue,