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

Refresh the python entry to the latest version.

Browse source 
Sponsored by:	The FreeBSD Foundation
This commit is contained in:
Glen Barber 2014-07-13 23:09:42 +00:00
parent 3dbaa2518d
commit da58f986b6
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45275
1 changed files with 15 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -459,16 +459,15 @@
</links>
<body>
<p>We are pleased to announce the availability of support for
conflict-free Python package support across different Python
versions, based on the USES=uniquefiles feature recently
introduced to the Ports framework. This means that you can, in
theory, mark a Python package 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>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>In May and June a huge clean-up operation took place to
remove the last bits and pieces targeting easy_install. In the
@ -485,9 +484,9 @@
<p>Our upstreaming effort continues to produce good outcomes for
simplifying maintenance and reducing complexity.</p>
<p>Looking forward, one of the top priorities will be to comply
to the Uses framework in the foreseeable future and to roll
out a consistent maintainer policy for integrating new
<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>
</body>
@ -495,12 +494,10 @@
<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 &gt;=1.0,&lt;2.0).</task>
<task>Look at what adding pip (Python Package Index) support looks like.</task>
<task>Add default QA targets and functions for Python ports (TEST_DEPENDS,
regression-test, etc.)</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, come and say hi on IRC and let us know what you're
interested in!</task>
<task>To get involved, interested people can say hello on IRC and let us know their areas of interest!</task>
</help>
</project>