os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix lists in the Python section.

Browse source
This commit is contained in:
Warren Block 2014-07-14 02:27:10 +00:00
parent 95c64f6df5
commit f8af503e6a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45281
1 changed files with 11 additions and 11 deletions

22
en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
View file

@ -475,7 +475,7 @@
<body> <body>
<p> <p>
<li><p>We are pleased to announce the availability of conflict-free <p>We are pleased to announce the availability of conflict-free
Python package support across different Python versions based on the Python package support across different Python versions based on the
USES=uniquefiles feature recently introduced to the Ports framework. USES=uniquefiles feature recently introduced to the Ports framework.
A Python package can be marked as buildable and installable in A Python package can be marked as buildable and installable in
@ -483,27 +483,27 @@
host. The package building tools, however, do not support this feature host. The package building tools, however, do not support this feature
yet and the Python team will work closely with portmgr and pkg yet and the Python team will work closely with portmgr and pkg
developers to enable support on a global ports and package scale. developers to enable support on a global ports and package scale.
</p></li> </p>
<li><p>In May and June a huge clean-up operation took place to remove <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 the last bits and pieces targeting easy_install. In the beginning of
July we committed the final changes to remove easy_install support July we committed the final changes to remove easy_install support
completely from the ports framework. This greatly simplifies the completely from the ports framework. This greatly simplifies the
infrastructure and allows us to modernize and maintain it with less infrastructure and allows us to modernize and maintain it with less
effort.</p></li> effort.</p>
<li><p>We added Python 3.4, removed Python 3.1 after its end of life, <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 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 version to 2.3.1. The latest Python 2.7.8 and an updated setuptools
will hit the tree shortly.</p></li> will hit the tree shortly.</p>
<li><p>Our upstreaming effort continues to produce good outcomes for <p>Our upstreaming effort continues to produce good outcomes for
simplifying maintenance and reducing complexity.</p></li> simplifying maintenance and reducing complexity.</p>
<li><p>Looking forward, one of the top priorities is to comply with <p>Looking forward, one of the top priorities is to comply with
the USES framework in the foreseeable future and to roll out a the USES framework in the foreseeable future and to roll out a
consistent maintainer policy for integrating new Python-related ports consistent maintainer policy for integrating new Python-related ports
into the tree.</p></li> into the tree.</p>
</p> </p>
</body> </body>
@ -518,7 +518,7 @@
regression-test, etc.)</task> regression-test, etc.)</task>
<task>More tasks can be found on the team's wiki page (see links).</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 <task>To get involved, interested people can say hello on IRC and let us
know their areas of interes!</task> know their areas of interest!</task>
</help> </help>
</project> </project>