Examine individual changes
From Gentoo Wiki
This page allows you to examine the variables generated by the Abuse Filter for an individual change, and test it against filters.
Variables generated for this change
| Variable | Value |
|---|---|
Edit count of the user (user_editcount) | 24 |
Name of the user account (user_name) | 'Radhermit' |
Age of the user account (user_age) | 206204892 |
Page ID (page_id) | 25557 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'Python' |
Full page title (page_prefixedtitle) | 'Project:Python' |
Action (action) | 'edit' |
Edit summary/reason (summary) | 'drop myself as a member' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=Python
|Description=The Python project maintains dev-lang/python and most of dev-python/*.
|Email=python@gentoo.org
|IRC=#gentoo-python
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|LeadElectionDate=2019/12/05
|Members={{Project Member
|Developer=User:Floppym
|IsLead=No
}}{{Project Member
|Developer=User:Chutzpah
|IsLead=No
}}{{Project Member
|Developer=User:MGorny
|IsLead=Yes
}}{{Project Member
|Developer=User:Prometheanfire
|IsLead=No
}}{{Project Member
|Developer=User:Radhermit
|IsLead=No
}}{{Project Member
|Developer=User:Sping
|IsLead=No
}}{{Project Member
|Developer=User:Soap
|IsLead=No
}}{{Project Member
|Developer=User:Sbraz
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|IsLead=No
}}{{Project Member
|Developer=User:Bman
|IsLead=No
}}{{Project Member
|Developer=User:Slashbeast
|IsLead=No
}}{{Project Member
|Developer=User:Pacho
|IsLead=No
}}{{Project Member
|Developer=User:Zlogene
|IsLead=No
}}
}}
== Python 2 end-of-life ==
By the end of 2019, Python 2.7 has reached end-of-life. Many projects have dropped Python 2 support already, and more are planning to do that. Gentoo is planning to continue providing its support where necessary for how long it's feasible to. However, this doesn't mean that we're going to go out of our way to provide support where upstream discontinued it.
More specifically:
* Packages that support both Python 2 and Python 3 but have no remaining Python 2 reverse dependencies will eventually have Python 2 support removed and become Python 3 only.
* Packages that support only Python 2 and have little chances of being ported to Python 3 will be removed eventually. The exact time of removal depends on usefulness and maintenance costs of individual packages.
* Python 2.7 interpreter will be kept as long as necessary and/or feasible. We'll continue patching it if necessary. You can use it along with virtualenv/pip to support your py2 apps for the time being.
* PyPy(2.7) support in packages has been removed already.
* PyPy2.7 interpreter will be kept as it is necessary to build PyPy3.
== Documentation ==
=== For users ===
* [[/Implementations|Implementations]]
* [[/python-exec|python-exec]] script wrapper
* <var>[[/PYTHON_TARGETS|PYTHON_TARGETS]]</var> variable
=== For developers ===
* [https://dev.gentoo.org/~mgorny/python-guide/ Gentoo Python Guide]
* [[/Python.eclass conversion|Conversion guide for python.eclass packages]]
* [[/API change history|Eclass API change history]]
* [[/Eclass design rationale|Eclass design rationale]]
* [[/Tests|Test suites]]
* [[/Virtuals|Virtual packages]]
* [[/Implementation_USE_flags|USE flags on Python implementations]]
* [[/Adding_and_Removing_Python_implementations|Adding and Removing Python implementations to/from PYTHON_COMPAT]]
* [[/Wheels_packages_in_Gentoo|Wheels packages]]
* [[/Strict_aliasing|Strict aliasing issues (-fno-strict-aliasing)]]
* [[/Dependencies|Dependencies on Python packages (and Python)]]
* [[/Byte_compiling|Byte compiling Python modules]]
* Other issues
** [[/Sphinx race conditions|Sphinx race conditions]] (e.g. FileExistsError: [Errno 17] File exists ...)
* [https://qa-reports.gentoo.org/output/gpyutils/ gpyutils output]
== Policy ==
=== Adding packages ===
Anyone may add Python packages to the repository, however there are a couple of requirements if you want the Python project team to maintain them:
# The package must be a dependency of an existing package maintained by the Python team in the tree.
# The package is a Python library with a significant level of demand from developers or users.
In either case, please ping a member of the Python team before adding the python project to the packages {{Path|metadata.xml}} file.
For all added packages, the ebuild ''must define test phase'' if the upstream has some tests and they are not thoroughly broken by design.
=== Stabilizing packages ===
Stable request bugs may be created if the package already has stable keywords, or upon request.
Please do not stabilize packages with no stable keywords without some reason for doing so. Stabilizing packages increases the workload on both the Python team and arch teams, and this should be weighed against the value of having an ebuild with stable keywords.
==== ALLARCHES ====
Packages which are not platform-dependent may be stabilized according to the ALLARCHES policy, where a single arch tester may stabilize the package for all arches at once without testing on each individually.
Determining if the package is platform-dependent may be tricky, but here are some guidelines:
* Most pure-Python packages may be considered platform-independent if they do not depend on architecture-specific values or functionality.
* Packages which compile and install extension modules should be considered platform-dependent since they invoke the system toolchain.
=== New Python versions ===
{{package|app-portage/gpyutils}} can be used to find packages that need to be tested with a new version of Python. Please do not file bug reports requesting that a new Python version be added to PYTHON_COMPAT.' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=Python
|Description=The Python project maintains dev-lang/python and most of dev-python/*.
|Email=python@gentoo.org
|IRC=#gentoo-python
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|LeadElectionDate=2019/12/05
|Members={{Project Member
|Developer=User:Floppym
|IsLead=No
}}{{Project Member
|Developer=User:Chutzpah
|IsLead=No
}}{{Project Member
|Developer=User:MGorny
|IsLead=Yes
}}{{Project Member
|Developer=User:Prometheanfire
|IsLead=No
}}{{Project Member
|Developer=User:Sping
|IsLead=No
}}{{Project Member
|Developer=User:Soap
|IsLead=No
}}{{Project Member
|Developer=User:Sbraz
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|IsLead=No
}}{{Project Member
|Developer=User:Bman
|IsLead=No
}}{{Project Member
|Developer=User:Slashbeast
|IsLead=No
}}{{Project Member
|Developer=User:Pacho
|IsLead=No
}}{{Project Member
|Developer=User:Zlogene
|IsLead=No
}}
}}
== Python 2 end-of-life ==
By the end of 2019, Python 2.7 has reached end-of-life. Many projects have dropped Python 2 support already, and more are planning to do that. Gentoo is planning to continue providing its support where necessary for how long it's feasible to. However, this doesn't mean that we're going to go out of our way to provide support where upstream discontinued it.
More specifically:
* Packages that support both Python 2 and Python 3 but have no remaining Python 2 reverse dependencies will eventually have Python 2 support removed and become Python 3 only.
* Packages that support only Python 2 and have little chances of being ported to Python 3 will be removed eventually. The exact time of removal depends on usefulness and maintenance costs of individual packages.
* Python 2.7 interpreter will be kept as long as necessary and/or feasible. We'll continue patching it if necessary. You can use it along with virtualenv/pip to support your py2 apps for the time being.
* PyPy(2.7) support in packages has been removed already.
* PyPy2.7 interpreter will be kept as it is necessary to build PyPy3.
== Documentation ==
=== For users ===
* [[/Implementations|Implementations]]
* [[/python-exec|python-exec]] script wrapper
* <var>[[/PYTHON_TARGETS|PYTHON_TARGETS]]</var> variable
=== For developers ===
* [https://dev.gentoo.org/~mgorny/python-guide/ Gentoo Python Guide]
* [[/Python.eclass conversion|Conversion guide for python.eclass packages]]
* [[/API change history|Eclass API change history]]
* [[/Eclass design rationale|Eclass design rationale]]
* [[/Tests|Test suites]]
* [[/Virtuals|Virtual packages]]
* [[/Implementation_USE_flags|USE flags on Python implementations]]
* [[/Adding_and_Removing_Python_implementations|Adding and Removing Python implementations to/from PYTHON_COMPAT]]
* [[/Wheels_packages_in_Gentoo|Wheels packages]]
* [[/Strict_aliasing|Strict aliasing issues (-fno-strict-aliasing)]]
* [[/Dependencies|Dependencies on Python packages (and Python)]]
* [[/Byte_compiling|Byte compiling Python modules]]
* Other issues
** [[/Sphinx race conditions|Sphinx race conditions]] (e.g. FileExistsError: [Errno 17] File exists ...)
* [https://qa-reports.gentoo.org/output/gpyutils/ gpyutils output]
== Policy ==
=== Adding packages ===
Anyone may add Python packages to the repository, however there are a couple of requirements if you want the Python project team to maintain them:
# The package must be a dependency of an existing package maintained by the Python team in the tree.
# The package is a Python library with a significant level of demand from developers or users.
In either case, please ping a member of the Python team before adding the python project to the packages {{Path|metadata.xml}} file.
For all added packages, the ebuild ''must define test phase'' if the upstream has some tests and they are not thoroughly broken by design.
=== Stabilizing packages ===
Stable request bugs may be created if the package already has stable keywords, or upon request.
Please do not stabilize packages with no stable keywords without some reason for doing so. Stabilizing packages increases the workload on both the Python team and arch teams, and this should be weighed against the value of having an ebuild with stable keywords.
==== ALLARCHES ====
Packages which are not platform-dependent may be stabilized according to the ALLARCHES policy, where a single arch tester may stabilize the package for all arches at once without testing on each individually.
Determining if the package is platform-dependent may be tricky, but here are some guidelines:
* Most pure-Python packages may be considered platform-independent if they do not depend on architecture-specific values or functionality.
* Packages which compile and install extension modules should be considered platform-dependent since they invoke the system toolchain.
=== New Python versions ===
{{package|app-portage/gpyutils}} can be used to find packages that need to be tested with a new version of Python. Please do not file bug reports requesting that a new Python version be added to PYTHON_COMPAT.' |
Unified diff of changes made by edit (edit_diff) | '@@ -18,7 +18,4 @@
}}{{Project Member
|Developer=User:Prometheanfire
-|IsLead=No
-}}{{Project Member
-|Developer=User:Radhermit
|IsLead=No
}}{{Project Member
' |
Old page size (old_size) | 5086 |
Lines added in edit (added_lines) | [] |
Lines removed in edit (removed_lines) | [
0 => '|IsLead=No',
1 => '}}{{Project Member',
2 => '|Developer=User:Radhermit'
] |
New page text, stripped of any markup (new_text) | '
Python
Description
The Python project maintains dev-lang/python and most of dev-python/*.
Project email
python@gentoo.org
IRC channel
#gentoo-python
Lead(s)
Michał Górny
(mgorny) Last elected: 2019/12/05
Member(s)
Aaron Bauman
(bman)Patrick McLean
(chutzpah)Mike Gilbert
(floppym)Georgy Yakovlev
(gyakovlev)Pacho Ramos
(Pacho)Matthew Thode
(prometheanfire)Tim Harder
(radhermit)Louis Sautier
(sbraz)Piotr Karbowski
(slashbeast)David Seifert
(soap)Sebastian Pipping
(sping)Mikle Kolyada
(Zlogene)
Subproject(s)(and inherited member(s))
(none)
Parent Project
Gentoo
Project listing
Contents
1 Python 2 end-of-life
2 Documentation
2.1 For users
2.2 For developers
3 Policy
3.1 Adding packages
3.2 Stabilizing packages
3.2.1 ALLARCHES
3.3 New Python versions
Python 2 end-of-life[edit | edit source]
By the end of 2019, Python 2.7 has reached end-of-life. Many projects have dropped Python 2 support already, and more are planning to do that. Gentoo is planning to continue providing its support where necessary for how long it's feasible to. However, this doesn't mean that we're going to go out of our way to provide support where upstream discontinued it.
More specifically:
Packages that support both Python 2 and Python 3 but have no remaining Python 2 reverse dependencies will eventually have Python 2 support removed and become Python 3 only.
Packages that support only Python 2 and have little chances of being ported to Python 3 will be removed eventually. The exact time of removal depends on usefulness and maintenance costs of individual packages.
Python 2.7 interpreter will be kept as long as necessary and/or feasible. We'll continue patching it if necessary. You can use it along with virtualenv/pip to support your py2 apps for the time being.
PyPy(2.7) support in packages has been removed already.
PyPy2.7 interpreter will be kept as it is necessary to build PyPy3.
Documentation[edit | edit source]
For users[edit | edit source]
Implementations
python-exec script wrapper
PYTHON_TARGETS variable
For developers[edit | edit source]
Gentoo Python Guide
Conversion guide for python.eclass packages
Eclass API change history
Eclass design rationale
Test suites
Virtual packages
USE flags on Python implementations
Adding and Removing Python implementations to/from PYTHON_COMPAT
Wheels packages
Strict aliasing issues (-fno-strict-aliasing)
Dependencies on Python packages (and Python)
Byte compiling Python modules
Other issues
Sphinx race conditions (e.g. FileExistsError: [Errno 17] File exists ...)
gpyutils output
Policy[edit | edit source]
Adding packages[edit | edit source]
Anyone may add Python packages to the repository, however there are a couple of requirements if you want the Python project team to maintain them:
The package must be a dependency of an existing package maintained by the Python team in the tree.
The package is a Python library with a significant level of demand from developers or users.
In either case, please ping a member of the Python team before adding the python project to the packages metadata.xml file.
For all added packages, the ebuild must define test phase if the upstream has some tests and they are not thoroughly broken by design.
Stabilizing packages[edit | edit source]
Stable request bugs may be created if the package already has stable keywords, or upon request.
Please do not stabilize packages with no stable keywords without some reason for doing so. Stabilizing packages increases the workload on both the Python team and arch teams, and this should be weighed against the value of having an ebuild with stable keywords.
ALLARCHES[edit | edit source]
Packages which are not platform-dependent may be stabilized according to the ALLARCHES policy, where a single arch tester may stabilize the package for all arches at once without testing on each individually.
Determining if the package is platform-dependent may be tricky, but here are some guidelines:
Most pure-Python packages may be considered platform-independent if they do not depend on architecture-specific values or functionality.
Packages which compile and install extension modules should be considered platform-dependent since they invoke the system toolchain.
New Python versions[edit | edit source]
app-portage/gpyutils can be used to find packages that need to be tested with a new version of Python. Please do not file bug reports requesting that a new Python version be added to PYTHON_COMPAT.' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tbody><tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>Python</big>
</th></tr>
<tr valign="top">
<th>Description
</th>
<td style="text-align: justify;">The Python project maintains dev-lang/python and most of dev-python/*.
</td></tr>
<tr>
<th><span title="Mails to member(s) listed below.">Project email</span>
</th>
<td><a rel="nofollow" class="external text" href="mailto:python@gentoo.org">python@gentoo.org</a>
</td></tr>
<tr>
<th><span title="The link opens a webchat to this project's Freenode IRC channel.">IRC channel</span>
</th>
<td><a rel="nofollow" class="external text" href="https://webchat.freenode.net/?channels=gentoo-python">#gentoo-python</a>
</td></tr>
<tr valign="top">
<th>Lead(s)
</th>
<td><ul><li><a href="/wiki/User:MGorny" title="User:MGorny">Michał Górny</a>
(mgorny)</li></ul> <br />Last elected: 2019/12/05
</td></tr>
<tr valign="top">
<th>Member(s)
</th>
<td><ul><li><a href="/wiki/User:Bman" title="User:Bman">Aaron Bauman</a>
(bman)</li><li><a href="/wiki/User:Chutzpah" title="User:Chutzpah">Patrick McLean</a>
(chutzpah)</li><li><a href="/wiki/User:Floppym" title="User:Floppym">Mike Gilbert</a>
(floppym)</li><li><a href="/wiki/User:GYakovlev" title="User:GYakovlev">Georgy Yakovlev</a>
(gyakovlev)</li><li><a href="/wiki/User:Pacho" title="User:Pacho">Pacho Ramos</a>
(Pacho)</li><li><a href="/wiki/User:Prometheanfire" title="User:Prometheanfire">Matthew Thode</a>
(prometheanfire)</li><li><a href="/wiki/User:Radhermit" title="User:Radhermit">Tim Harder</a>
(radhermit)</li><li><a href="/wiki/User:Sbraz" title="User:Sbraz">Louis Sautier</a>
(sbraz)</li><li><a href="/wiki/User:Slashbeast" title="User:Slashbeast">Piotr Karbowski</a>
(slashbeast)</li><li><a href="/wiki/User:Soap" title="User:Soap">David Seifert</a>
(soap)</li><li><a href="/wiki/User:Sping" title="User:Sping">Sebastian Pipping</a>
(sping)</li><li><a href="/wiki/User:Zlogene" title="User:Zlogene">Mikle Kolyada</a>
(Zlogene)</li></ul>
</td></tr>
<tr valign="top">
<th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td>(none)
</td></tr>
<tr>
<th>Parent Project
</th>
<td><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Gentoo</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></tbody></table>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Python_2_end-of-life"><span class="tocnumber">1</span> <span class="toctext">Python 2 end-of-life</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Documentation"><span class="tocnumber">2</span> <span class="toctext">Documentation</span></a>
<ul>
<li class="toclevel-2 tocsection-3"><a href="#For_users"><span class="tocnumber">2.1</span> <span class="toctext">For users</span></a></li>
<li class="toclevel-2 tocsection-4"><a href="#For_developers"><span class="tocnumber">2.2</span> <span class="toctext">For developers</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-5"><a href="#Policy"><span class="tocnumber">3</span> <span class="toctext">Policy</span></a>
<ul>
<li class="toclevel-2 tocsection-6"><a href="#Adding_packages"><span class="tocnumber">3.1</span> <span class="toctext">Adding packages</span></a></li>
<li class="toclevel-2 tocsection-7"><a href="#Stabilizing_packages"><span class="tocnumber">3.2</span> <span class="toctext">Stabilizing packages</span></a>
<ul>
<li class="toclevel-3 tocsection-8"><a href="#ALLARCHES"><span class="tocnumber">3.2.1</span> <span class="toctext">ALLARCHES</span></a></li>
</ul>
</li>
<li class="toclevel-2 tocsection-9"><a href="#New_Python_versions"><span class="tocnumber">3.3</span> <span class="toctext">New Python versions</span></a></li>
</ul>
</li>
</ul>
</div>
<h2><span class="mw-headline" id="Python_2_end-of-life">Python 2 end-of-life</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=1" class="mw-editsection-visualeditor" title="Edit section: Python 2 end-of-life">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=1" title="Edit section: Python 2 end-of-life">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>By the end of 2019, Python 2.7 has reached end-of-life. Many projects have dropped Python 2 support already, and more are planning to do that. Gentoo is planning to continue providing its support where necessary for how long it's feasible to. However, this doesn't mean that we're going to go out of our way to provide support where upstream discontinued it.
</p><p>More specifically:
</p>
<ul><li>Packages that support both Python 2 and Python 3 but have no remaining Python 2 reverse dependencies will eventually have Python 2 support removed and become Python 3 only.</li>
<li>Packages that support only Python 2 and have little chances of being ported to Python 3 will be removed eventually. The exact time of removal depends on usefulness and maintenance costs of individual packages.</li>
<li>Python 2.7 interpreter will be kept as long as necessary and/or feasible. We'll continue patching it if necessary. You can use it along with virtualenv/pip to support your py2 apps for the time being.</li>
<li>PyPy(2.7) support in packages has been removed already.</li>
<li>PyPy2.7 interpreter will be kept as it is necessary to build PyPy3.</li></ul>
<h2><span class="mw-headline" id="Documentation">Documentation</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=2" class="mw-editsection-visualeditor" title="Edit section: Documentation">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=2" title="Edit section: Documentation">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<h3><span class="mw-headline" id="For_users">For users</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=3" class="mw-editsection-visualeditor" title="Edit section: For users">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=3" title="Edit section: For users">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><li><a href="/wiki/Project:Python/Implementations" title="Project:Python/Implementations">Implementations</a></li>
<li><a href="/wiki/Project:Python/python-exec" title="Project:Python/python-exec">python-exec</a> script wrapper</li>
<li><var><a href="/wiki/Project:Python/PYTHON_TARGETS" title="Project:Python/PYTHON TARGETS">PYTHON_TARGETS</a></var> variable</li></ul>
<h3><span class="mw-headline" id="For_developers">For developers</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=4" class="mw-editsection-visualeditor" title="Edit section: For developers">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=4" title="Edit section: For developers">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><li><a rel="nofollow" class="external text" href="https://dev.gentoo.org/~mgorny/python-guide/">Gentoo Python Guide</a></li>
<li><a href="/wiki/Project:Python/Python.eclass_conversion" title="Project:Python/Python.eclass conversion">Conversion guide for python.eclass packages</a></li>
<li><a href="/wiki/Project:Python/API_change_history" title="Project:Python/API change history">Eclass API change history</a></li>
<li><a href="/wiki/Project:Python/Eclass_design_rationale" title="Project:Python/Eclass design rationale">Eclass design rationale</a></li>
<li><a href="/wiki/Project:Python/Tests" title="Project:Python/Tests">Test suites</a></li>
<li><a href="/wiki/Project:Python/Virtuals" title="Project:Python/Virtuals">Virtual packages</a></li>
<li><a href="/wiki/Project:Python/Implementation_USE_flags" title="Project:Python/Implementation USE flags">USE flags on Python implementations</a></li>
<li><a href="/wiki/Project:Python/Adding_and_Removing_Python_implementations" title="Project:Python/Adding and Removing Python implementations">Adding and Removing Python implementations to/from PYTHON_COMPAT</a></li>
<li><a href="/wiki/Project:Python/Wheels_packages_in_Gentoo" title="Project:Python/Wheels packages in Gentoo">Wheels packages</a></li>
<li><a href="/wiki/Project:Python/Strict_aliasing" title="Project:Python/Strict aliasing">Strict aliasing issues (-fno-strict-aliasing)</a></li>
<li><a href="/wiki/Project:Python/Dependencies" title="Project:Python/Dependencies">Dependencies on Python packages (and Python)</a></li>
<li><a href="/wiki/Project:Python/Byte_compiling" title="Project:Python/Byte compiling">Byte compiling Python modules</a></li>
<li>Other issues
<ul><li><a href="/wiki/Project:Python/Sphinx_race_conditions" title="Project:Python/Sphinx race conditions">Sphinx race conditions</a> (e.g. FileExistsError: [Errno 17] File exists ...)</li></ul></li>
<li><a rel="nofollow" class="external text" href="https://qa-reports.gentoo.org/output/gpyutils/">gpyutils output</a></li></ul>
<h2><span class="mw-headline" id="Policy">Policy</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=5" class="mw-editsection-visualeditor" title="Edit section: Policy">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=5" title="Edit section: Policy">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<h3><span class="mw-headline" id="Adding_packages">Adding packages</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=6" class="mw-editsection-visualeditor" title="Edit section: Adding packages">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=6" title="Edit section: Adding packages">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Anyone may add Python packages to the repository, however there are a couple of requirements if you want the Python project team to maintain them:
</p>
<ol><li>The package must be a dependency of an existing package maintained by the Python team in the tree.</li>
<li>The package is a Python library with a significant level of demand from developers or users.</li></ol>
<p>In either case, please ping a member of the Python team before adding the python project to the packages <span style="font-family: monospace; font-size: 95%">metadata.xml</span> file.
</p><p>For all added packages, the ebuild <i>must define test phase</i> if the upstream has some tests and they are not thoroughly broken by design.
</p>
<h3><span class="mw-headline" id="Stabilizing_packages">Stabilizing packages</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=7" class="mw-editsection-visualeditor" title="Edit section: Stabilizing packages">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=7" title="Edit section: Stabilizing packages">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Stable request bugs may be created if the package already has stable keywords, or upon request.
</p><p>Please do not stabilize packages with no stable keywords without some reason for doing so. Stabilizing packages increases the workload on both the Python team and arch teams, and this should be weighed against the value of having an ebuild with stable keywords.
</p>
<h4><span class="mw-headline" id="ALLARCHES">ALLARCHES</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=8" class="mw-editsection-visualeditor" title="Edit section: ALLARCHES">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=8" title="Edit section: ALLARCHES">edit source</a><span class="mw-editsection-bracket">]</span></span></h4>
<p>Packages which are not platform-dependent may be stabilized according to the ALLARCHES policy, where a single arch tester may stabilize the package for all arches at once without testing on each individually.
</p><p>Determining if the package is platform-dependent may be tricky, but here are some guidelines:
</p>
<ul><li>Most pure-Python packages may be considered platform-independent if they do not depend on architecture-specific values or functionality.</li>
<li>Packages which compile and install extension modules should be considered platform-dependent since they invoke the system toolchain.</li></ul>
<h3><span class="mw-headline" id="New_Python_versions">New Python versions</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Python&veaction=edit&section=9" class="mw-editsection-visualeditor" title="Edit section: New Python versions">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Python&action=edit&section=9" title="Edit section: New Python versions">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<p><a rel="nofollow" class="external text" href="https://packages.gentoo.org/packages/app-portage/gpyutils">app-portage/gpyutils</a> can be used to find packages that need to be tested with a new version of Python. Please do not file bug reports requesting that a new Python version be added to PYTHON_COMPAT.
</p>
' |
Unix timestamp of change (timestamp) | 1611778677 |