Update Python team report from Phabricator D386.diff.
This commit is contained in:
Warren Block
parent
1f51274d50
commit
5f3f59a238
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45279
1 changed files with 42 additions and 40 deletions
|
|
@ -456,69 +456,71 @@
|
|||
</project>
|
||||
|
||||
<project cat='ports'>
|
||||
<title>&os; Python Ports</title>
|
||||
<title>FreeBSD Python Ports</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
<name>
|
||||
<given>&os;</given>
|
||||
<common>Python Team</common>
|
||||
<given>FreeBSD</given>
|
||||
<common>Python Team</common>
|
||||
</name>
|
||||
<email>python@FreeBSD.org</email>
|
||||
</person>
|
||||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="https://wiki.FreeBSD.org/Python">The &os; Python Team Page</url>
|
||||
<url href="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team Page</url>
|
||||
<url href="irc://freebsd-python@irc.freenode.net">IRC channel</url>
|
||||
</links>
|
||||
|
||||
<body>
|
||||
<p>We are pleased to announce the availability of conflict-free
|
||||
Python package support across different Python versions based
|
||||
on the USES=uniquefiles feature recently introduced to the
|
||||
Ports framework. A Python package can be marked as buildable
|
||||
and installable in parallel for different Python versions at
|
||||
the same time on the same host. The package building tools,
|
||||
however, do not support this feature yet and the Python team
|
||||
will work closely with portmgr and pkg developers to enable
|
||||
support on a global ports and package scale.</p>
|
||||
<p>
|
||||
<ul>
|
||||
<li><p>We are pleased to announce the availability of conflict-free
|
||||
Python package support across different Python versions based on the
|
||||
USES=uniquefiles feature recently introduced to the Ports framework.
|
||||
A Python package can be marked as buildable and installable in
|
||||
parallel for different Python versions at the same time on the same
|
||||
host. The package building tools, however, do not support this feature
|
||||
yet and the Python team will work closely with portmgr and pkg
|
||||
developers to enable support on a global ports and package scale.
|
||||
</p></li>
|
||||
|
||||
<p>In May and June a huge clean-up operation took place to
|
||||
remove the last bits and pieces targeting easy_install. In the
|
||||
beginning of July we committed the final changes to remove
|
||||
easy_install support completely from the ports framework. This
|
||||
greatly simplifies the infrastructure and allows us to
|
||||
modernize and maintain it with less effort.</p>
|
||||
<li><p>In May and June a huge clean-up operation took place to remove
|
||||
the last bits and pieces targeting easy_install. In the beginning of
|
||||
July we committed the final changes to remove easy_install support
|
||||
completely from the ports framework. This greatly simplifies the
|
||||
infrastructure and allows us to modernize and maintain it with less
|
||||
effort.</p></li>
|
||||
|
||||
<p>We added Python 3.4, removed Python 3.1 after its end of
|
||||
life, updated the setuptools ports to version 5.1 and PyPy's
|
||||
development version to 2.3.1. The latest Python 2.7.8 and an
|
||||
updated setuptools will hit the tree shortly.</p>
|
||||
<li><p>We added Python 3.4, removed Python 3.1 after its end of life,
|
||||
updated the setuptools ports to version 5.1 and PyPy's development
|
||||
version to 2.3.1. The latest Python 2.7.8 and an updated setuptools
|
||||
will hit the tree shortly.</p></li>
|
||||
|
||||
<p>Our upstreaming effort continues to produce good outcomes for
|
||||
simplifying maintenance and reducing complexity.</p>
|
||||
<li><p>Our upstreaming effort continues to produce good outcomes for
|
||||
simplifying maintenance and reducing complexity.</p></li>
|
||||
|
||||
<p>Looking forward, one of the top priorities is to comply with
|
||||
the USES framework in the foreseeable future and to roll out
|
||||
a consistent maintainer policy for integrating new
|
||||
Python-related ports into the tree.</p>
|
||||
<li><p>Looking forward, one of the top priorities is to comply with
|
||||
the USES framework in the foreseeable future and to roll out a
|
||||
consistent maintainer policy for integrating new Python-related ports
|
||||
into the tree.</p></li>
|
||||
|
||||
</ul>
|
||||
</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
<task>Migrate bsd.python.mk to the Uses framework.</task>
|
||||
<task>Develop a high-level and lightweight Python Ports
|
||||
Policy.</task>
|
||||
<task>Add support for granular dependencies (for example
|
||||
>=1.0,<2.0).</task>
|
||||
<task>Develop a high-level and lightweight Python Ports Policy.</task>
|
||||
<task>Add support for granular dependencies (for example >=1.0,<2.0).</task>
|
||||
<task>See what adding pip (Python Package Index) support will
|
||||
require.</task>
|
||||
<task>Add default QA targets and functions for Python ports
|
||||
(TEST_DEPENDS, regression-test, etc.)</task>
|
||||
<task>More tasks can be found on the team's wiki page (see
|
||||
links).</task>
|
||||
<task>To get involved, interested people can say hello on IRC
|
||||
and let us know their areas of interest!</task>
|
||||
require.</task>
|
||||
<task>Add default QA targets and functions for Python ports (TEST_DEPENDS,
|
||||
regression-test, etc.)</task>
|
||||
<task>More tasks can be found on the team's wiki page (see links).</task>
|
||||
<task>To get involved, interested people can say hello on IRC and let us
|
||||
know their areas of interes!</task>
|
||||
</help>
|
||||
</project>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue