SIGs/Python: Difference between revisions

Revision as of 12:26, 22 August 2016

Python Special Interest Group

A SIG for people who are interested in Python on Fedora. This includes:

packaging and optimizing the various Python 2 and Python 3 Python runtimes
packaging Python libraries and applications
setting and improving standards for packaging them as RPMs
maintaining Python packages for Fedora

Contact Info

Mailing List: python-devel
IRC: #fedora-python on irc.freenode.net

Python SIG FAS group

You can add group::python-sig to your package so the core members of the python-sig get notified on each bug in your python program. This way it is possible to maintain all python packages with the group permissions, which will simplify general python cleanup changes.

If there is interest and shown familiarity with our guidelines and processes (which usually manifests in maintaining at least 5 to 10 Python packages) you can apply for having access to a broader group of packages that is commonly maintained. If you choose to apply for this, please discuss it with a sponsor of the python-sig. (You can find a list of those in FAS.)

The current list of packages maintained by the python-sig can be found at the package database.

Members of Python SIG

Python packages awaiting review

List of most python packages awaiting review - Bugzilla query for packages which have not passed review with "python" in the name or summary.

Packaging Quickstart

If you're just getting started with packaging python modules for Fedora, here's some hints to get you started:

The Fedora Packaging Guidelines must be followed for any package. The Python specific guidelines are a good starting point.
You can generate a spec template for your new python package like this:
```
dnf install rpmdevtools && rpmdev-newspec -t python
```
That will generate a spec file template that is a good starting point to making your package.
When packaging PyPI project you can generate the initial SPEC file using pyp2rpm tool.

Links

Python website
Python packaging Guidelines
Packaging Python Eggs (outdated – needs update to pip & friends)
Python Patches – patches to python2 and python3 in Fedora and EL

Unicode in Python, Completely Demystified (somewhat outdated)

Upstream Release Schedules

Python Features

Future work

Under development (Fedora 26)

Update of the Python 3 stack to 3.6

Older Changes

See the History of Python Changes

Porting to Python 3

Currently there is an ongoing effort to port packages from Python 2 to Python 3, for the packages where upstream supports Python 3, so the package can provide either two subpackages for Python 2 and Python 3 respectively, or only the Python 3 version.

Contributors interested in porting packages are encouraged to read the Python RPM Porting Guide

People who successfully port a number of packages are awarded the Parselmouth badge, and a separate wiki page is maintained with contributor's names and the packages they ported: Python 3 Log

You can track the overall progress at Fedora Porting Database.

Python Runtimes

Within Fedora:

python - The standard "CPython" implementation of Python 2
python3 - As above, for Python 3. There's a separate page detailing the status of building up a stack of pre-packaged Python 3 modules
jython - Python 2 implementation on top of the Java virtual machine
pypy - An alternate python 2 interpreter (with a JIT-compiler) written in a subset of python, compiled to .c. The interpreter has better memory use than CPython and speed is closing in on CPython. The JIT'd version is faster than CPython in many benchmarks. It is growing the ability to load CPython extension modules, though this is in an "alpha" state right now.

Within EPEL:

python26 - Python 2.6 stack for EPEL5, parallel-installable with the system Python 2.4 stack
python34 - Python 3.4 stack for EPEL7

Awaiting review:

Awaiting packaging:

Python Compilers