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 |
|---|---|
Whether or not the edit is marked as minor (no longer in use) (minor_edit) | false |
Edit count of the user (user_editcount) | 2389 |
Name of the user account (user_name) | 'MGorny' |
Age of the user account (user_age) | 253122346 |
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) | 'vdupras is retiring' |
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/04/26
|Members={{Project Member
|Developer=User:Floppym
|Role=Lead
|IsLead=Yes
}}{{Project Member
|Developer=User:Chutzpah
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Maksbotan
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:MGorny
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Prometheanfire
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Radhermit
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Sping
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Mrueg
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Monsieurp
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Soap
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Vdupras
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Sbraz
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|Role=Member
|IsLead=No
}}
}}
== Documentation ==
=== For users ===
* [[/Implementations|Implementations]]
* [[/python-exec|python-exec]] script wrapper
* <var>[[/PYTHON_TARGETS|PYTHON_TARGETS]]</var> variable
=== For developers ===
* [[/Python.eclass conversion|Conversion guide for python.eclass packages]]
* [[/API change history|Eclass API change history]]
* [[/Eclasses|eclasses]]
** [[/distutils-r1|distutils-r1]]
** [[/python-r1|python-r1]]
** [[/python-any-r1|python-any-r1]]
** [[/python-single-r1|python-single-r1]]
** [[/python-utils-r1|python-utils-r1]]
** [[/twisted-r1|twisted-r1]]
* Interoperability with other eclasses
** [[/scons-utils integration|scons-utils integration]]
** [[/waf-utils integration|waf-utils integration]]
* [[/Eclass design rationale|Eclass design rationale]]
* [[/pypy-bin|pypy-bin]] build instructions
* [[/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)]]
* [[/Namespace_packages|Namespace packages]]
* 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 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/04/26
|Members={{Project Member
|Developer=User:Floppym
|Role=Lead
|IsLead=Yes
}}{{Project Member
|Developer=User:Chutzpah
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Maksbotan
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:MGorny
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Prometheanfire
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Radhermit
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Sping
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Mrueg
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Monsieurp
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Soap
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Sbraz
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|Role=Member
|IsLead=No
}}
}}
== Documentation ==
=== For users ===
* [[/Implementations|Implementations]]
* [[/python-exec|python-exec]] script wrapper
* <var>[[/PYTHON_TARGETS|PYTHON_TARGETS]]</var> variable
=== For developers ===
* [[/Python.eclass conversion|Conversion guide for python.eclass packages]]
* [[/API change history|Eclass API change history]]
* [[/Eclasses|eclasses]]
** [[/distutils-r1|distutils-r1]]
** [[/python-r1|python-r1]]
** [[/python-any-r1|python-any-r1]]
** [[/python-single-r1|python-single-r1]]
** [[/python-utils-r1|python-utils-r1]]
** [[/twisted-r1|twisted-r1]]
* Interoperability with other eclasses
** [[/scons-utils integration|scons-utils integration]]
** [[/waf-utils integration|waf-utils integration]]
* [[/Eclass design rationale|Eclass design rationale]]
* [[/pypy-bin|pypy-bin]] build instructions
* [[/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)]]
* [[/Namespace_packages|Namespace packages]]
* 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.' |
Unified diff of changes made by edit (edit_diff) | '@@ -45,8 +45,4 @@
}}{{Project Member
|Developer=User:Soap
-|Role=Member
-|IsLead=No
-}}{{Project Member
-|Developer=User:Vdupras
|Role=Member
|IsLead=No
' |
Old page size (old_size) | 4242 |
Lines added in edit (added_lines) | [] |
Lines removed in edit (removed_lines) | [
0 => '|Role=Member',
1 => '|IsLead=No',
2 => '}}{{Project Member',
3 => '|Developer=User:Vdupras'
] |
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)
Mike Gilbert
(floppym)Lead Last elected: 2019/04/26
Member(s)
Patrick McLean
(chutzpah)MemberGeorgy Yakovlev
(gyakovlev)MemberMichał Górny
(mgorny)MemberMaxim Koltsov
(maksbotan)MemberPatrice Clement
(monsieurp)MemberManuel Rüger
(mrueg)MemberMatthew Thode
(prometheanfire)MemberTim Harder
(radhermit)MemberLouis Sautier
(sbraz)MemberDavid Seifert
(soap)MemberSebastian Pipping
(sping)MemberVirgil Dupras
(vdupras)Member
Subproject(s)(and inherited member(s))
(none)
Parent Project
Gentoo
Project listing
Contents
1 Documentation
1.1 For users
1.2 For developers
2 Policy
2.1 Adding packages
2.2 Stabilizing packages
2.2.1 ALLARCHES
Documentation[edit]
For users[edit]
Implementations
python-exec script wrapper
PYTHON_TARGETS variable
For developers[edit]
Conversion guide for python.eclass packages
Eclass API change history
eclasses
distutils-r1
python-r1
python-any-r1
python-single-r1
python-utils-r1
twisted-r1
Interoperability with other eclasses
scons-utils integration
waf-utils integration
Eclass design rationale
pypy-bin build instructions
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)
Namespace packages
Other issues
Sphinx race conditions (e.g. FileExistsError: [Errno 17] File exists ...)
gpyutils output
Policy[edit]
Adding packages[edit]
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]
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]
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.
' |
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:Floppym" title="User:Floppym">Mike Gilbert</a>
(floppym)<br /><i>Lead</i></li></ul> <br />Last elected: 2019/04/26
</td></tr>
<tr valign="top">
<th>Member(s)
</th>
<td><ul><li><a href="/wiki/User:Chutzpah" title="User:Chutzpah">Patrick McLean</a>
(chutzpah)<br /><i>Member</i></li><li><a href="/wiki/User:GYakovlev" title="User:GYakovlev">Georgy Yakovlev</a>
(gyakovlev)<br /><i>Member</i></li><li><a href="/wiki/User:MGorny" title="User:MGorny">Michał Górny</a>
(mgorny)<br /><i>Member</i></li><li><a href="/wiki/User:Maksbotan" title="User:Maksbotan">Maxim Koltsov</a>
(maksbotan)<br /><i>Member</i></li><li><a href="/wiki/User:Monsieurp" title="User:Monsieurp">Patrice Clement</a>
(monsieurp)<br /><i>Member</i></li><li><a href="/wiki/User:Mrueg" title="User:Mrueg">Manuel Rüger</a>
(mrueg)<br /><i>Member</i></li><li><a href="/wiki/User:Prometheanfire" title="User:Prometheanfire">Matthew Thode</a>
(prometheanfire)<br /><i>Member</i></li><li><a href="/wiki/User:Radhermit" title="User:Radhermit">Tim Harder</a>
(radhermit)<br /><i>Member</i></li><li><a href="/wiki/User:Sbraz" title="User:Sbraz">Louis Sautier</a>
(sbraz)<br /><i>Member</i></li><li><a href="/wiki/User:Soap" title="User:Soap">David Seifert</a>
(soap)<br /><i>Member</i></li><li><a href="/wiki/User:Sping" title="User:Sping">Sebastian Pipping</a>
(sping)<br /><i>Member</i></li><li><a href="/wiki/User:Vdupras" title="User:Vdupras">Virgil Dupras</a>
(vdupras)<br /><i>Member</i></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"><div class="toctitle" lang="en" dir="ltr"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Documentation"><span class="tocnumber">1</span> <span class="toctext">Documentation</span></a>
<ul>
<li class="toclevel-2 tocsection-2"><a href="#For_users"><span class="tocnumber">1.1</span> <span class="toctext">For users</span></a></li>
<li class="toclevel-2 tocsection-3"><a href="#For_developers"><span class="tocnumber">1.2</span> <span class="toctext">For developers</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-4"><a href="#Policy"><span class="tocnumber">2</span> <span class="toctext">Policy</span></a>
<ul>
<li class="toclevel-2 tocsection-5"><a href="#Adding_packages"><span class="tocnumber">2.1</span> <span class="toctext">Adding packages</span></a></li>
<li class="toclevel-2 tocsection-6"><a href="#Stabilizing_packages"><span class="tocnumber">2.2</span> <span class="toctext">Stabilizing packages</span></a>
<ul>
<li class="toclevel-3 tocsection-7"><a href="#ALLARCHES"><span class="tocnumber">2.2.1</span> <span class="toctext">ALLARCHES</span></a></li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<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&action=edit&section=1" title="Edit section: Documentation">edit</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&action=edit&section=2" title="Edit section: For users">edit</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&action=edit&section=3" title="Edit section: For developers">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><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/Eclasses" title="Project:Python/Eclasses">eclasses</a>
<ul><li><a href="/wiki/Project:Python/distutils-r1" title="Project:Python/distutils-r1">distutils-r1</a></li>
<li><a href="/wiki/Project:Python/python-r1" title="Project:Python/python-r1">python-r1</a></li>
<li><a href="/wiki/Project:Python/python-any-r1" title="Project:Python/python-any-r1">python-any-r1</a></li>
<li><a href="/wiki/Project:Python/python-single-r1" title="Project:Python/python-single-r1">python-single-r1</a></li>
<li><a href="/wiki/Project:Python/python-utils-r1" title="Project:Python/python-utils-r1">python-utils-r1</a></li>
<li><a href="/index.php?title=Project:Python/twisted-r1&action=edit&redlink=1" class="new" title="Project:Python/twisted-r1 (page does not exist)">twisted-r1</a></li></ul></li>
<li>Interoperability with other eclasses
<ul><li><a href="/wiki/Project:Python/scons-utils_integration" title="Project:Python/scons-utils integration">scons-utils integration</a></li>
<li><a href="/wiki/Project:Python/waf-utils_integration" title="Project:Python/waf-utils integration">waf-utils integration</a></li></ul></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/pypy-bin" title="Project:Python/pypy-bin">pypy-bin</a> build instructions</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/Namespace_packages" title="Project:Python/Namespace packages">Namespace packages</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&action=edit&section=4" title="Edit section: Policy">edit</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&action=edit&section=5" title="Edit section: Adding packages">edit</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&action=edit&section=6" title="Edit section: Stabilizing packages">edit</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&action=edit&section=7" title="Edit section: ALLARCHES">edit</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>
<!--
NewPP limit report
Cached time: 20191018103233
Cache expiry: 86400
Dynamic content: false
[SMW] In‐text annotation parser time: 0.01 seconds
CPU time usage: 0.214 seconds
Real time usage: 0.284 seconds
Preprocessor visited node count: 729/1000000
Preprocessor generated node count: 2146/1000000
Post‐expand include size: 5211/2097152 bytes
Template argument size: 1288/2097152 bytes
Highest expansion depth: 7/40
Expensive parser function count: 0/100
Unstrip recursion depth: 0/20
Unstrip post‐expand size: 0/5000000 bytes
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
100.00% 234.805 1 -total
99.32% 233.210 1 Template:Project
50.30% 118.110 13 Template:ProjectMemberLine
20.19% 47.404 13 Template:ProjectMemberLineNickname
13.27% 31.169 12 Template:Project_Member
0.55% 1.292 1 Template:Path
-->
</div>' |
Unix timestamp of change (timestamp) | 1571394753 |