diff options
Diffstat (limited to 'guide/interpreter-maintenance.html')
| -rw-r--r-- | guide/interpreter-maintenance.html | 27 |
1 files changed, 14 insertions, 13 deletions
diff --git a/guide/interpreter-maintenance.html b/guide/interpreter-maintenance.html index f0ab8b4..9407e9e 100644 --- a/guide/interpreter-maintenance.html +++ b/guide/interpreter-maintenance.html @@ -1,10 +1,10 @@ <!DOCTYPE html> -<html> +<html lang="en"> <head> <meta charset="utf-8" /> - <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.17.1: http://docutils.sourceforge.net/" /> + <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.18.1: http://docutils.sourceforge.net/" /> <title>Maintenance of Python implementations — Gentoo Python Guide documentation</title> <link rel="stylesheet" type="text/css" href="_static/pygments.css" /> @@ -12,6 +12,7 @@ <script data-url_root="./" id="documentation_options" src="_static/documentation_options.js"></script> <script src="_static/jquery.js"></script> <script src="_static/underscore.js"></script> + <script src="_static/_sphinx_javascript_frameworks_compat.js"></script> <script src="_static/doctools.js"></script> <link rel="index" title="Index" href="genindex.html" /> <link rel="search" title="Search" href="search.html" /> @@ -33,9 +34,9 @@ <div class="body" role="main"> <section id="maintenance-of-python-implementations"> -<h1>Maintenance of Python implementations<a class="headerlink" href="#maintenance-of-python-implementations" title="Permalink to this headline">¶</a></h1> +<h1>Maintenance of Python implementations<a class="headerlink" href="#maintenance-of-python-implementations" title="Permalink to this heading">¶</a></h1> <section id="life-cycle-of-a-python-implementation"> -<h2>Life cycle of a Python implementation<a class="headerlink" href="#life-cycle-of-a-python-implementation" title="Permalink to this headline">¶</a></h2> +<h2>Life cycle of a Python implementation<a class="headerlink" href="#life-cycle-of-a-python-implementation" title="Permalink to this heading">¶</a></h2> <p>Every Python implementation (understood as a potential target) in Gentoo follows roughly the following life cycle:</p> <ol class="arabic simple"> @@ -91,9 +92,9 @@ at stage 8, as the targets were removed already and it is kept as a dependency and testing target.</p> </section> <section id="notes-specific-to-python-interpreters"> -<h2>Notes specific to Python interpreters<a class="headerlink" href="#notes-specific-to-python-interpreters" title="Permalink to this headline">¶</a></h2> +<h2>Notes specific to Python interpreters<a class="headerlink" href="#notes-specific-to-python-interpreters" title="Permalink to this heading">¶</a></h2> <section id="cpython-patchsets"> -<h3>CPython patchsets<a class="headerlink" href="#cpython-patchsets" title="Permalink to this headline">¶</a></h3> +<h3>CPython patchsets<a class="headerlink" href="#cpython-patchsets" title="Permalink to this heading">¶</a></h3> <p>Gentoo is maintaining patchsets for all CPython versions. These include some non-upstreamable Gentoo patches and upstream backports. While it is considered acceptable to add a new patch (e.g. a security bug fix) @@ -134,7 +135,7 @@ create the tag and push it:</p> </div> </section> <section id="pypy"> -<h3>PyPy<a class="headerlink" href="#pypy" title="Permalink to this headline">¶</a></h3> +<h3>PyPy<a class="headerlink" href="#pypy" title="Permalink to this heading">¶</a></h3> <p>Due to high resource requirements and long build time, PyPy on Gentoo is provided both in source and precompiled form. This creates a bit unusual ebuild structure:</p> @@ -168,9 +169,9 @@ in <code class="docutils literal notranslate"><span class="pre">~/binpkg/${arch} </section> </section> <section id="adding-a-new-python-implementation"> -<h2>Adding a new Python implementation<a class="headerlink" href="#adding-a-new-python-implementation" title="Permalink to this headline">¶</a></h2> +<h2>Adding a new Python implementation<a class="headerlink" href="#adding-a-new-python-implementation" title="Permalink to this heading">¶</a></h2> <section id="eclass-and-profile-changes"> -<h3>Eclass and profile changes<a class="headerlink" href="#eclass-and-profile-changes" title="Permalink to this headline">¶</a></h3> +<h3>Eclass and profile changes<a class="headerlink" href="#eclass-and-profile-changes" title="Permalink to this heading">¶</a></h3> <p>When adding a new Python target, please remember to perform all the following tasks:</p> <ul class="simple"> @@ -195,7 +196,7 @@ in <code class="docutils literal notranslate"><span class="pre">app-portage/gpyu </ul> </section> <section id="porting-initial-packages"> -<h3>Porting initial packages<a class="headerlink" href="#porting-initial-packages" title="Permalink to this headline">¶</a></h3> +<h3>Porting initial packages<a class="headerlink" href="#porting-initial-packages" title="Permalink to this heading">¶</a></h3> <p>The initial porting is quite hard due to a number of circular dependencies. To ease the process, it is recommended to temporarily limit testing of the packages that feature many additional test @@ -282,7 +283,7 @@ on reenabling tests in the packages where they were skipped.</p> </section> </section> <section id="python-build-system-bootstrap"> -<h2>Python build system bootstrap<a class="headerlink" href="#python-build-system-bootstrap" title="Permalink to this headline">¶</a></h2> +<h2>Python build system bootstrap<a class="headerlink" href="#python-build-system-bootstrap" title="Permalink to this heading">¶</a></h2> <p>Python build systems are often facing the bootstrap problem — that is, the build system itself has some dependencies, while these dependencies require the same build system to build. The common upstream way @@ -378,7 +379,7 @@ dependencies will be added or vendored into flit_core.</p> </form> </div> </div> -<script>$('#searchbox').show(0);</script> +<script>document.getElementById('searchbox').style.display = "block"</script> @@ -395,7 +396,7 @@ dependencies will be added or vendored into flit_core.</p> ©2020, Michał Górny, license: CC BY 4.0. | - Powered by <a href="http://sphinx-doc.org/">Sphinx 4.5.0</a> + Powered by <a href="http://sphinx-doc.org/">Sphinx 5.0.1</a> & <a href="https://github.com/bitprophet/alabaster">Alabaster 0.7.12</a> | |