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

- Add a Q3 report for the Python ports

Browse source 
Submitted by:	mva
This commit is contained in:
Gabor Pali 2013-09-16 21:13:24 +00:00
parent 3a9e93da8b
commit c297d68a1a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=42673
1 changed files with 78 additions and 1 deletions

79
en_US.ISO8859-1/htdocs/news/status/report-2013-07-2013-09.xml
View file

@ -19,7 +19,7 @@
<!-- XXX: keep updating the number of entries --> <!-- XXX: keep updating the number of entries -->
<p>Thanks to all the reporters for the excellent work! This report <p>Thanks to all the reporters for the excellent work! This report
contains 5 entries and we hope you enjoy reading it.</p> contains 6 entries and we hope you enjoy reading it.</p>
<!-- XXX: set date for the next set of submissions --> <!-- XXX: set date for the next set of submissions -->
<p>The deadline for submissions covering between October and <p>The deadline for submissions covering between October and
@ -38,6 +38,12 @@
<description>Kernel</description> <description>Kernel</description>
</category> </category>
<category>
<name>ports</name>
<description>Ports</description>
</category>
<project cat='kern'> <project cat='kern'>
<title>AES-NI Improvements for GELI</title> <title>AES-NI Improvements for GELI</title>
@ -244,4 +250,75 @@
and support for a few additional features.</p> and support for a few additional features.</p>
</body> </body>
</project> </project>
<project cat='ports'>
<title>&os; Python Ports</title>
<contact>
<person>
<name>
<given>&os;</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="irc://freebsd-python@irc.freenode.net">IRC channel</url>
</links>
<body>
<p>We are currently working on cleaning up the
<tt>lang/python*</tt> ports to improve the compatibility with
the original upstream build behaviour and to lower the need for
&os;-specific build patches. A first step was made in September
by reducing the flags injected into the different Python
interpreter versions.</p>
<p>The first tasks for supporting the installation of packages for
different Python ports have been done. A new metaport structure
has replaced the original Python port behaviour and will be
enhanced over the next months to enable improved installation
support of packages for different Python versions at the same
time.</p>
<p>Plans are made to enhance the Python ports framework by
automating the insertion of byte-compiled files into
<tt>pkg-plist</tt> files. Besides the reduction of packaging
list sizes, this is also required to offer packages for multiple
Python versions.</p>
<p>PyPy was heavily enhanced over the last couple of months.
Major updates of the port solved integration issues and a new
<tt>pypy-devel</tt> port for snapshots and previews was added.
Since the PyPy&nbsp;3 release, there is a new
<tt>pypy3-devel</tt> port available to provide not only
compatibility for Python&nbsp;2.x specific scripts, but also for
those using the 3.x language specification.</p>
<p>IronPython found its way into the &os; ports tree, which
provides an implementation of the Python language based on .NET
and Mono.</p>
</body>
<help>
<task>Develop a high-level and lightweight Python Ports
Policy.</task>
<task>Chase the unification of Distribute
(<tt>devel/py-distribute</tt>) and Setuptools
(<tt>devel/py-setuptools*</tt>).</task>
<task>Add support for granular dependencies (for example
<tt>>=1.0</tt> or <tt>&lt; 2.0</tt>).</task>
<task>Look at what adding <tt>pip</tt> (Python Package Index)
support looks like.</task>
<task>More tasks can be found on the Team's wiki page (see
links).</task>
</help>
</project>
</report> </report>