No edit summary |
(Clean up last commit which adds a quickstart to packaging section) |
||
Line 44: | Line 44: | ||
* [https://bugzilla.redhat.com/show_bug.cgi?id=593069 pynie] - Python 3, on top of the [https://admin.fedoraproject.org/pkgdb/acls/name/parrot Parrot virtual machine] | * [https://bugzilla.redhat.com/show_bug.cgi?id=593069 pynie] - Python 3, on top of the [https://admin.fedoraproject.org/pkgdb/acls/name/parrot Parrot virtual machine] | ||
=== Packaging Quickstart === | |||
If you're just getting started with packaging python modules for Fedora, here's some hints to get you started: | |||
* The [[Packaging:Guidelines Fedora Packaging Guidelines]] must be followed for any package. The [[Packaging:Python Python specific guidelines]] are a good starting point. | |||
* You can generate a spec template for your new python package like this: <pre>yum install rpmdevtools && rpmdev-newspec -t python</pre>. That will generate a spec file template that is a good starting point to making your package. | |||
=== Package requests === | === Package requests === | ||
Line 52: | Line 59: | ||
* [http://code.google.com/p/tgscheduler/ tgscheduler] - TurboGears scheduler | * [http://code.google.com/p/tgscheduler/ tgscheduler] - TurboGears scheduler | ||
=== Links === | === Links === | ||
Revision as of 19:32, 4 May 2013
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
Members
Ignacio Vazquez-Abrams
Tim Lauridsen
Paul Nasrat
Toshio Kuratomi
Tejas Dinkar
Aurelien Bompard
José Matos
Michel Salim
Alex Lancaster
Luke Macken
Christos Trochalakis
FelixSchwarz
Dave Malcolm: interested in core Python runtimes and low-level implementation details
Martin Bacovsky
Thomas Spura
Andrew Colin Kissa
Abdel Martínez
Luis Bazán
Bohuslav Kabrda
Ramakrishna Reddy Yekulla
Kushal Das
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.
- pynie - Python 3, on top of the Parrot virtual machine
Packaging Quickstart
If you're just getting started with packaging python modules for Fedora, here's some hints to get you started:
- The Packaging:Guidelines Fedora Packaging Guidelines must be followed for any package. The Packaging:Python Python specific guidelines are a good starting point.
- You can generate a spec template for your new python package like this:
yum install rpmdevtools && rpmdev-newspec -t python
. That will generate a spec file template that is a good starting point to making your package.
Package requests
- Chandler PIM - I don't think it is such hot idea ... upstream is pinning for the fjords, and after couple of years of non-development, it is not that advanced as it used to be.
- itools - A python library that includes several useful tools, such as an ODF anonymizer that can be used to sanitize confidential documents before attaching them tp bug reports
- python-multiprocessing - multiprocessing backport useful for EL-5 review request
- repoze.profile - WSGI profiling middleware
- tgscheduler - TurboGears scheduler
Links
Python website
Building Python packages
TurboGears
Packaging TurboGears Applications
Packaging Python Eggs
Parallel installable Python26 information (mainly EPEL5).
Unicode in Python, Completely Demystified
Upstream Release Schedules
Python Features
Future work
- port anaconda and yum to python 3
- debug versions of Python 2 and Python 3 in addition to the traditional optimized builds
- add PyPy to Fedora, possibly with a stack of extensions
- add a stack of extensions to Jython, in RPM form
- Rename python packages to reflect python implementation in the name
Under development (Fedora 18)
Added in Fedora 17
Added in Fedora 16
- GCC plugin embedding Python, for writing GCC extensions in Python
- Static analysis tool to detect common mistakes made in Python extension modules written in C
Added in Fedora 15
Added in Fedora 14
- upgrade of the Python 2 stack to 2.7
- pypy was packaged, available prebuilt via rpm
Added in Fedora 13
- parallel-installable Python 3 stack
- gdb hooks to make it easier to debug Python and extension modules
- Systemtap probe points for tracing Python function calls
Added in Fedora 11
Added in Fedora 10
Stalled features
Python Runtimes
Within Fedora:
python
- The standard "CPython" implementation of Python 2python3
- As above, for Python 3. There's a separate page detailing the status of building up a stack of pre-packaged Python 3 modulesjython
- Python 2 implementation on top of the Java virtual machinepypy
- 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
Awaiting review:
- pynie - Python 3, on top of the Parrot virtual machine
Awaiting packaging
- IronPython
- Ironclad CPython extensions from IronPython
- Python-on-a-Chip (p14p)
Python Compilers
Within Fedora: