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

- Add a 2013Q4 report for the Python ports

Browse source 
Submitted by:	mva
This commit is contained in:
Gabor Pali 2014-01-14 13:06:44 +00:00
parent 7429066b70
commit bbb6011f26
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=43499
1 changed files with 68 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

69
en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml
View file

@ -19,7 +19,7 @@
<!-- XXX: Keep updating the number of entries -->
<p>Thanks to all the reporters for the excellent work! This report
contains 12 entries and we hope you enjoy reading it.</p>
contains 13 entries and we hope you enjoy reading it.</p>
<p>The deadline for submissions covering between January and
March 2014 is April 7th, 2014.</p>
@ -661,4 +661,71 @@
Linux"</tt>.</task>
</help>
</project>
<project cat='ports'>
<title>&os; Python Ports</title>
<contact>
<person>
<name>&os; Python Team</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>Python is a widely used general-purpose, high-level programming
language. For many operating systems, Python is a standard
component; it ships with &os; as well. A lot of progress has
been made around the &os; Python ports in the last quarter.</p>
<p>The <tt>devel/py-distribute</tt> port has been replaced by the
refreshed <tt>devel/py-setuptools</tt> port, which comes with a
lot of features that simplify the ways of installing Python
packages. The change also led us to install everything through
Setuptools now, which resembles a PyIP a bit and allows us to
perform some major cleanup on the distutils installation
behaviour.</p>
<p>The implicit <tt>lang/python</tt> build and run-time dependency
was removed from the ports infrastructure. Every port now
depends on a specific Python version or on the
<tt>lang/python</tt> metaport. This prevents compatibility
issues for ports that depend on Python&nbsp;2.x OR
Python&nbsp;3.x exclusively, but use the <tt>python</tt>
command, which might point to a version of incompatible user
choice.</p>
<p>The <tt>lang/python27</tt> port was updated to version 2.7.6,
and the <tt>lang/python33</tt> port was updated to version
3.3.3, and the <tt>lang/pypy</tt> port was updated to version
2.2.1</p>
<p>We are currently working on the necessary infrastructure quirks
to support different Python versions for the same port. Most of
the work has been done and needs to be tested before it can be
integrated.</p>
</body>
<help>
<task>Develop a high-level and lightweight Python Ports Policy.</task>
<task>Add support for granular dependencies (for example
<tt>&gt;=1.0</tt> or <tt>&lt;2.0</tt>).</task>
<task>Look at what adding PyPI (the Python Package Index) support
looks like.</task>
<task>Convert all <tt>USE_PYDISTUTILS=easy_install</tt> entries to
<tt>yes</tt> and remove the use of <tt>easy_install</tt> from
the ports infrastructure.</task>
<task>More tasks can be found on the team's wiki page (see
links).</task>
</help>
</project>
</report>