@@ -109,20 +109,22 @@ Node has to be installed.</p>
110<div class="section" id="tips-for-debugging-development">
110<div class="section" id="tips-for-debugging-development">
111<h2>Tips for debugging/development<a class="headerlink" href="#tips-for-debugging-development" title="Permalink to this headline">¶</a></h2>
111<h2>Tips for debugging/development<a class="headerlink" href="#tips-for-debugging-development" title="Permalink to this headline">¶</a></h2>
112−<ol class="arabic simple">
112+<ol class="arabic">
113<li><dl class="first docutils">
113<li><dl class="first docutils">
114<dt>Turn on debug logging</dt>
114<dt>Turn on debug logging</dt>
115−<dd>Whether you are working on a new engine or trying to eliminate a bug, it is always a good idea
115+<dd><p class="first last">Whether you are working on a new engine or trying to eliminate a bug, it is always a good idea
116to turn on debug logging. When debug logging is enabled a stack trace appears,
116to turn on debug logging. When debug logging is enabled a stack trace appears,
117instead of the cryptic <code class="docutils literal"><span class="pre">Internal</span> <span class="pre">Server</span> <span class="pre">Error</span></code> message. It can be turned on by setting
117instead of the cryptic <code class="docutils literal"><span class="pre">Internal</span> <span class="pre">Server</span> <span class="pre">Error</span></code> message. It can be turned on by setting
118−<code class="docutils literal"><span class="pre">debug:</span> <span class="pre">False</span></code> to <code class="docutils literal"><span class="pre">debug:</span> <span class="pre">True</span></code> in settings.yml.</dd>
118+<code class="docutils literal"><span class="pre">debug:</span> <span class="pre">False</span></code> to <code class="docutils literal"><span class="pre">debug:</span> <span class="pre">True</span></code> in settings.yml.</p>
121<li><dl class="first docutils">
122<li><dl class="first docutils">
122<dt>Run <code class="docutils literal"><span class="pre">./manage.sh</span> <span class="pre">tests</span></code> before creating a PR.</dt>
123<dt>Run <code class="docutils literal"><span class="pre">./manage.sh</span> <span class="pre">tests</span></code> before creating a PR.</dt>
123−<dd>Failing build on Travis is common because of PEP8 checks. So a new commit must be created
124+<dd><p class="first last">Failing build on Travis is common because of PEP8 checks. So a new commit must be created
124containing these format fixes. This phase can be skipped if <code class="docutils literal"><span class="pre">./manage.sh</span> <span class="pre">tests</span></code> is run
125containing these format fixes. This phase can be skipped if <code class="docutils literal"><span class="pre">./manage.sh</span> <span class="pre">tests</span></code> is run
125−locally before creating a PR.</dd>
126+locally before creating a PR.</p>