diff options
Diffstat (limited to 'guide/package-maintenance.html')
| -rw-r--r-- | guide/package-maintenance.html | 21 |
1 files changed, 11 insertions, 10 deletions
diff --git a/guide/package-maintenance.html b/guide/package-maintenance.html index 320466d..9fb1d4e 100644 --- a/guide/package-maintenance.html +++ b/guide/package-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>Python package maintenance — 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" /> @@ -34,9 +35,9 @@ <div class="body" role="main"> <section id="python-package-maintenance"> -<h1>Python package maintenance<a class="headerlink" href="#python-package-maintenance" title="Permalink to this headline">¶</a></h1> +<h1>Python package maintenance<a class="headerlink" href="#python-package-maintenance" title="Permalink to this heading">¶</a></h1> <section id="support-for-python-2"> -<h2>Support for Python 2<a class="headerlink" href="#support-for-python-2" title="Permalink to this headline">¶</a></h2> +<h2>Support for Python 2<a class="headerlink" href="#support-for-python-2" title="Permalink to this heading">¶</a></h2> <p>Since Python 2.7 reached EOL, Gentoo is currently phasing out support for Python 2. Unless your package or its reverse dependencies really need it, you should omit it from <code class="docutils literal notranslate"><span class="pre">PYTHON_COMPAT</span></code>. If you’re adding @@ -49,7 +50,7 @@ of reverse dependencies afterwards.</p> supporting it soon are being slowly removed.</p> </section> <section id="which-implementations-to-test-new-packages-for"> -<h2>Which implementations to test new packages for?<a class="headerlink" href="#which-implementations-to-test-new-packages-for" title="Permalink to this headline">¶</a></h2> +<h2>Which implementations to test new packages for?<a class="headerlink" href="#which-implementations-to-test-new-packages-for" title="Permalink to this heading">¶</a></h2> <p>The absolute minimum set of targets are the current default targets found in <code class="docutils literal notranslate"><span class="pre">profiles/base/make.defaults</span></code>. However, developers are strongly encouraged to test at least the next Python 3 version @@ -58,7 +59,7 @@ in order to ease future transition, and preferably all future versions.</p> coverage of PyPy3 support.</p> </section> <section id="adding-new-python-implementations-to-existing-packages"> -<h2>Adding new Python implementations to existing packages<a class="headerlink" href="#adding-new-python-implementations-to-existing-packages" title="Permalink to this headline">¶</a></h2> +<h2>Adding new Python implementations to existing packages<a class="headerlink" href="#adding-new-python-implementations-to-existing-packages" title="Permalink to this heading">¶</a></h2> <p>New Python implementations can generally be added to existing packages without a revision bump. This is because the new dependencies are added conditionally to new USE flags. Since the existing users can not have @@ -70,7 +71,7 @@ will not be able to enable newly added flags and therefore the risk of the change breaking stable systems is minimal.</p> </section> <section id="which-packages-can-be-co-maintained-by-the-python-project"> -<h2>Which packages can be (co-)maintained by the Python project?<a class="headerlink" href="#which-packages-can-be-co-maintained-by-the-python-project" title="Permalink to this headline">¶</a></h2> +<h2>Which packages can be (co-)maintained by the Python project?<a class="headerlink" href="#which-packages-can-be-co-maintained-by-the-python-project" title="Permalink to this heading">¶</a></h2> <p>A large part of the Python ecosystem is fairly consistent, making it feasible for (co-)maintenance by the Gentoo Python team.</p> <p>As a rule of thumb, Python team is ready to maintain packages specific @@ -87,7 +88,7 @@ the package. However, if you are not a member of the project, please do not add us without asking first.</p> </section> <section id="porting-packages-to-a-new-eapi"> -<h2>Porting packages to a new EAPI<a class="headerlink" href="#porting-packages-to-a-new-eapi" title="Permalink to this headline">¶</a></h2> +<h2>Porting packages to a new EAPI<a class="headerlink" href="#porting-packages-to-a-new-eapi" title="Permalink to this heading">¶</a></h2> <p>When porting packages to a new EAPI, please take care not to port the dependencies of Portage prematurely. This generally includes <code class="docutils literal notranslate"><span class="pre">app-portage/gemato</span></code>, <code class="docutils literal notranslate"><span class="pre">dev-python/setuptools</span></code> and their recursive @@ -169,7 +170,7 @@ necessary to install a new Portage version.</p> </form> </div> </div> -<script>$('#searchbox').show(0);</script> +<script>document.getElementById('searchbox').style.display = "block"</script> @@ -186,7 +187,7 @@ necessary to install a new Portage version.</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> | |