[MIR] pypy
Bug #1352900 reported by
Barry Warsaw
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pypy (Ubuntu) |
Fix Released
|
Undecided
|
Barry Warsaw | ||
Bug Description
This is a placeholder for further thought and discussion, possibly leading to a proper MIR. Quoting IRC:
> a lot of packages start building modules for pypy. any opinion about having it in main? currently we just disabled these
> hmm. haven't thought about it too much, but i like that folks are starting to support pypy better, and i don't like carrying deltas just to manage this distinction. maybe we should MIR pypy...
| Changed in pypy (Ubuntu): | |
| assignee: | nobody → Barry Warsaw (barry) |
Revision history for this message
| Barry Warsaw (barry) wrote | #1 |
Revision history for this message
| Barry Warsaw (barry) wrote | #2 |
Revision history for this message
| Matthias Klose (doko) wrote | #3 |
Download full text (3.4 KiB)
| Changed in pypy (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
[Availability]
pypy has been available since Precise. It builds on all architectures except armel and armhf. PyPy requires >= 1400 MiB on 32 bit systems to build.
[Rationale]
Upstream: http://
PyPy is an important and popular alternative implementation of the Python language. For many workloads it can provide better performance than the standard CPython implementation. It includes a JIT, and may provide better memory footprint for some applications. We want to start building Python packages which are compatible with PyPy so that our users can choose PyPy for their projects where appropriate.
[Security]
There are no known CVEs for PyPy. No known security issues in Ubuntu. /usr/bin scripts are not setuid/setgid and there are no /sbin or /usr/sbin scripts in the pypy package. PyPy includes no init scripts and by itself does not open any ports. (Of course, Python programs executed with PyPy could open such ports, but that's no different from any other Python interpreter.)
[Quality assurance]
PyPy is an active and well supported project upstream. It is generally invoked in a manner similar to CPython; it has an interactive interpreter and can be used in shebang lines. PyPy is actively supported in Debian and there is no delta in Ubuntu. The number of bug reports in both trackers is not huge out of hand. It has a debian/watch file.
[Dependencies]
All of its binary and build dependencies are already in main.
[Standards compliance]
To the best of my knowledge, there are no known violations of FHS or Debian policy.
[Maintenance]
In Debian, PyPy currently has a single maintainer, and it is well-maintained. Under Ubuntu, the same developers currently maintaining the CPython stack would be additionally responsible for maintaining PyPy.
[Background information]
PyPy itself is compatible with the Python 2 language specification. PyPy3 compatible with the Python 3 language specification was announced on June 20, 2014 but it is not currently available in Debian or Ubuntu (LP: #1363896). At some point we should package PyPy3 for Debian and pull it into Ubuntu, where it should have the same status as the PyPy package. There are no current plans to do this though.