diff options
Diffstat (limited to 'guide/expert-multi.html')
| -rw-r--r-- | guide/expert-multi.html | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/guide/expert-multi.html b/guide/expert-multi.html index 2248d41..4fd2a4b 100644 --- a/guide/expert-multi.html +++ b/guide/expert-multi.html @@ -1,16 +1,16 @@ <!DOCTYPE html> -<html lang="en"> +<html lang="en" data-content_root="./"> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" /> <title>Expert python-r1 usage — Gentoo Python Guide documentation</title> - <link rel="stylesheet" type="text/css" href="_static/pygments.css?v=b3523f8e" /> + <link rel="stylesheet" type="text/css" href="_static/pygments.css?v=4f649999" /> <link rel="stylesheet" type="text/css" href="_static/alabaster.css?v=039e1c02" /> - <script data-url_root="./" id="documentation_options" src="_static/documentation_options.js?v=b3ba4146"></script> + <script src="_static/documentation_options.js?v=5929fcd5"></script> <script src="_static/doctools.js?v=888ff710"></script> - <script src="_static/sphinx_highlight.js?v=4825356b"></script> + <script src="_static/sphinx_highlight.js?v=dc90522c"></script> <link rel="index" title="Index" href="genindex.html" /> <link rel="search" title="Search" href="search.html" /> <link rel="next" title="Integration with build systems written in Python" href="buildsys.html" /> @@ -32,12 +32,12 @@ <div class="body" role="main"> <section id="expert-python-r1-usage"> -<h1>Expert python-r1 usage<a class="headerlink" href="#expert-python-r1-usage" title="Permalink to this heading">¶</a></h1> +<h1>Expert python-r1 usage<a class="headerlink" href="#expert-python-r1-usage" title="Link to this heading">¶</a></h1> <p>The APIs described in this chapter are powerful but even harder to use than those described in <code class="docutils literal notranslate"><span class="pre">python-r1</span></code> chapter. You should not consider using them unless you have a proper ninja training.</p> <section id="partially-restricting-python-implementation"> -<span id="index-0"></span><h2>Partially restricting Python implementation<a class="headerlink" href="#partially-restricting-python-implementation" title="Permalink to this heading">¶</a></h2> +<span id="index-0"></span><h2>Partially restricting Python implementation<a class="headerlink" href="#partially-restricting-python-implementation" title="Link to this heading">¶</a></h2> <p>There are packages that have been ported to Python 3 only partially. They may still have some optional dependencies that support Python 2 only, they may have some components that do not support Python 3 yet. @@ -149,9 +149,9 @@ list.</p> <span class="s2"> "</span> </pre></div> </div> -<span class="target" id="index-1"></span></section> +</section> <section id="restricting-interpreters-for-python-setup"> -<span id="index-2"></span><h2>Restricting interpreters for python_setup<a class="headerlink" href="#restricting-interpreters-for-python-setup" title="Permalink to this heading">¶</a></h2> +<span id="index-2"></span><span id="index-1"></span><h2>Restricting interpreters for python_setup<a class="headerlink" href="#restricting-interpreters-for-python-setup" title="Link to this heading">¶</a></h2> <p>A specific case of the restriction described above is when the build step supports a subset of Python targets for the runtime part. This could happen e.g. if package’s Python bindings have been ported @@ -285,9 +285,9 @@ call).</p> </div> <p>Note that when the restriction is caused by dependencies rather than package’s files, the any-r1 API described below is preferable to this.</p> -<span class="target" id="index-3"></span></section> +</section> <section id="disjoint-build-dependencies-any-r1-api"> -<span id="index-4"></span><h2>Disjoint build dependencies (any-r1 API)<a class="headerlink" href="#disjoint-build-dependencies-any-r1-api" title="Permalink to this heading">¶</a></h2> +<span id="index-4"></span><span id="index-3"></span><h2>Disjoint build dependencies (any-r1 API)<a class="headerlink" href="#disjoint-build-dependencies-any-r1-api" title="Link to this heading">¶</a></h2> <p>Some packages have disjoint sets of runtime and pure build-time dependencies. The former need to be built for all enabled implementations, the latter only for one of them. The any-r1 API @@ -296,7 +296,7 @@ in <code class="docutils literal notranslate"><span class="pre">python-r1</span> to build documentation. Naturally, you’re going to build the documents only once, not separately for every enabled target.</p> <section id="using-regular-python-r1-api"> -<h3>Using regular python-r1 API<a class="headerlink" href="#using-regular-python-r1-api" title="Permalink to this heading">¶</a></h3> +<h3>Using regular python-r1 API<a class="headerlink" href="#using-regular-python-r1-api" title="Link to this heading">¶</a></h3> <p>If you were using the regular API, you’d have to use <code class="docutils literal notranslate"><span class="pre">${PYTHON_USEDEP}</span></code> on the dependencies. The resulting code could look like the following:</p> @@ -326,7 +326,7 @@ to the old version of <code class="docutils literal notranslate"><span class="pr be used via Python 2.7 at all.</p> </section> <section id="using-any-r1-api-with-python-r1"> -<h3>Using any-r1 API with python-r1<a class="headerlink" href="#using-any-r1-api-with-python-r1" title="Permalink to this heading">¶</a></h3> +<h3>Using any-r1 API with python-r1<a class="headerlink" href="#using-any-r1-api-with-python-r1" title="Link to this heading">¶</a></h3> <p>As the name suggests, the any-r1 API resembles the API used by <code class="docutils literal notranslate"><span class="pre">python-any-r1</span></code> eclass. The disjoint build-time dependencies are declared using <code class="docutils literal notranslate"><span class="pre">python_gen_any_dep</span></code>, and need to be tested @@ -367,7 +367,7 @@ we have used this API to add Python 3.8 support to packages before another implementation for Sphinx.</p> </section> <section id="different-sets-of-build-time-dependencies"> -<h3>Different sets of build-time dependencies<a class="headerlink" href="#different-sets-of-build-time-dependencies" title="Permalink to this heading">¶</a></h3> +<h3>Different sets of build-time dependencies<a class="headerlink" href="#different-sets-of-build-time-dependencies" title="Link to this heading">¶</a></h3> <p>Let’s consider the case when Python is used at build-time for something else still. In that case, we want <code class="docutils literal notranslate"><span class="pre">python_setup</span></code> to work unconditionally but enforce dependencies only with <code class="docutils literal notranslate"><span class="pre">doc</span></code> flag enabled.</p> @@ -400,7 +400,7 @@ it will use <em>any</em> interpreter that is supported and installed, even if it is not enabled explicitly in <code class="docutils literal notranslate"><span class="pre">PYTHON_TARGETS</span></code>.</p> </section> <section id="using-any-r1-api-with-distutils-r1"> -<h3>Using any-r1 API with distutils-r1<a class="headerlink" href="#using-any-r1-api-with-distutils-r1" title="Permalink to this heading">¶</a></h3> +<h3>Using any-r1 API with distutils-r1<a class="headerlink" href="#using-any-r1-api-with-distutils-r1" title="Link to this heading">¶</a></h3> <p>The alternate build dependency API also integrates with <code class="docutils literal notranslate"><span class="pre">distutils-r1</span></code> eclass. If <code class="docutils literal notranslate"><span class="pre">python_check_deps()</span></code> is declared, the <code class="docutils literal notranslate"><span class="pre">python_*_all()</span></code> sub-phase functions are called with the interpreter selected according @@ -431,7 +431,7 @@ therefore <code class="docutils literal notranslate"><span class="pre">python_ch </section> </section> <section id="combining-any-r1-api-with-implementation-restrictions"> -<h2>Combining any-r1 API with implementation restrictions<a class="headerlink" href="#combining-any-r1-api-with-implementation-restrictions" title="Permalink to this heading">¶</a></h2> +<h2>Combining any-r1 API with implementation restrictions<a class="headerlink" href="#combining-any-r1-api-with-implementation-restrictions" title="Link to this heading">¶</a></h2> <p>Both APIs described above can be combined. This can be used when build-time scripts support a subset of implementations supported by the package itself, and by its build-time dependencies. For example, @@ -627,7 +627,7 @@ to <code class="docutils literal notranslate"><span class="pre">python_gen_any_d ©2020, Michał Górny, license: CC BY 4.0. | - Powered by <a href="http://sphinx-doc.org/">Sphinx 7.1.2</a> + Powered by <a href="http://sphinx-doc.org/">Sphinx 7.2.6</a> & <a href="https://github.com/bitprophet/alabaster">Alabaster 0.7.13</a> | |