From Fedora Project Wiki
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{admon/important|Old page|This page is a ''Feature page'' for Fedora 15 (that's history). It is not a general information page about PyPy in Fedora. Expect everything here to be outdated. Do not update it.}}
<!-- All fields on this form are required to be accepted by FESCo.
<!-- All fields on this form are required to be accepted by FESCo.
  We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
  We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
Line 7: Line 8:


== Summary ==
== Summary ==
Fedora 15 and later versions has an alternate Python 2 runtime and add-on module stack built using PyPy, an alternate implementation of the Python 2 language, featuring Just-in-Time compilation.
Fedora N+1 <!-- {{FedoraVersion|long|next}} --> has an alternate Python 2 runtime and add-on module stack built using PyPy, an alternate implementation of the Python 2 language, featuring Just-in-Time compilation.


== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:dmalcolm| Dave Malcolm]], [[User:mcyprian| Michal Cyprian]]
* Name: [[User:dmalcolm| Dave Malcolm]]


<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* Email: <dmalcolm@redhat.com>, <mcyprian@redhat.com>
* Email: <dmalcolm@redhat.com>
 
== Current status ==
* Targeted release: Fedora 16? <!-- [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]] -->
* Last updated: 2011-05-03
* Percentage of completion: 30%


<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
Line 20: Line 26:
PyPy has been packaged within Fedora from Fedora 15 onwards, and is available via:
PyPy has been packaged within Fedora from Fedora 15 onwards, and is available via:


In Fedora 22 and later versions use [[dnf|DNF]]:
<pre>
<pre>
# dnf install pypy
yum install pypy
</pre>
</pre>


Or with YUM in Fedora 21 and earlier versions:
See the [https://bugzilla.redhat.com/show_bug.cgi?id=588941 package review])
<pre>
# yum install pypy
</pre>


We currently have PyPy-1.5


The latest updates of PyPy package information can be found at [https://bodhi.fedoraproject.org/updates/?packages=pypy Fedora Package Database]
There is a [https://bugzilla.redhat.com/showdependencytree.cgi?id=669836&hide_resolved=1 tracker bug for the PyPy stack] in Red Hat bugzilla.


See the [https://bugzilla.redhat.com/show_bug.cgi?id=588941 package review]
Areas of uncertainty:
* as of 1.4.1, support for .c extensions (using the CPython API) is still experimental (need to try some extensions and see what works)
* 1.4.1 ships with a bytecode format similar to (but slightly different from) CPython 2.5.1.  It's not yet clear to me what the anticipated rate of change to the bytecode format is.  If we build out a collection of pure-python extensions in RPM form (e.g. a pypy-django.rpm), with .pyc files, we don't want to be constantly having to rebuild them all as the precise bytecode format changes (even if we e.g. ported [http://www.python.org/dev/peps/pep-3147/ PEP 3147], we still ought to rebuild the RPMs)


There is a [https://bugzilla.redhat.com/showdependencytree.cgi?id=669836&hide_resolved=1 tracker bug for the PyPy stack] in Red Hat bugzilla.
Upstream work
* working on improving the readability of the 6 million lines of autogenerated C code emitted by the build; I've [http://codespeak.net/pipermail/pypy-dev/2010q4/006532.html sent patches upstream for this], but it's not yet finished.


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
[http://pypy.org/ PyPy] is a fast, compliant alternative implementation of the Python language (2.7.10). It has several advantages and distinct features. Thanks to its Just-in-Time compiler, Python programs often run faster on PyPy. Memory-hungry Python programs (several hundreds of MBs or more) might end up taking less space than they do in CPython.
[http://pypy.org/ PyPy] is a fast, compliant alternative implementation of the Python language (2.7.10). It has several advantages and distinct features. Thanks to its Just-in-Time compiler, Python programs often run faster on PyPy. Memory-hungry Python programs (several hundreds of MBs or more) might end up taking less space than they do in CPython.
This feature is exploring the idea of shipping PyPy, and the scope is not yet clear, be it:
# just the core interpreter, or
# sharing pure-Python add-on modules with the system Python (but with split bytecode files), or
# a full, independent Python stack, but with just pure-Python add-on modules, or
# a full, independent Python stack, with both pure-Python and machine-code extension modules


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 54: Line 66:


<!-- Please keep this table sorted alphabetically by python module name -->
<!-- Please keep this table sorted alphabetically by python module name -->
PyPy supports most of the commonly used Python standard library modules complete list [http://packages.pypy.org/ here]
An upstream guide to PyPy compatibility can be seen at https://bitbucket.org/pypy/compatibility/wiki/Home
{|
! Python Module !! Fedora CPython package !! PyPy Compatibility and Notes !! Fedora PyPy status
|-
|          || swig        || ||
|-
| cairo    || pycairo    || ||
|-
| coverage || python-coverage || ||
|-
| dbus    || dbus-python || ||
|-
| django  || Django      || ||
|-
| gtk      || pygtk2      || I filed an [https://codespeak.net/issue/pypy-dev/issue620 upstream bug relating to ./configure]; after that there are [https://codespeak.net/issue/pypy-dev/issue625 multiple compilation errors] ||
|-
| lxml    || python-lxml || ||
|-
| gobject  || pygobject2  || ||
|-
| MySQLdb  || MySQL-python || || {{bz|669835}}
|-
| numpy    || numpy      || ||
|-
| psycopg2 || python-psycopg2 || See also https://github.com/mvantellingen/psycopg2-ctypes ||
|-
| PyKDE4  || PyKDE4 (from the kdebindings srpm) || ||
|-
| PyQt4    || PyQt4      || ||
|-
| rpm      || rpm-python (subpackage of "rpm")|| ||
|-
| scipy    || scipy      || ||
|-
| selinux  || libselinux-python || (generated by SWIG during build of libselinux) ||
|-
| semanage || libsemanage-python || (generated by SWIG during build of libsemanage) ||
|-
| setuptools || python-setuptools || ( we've switched to the "Distribute" fork) || {{bz|669825}}
|-
| sip      || sip        || ||
|-
| sqlalchemy || python-sqlalchemy || ||
|-
| virtualenv || python-virtualenv || ||
|}


== How To Test ==
== How To Test ==

Latest revision as of 13:07, 14 April 2016

Old page
This page is a Feature page for Fedora 15 (that's history). It is not a general information page about PyPy in Fedora. Expect everything here to be outdated. Do not update it.


PyPy Stack

Summary

Fedora N+1 has an alternate Python 2 runtime and add-on module stack built using PyPy, an alternate implementation of the Python 2 language, featuring Just-in-Time compilation.

Owner

  • Email: <dmalcolm@redhat.com>

Current status

  • Targeted release: Fedora 16?
  • Last updated: 2011-05-03
  • Percentage of completion: 30%


PyPy has been packaged within Fedora from Fedora 15 onwards, and is available via: 

yum install pypy

See the package review)

We currently have PyPy-1.5

There is a tracker bug for the PyPy stack in Red Hat bugzilla.

Areas of uncertainty:

  • as of 1.4.1, support for .c extensions (using the CPython API) is still experimental (need to try some extensions and see what works)
  • 1.4.1 ships with a bytecode format similar to (but slightly different from) CPython 2.5.1. It's not yet clear to me what the anticipated rate of change to the bytecode format is. If we build out a collection of pure-python extensions in RPM form (e.g. a pypy-django.rpm), with .pyc files, we don't want to be constantly having to rebuild them all as the precise bytecode format changes (even if we e.g. ported PEP 3147, we still ought to rebuild the RPMs)

Upstream work

  • working on improving the readability of the 6 million lines of autogenerated C code emitted by the build; I've sent patches upstream for this, but it's not yet finished.

Detailed Description

PyPy is a fast, compliant alternative implementation of the Python language (2.7.10). It has several advantages and distinct features. Thanks to its Just-in-Time compiler, Python programs often run faster on PyPy. Memory-hungry Python programs (several hundreds of MBs or more) might end up taking less space than they do in CPython.

This feature is exploring the idea of shipping PyPy, and the scope is not yet clear, be it:

  1. just the core interpreter, or
  2. sharing pure-Python add-on modules with the system Python (but with split bytecode files), or
  3. a full, independent Python stack, but with just pure-Python add-on modules, or
  4. a full, independent Python stack, with both pure-Python and machine-code extension modules

Benefit to Fedora

PyPy is an innovative implementation of the Python language, but it can take an hour to build, requiring a powerful machine. By providing an easy way for people to install a PyPy stack, we continue to push Fedora as an excellent platform for Python developers.

Fedora aims to showcase the latest and greatest in Free/Open Source Software: PyPy is certainly innovative.

Fedora heavily uses Python, both within the operating system itself, and within the infrastructure used by the project. As PyPy becomes more mature we may eventually want to migrate from CPython to PyPy for some of these workloads.

Scope

An upstream guide to PyPy compatibility can be seen at https://bitbucket.org/pypy/compatibility/wiki/Home

Python Module Fedora CPython package PyPy Compatibility and Notes Fedora PyPy status
swig
cairo pycairo
coverage python-coverage
dbus dbus-python
django Django
gtk pygtk2 I filed an upstream bug relating to ./configure; after that there are multiple compilation errors
lxml python-lxml
gobject pygobject2
MySQLdb MySQL-python RHBZ #669835
numpy numpy
psycopg2 python-psycopg2 See also https://github.com/mvantellingen/psycopg2-ctypes
PyKDE4 PyKDE4 (from the kdebindings srpm)
PyQt4 PyQt4
rpm rpm-python (subpackage of "rpm")
scipy scipy
selinux libselinux-python (generated by SWIG during build of libselinux)
semanage libsemanage-python (generated by SWIG during build of libsemanage)
setuptools python-setuptools ( we've switched to the "Distribute" fork) RHBZ #669825
sip sip
sqlalchemy python-sqlalchemy
virtualenv python-virtualenv

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/PyPyStack&oldid=443169"