From Fedora Project Wiki
< SIGs
m (→Python Runtimes: use the "package" template) |
No edit summary |
||
| (50 intermediate revisions by 20 users not shown) | |||
| Line 5: | Line 5: | ||
== Python Special Interest Group == | == Python Special Interest Group == | ||
A SIG for people who are interested in Python on Fedora. This includes | A SIG for people who are interested in Python on Fedora. This includes: | ||
packaging and optimizing the various Python 2 and Python 3 [ | * packaging and optimizing the various Python 2 and Python 3 [[#Python_Runtimes|Python runtimes]] | ||
* packaging Python libraries and applications | |||
* setting and improving [[Packaging:Python|standards for packaging them as RPMs]] | |||
* maintaining Python packages for Fedora | |||
=== Contact Info === | === Contact Info === | ||
Mailing List: [ | Mailing List for general discussions: [https://lists.fedoraproject.org/mailman/listinfo/python-devel python-devel] <BR> | ||
IRC: #fedora-python on irc.freenode.net <BR> | IRC: #fedora-python on irc.freenode.net <BR> | ||
=== Python SIG FAS group === | |||
You can add [https://admin.fedoraproject.org/pkgdb/packager/group::python-sig/ 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. | |||
To apply for the group, please apply: | |||
* at the [https://admin.fedoraproject.org/accounts/group/view/python-sig FAS group] | |||
* for the [https://lists.fedoraproject.org/mailman/listinfo/python-sig python-sig] mailing list. | |||
Unfortunately, this python-sig group is restricted because there are also security sensitive mails send out. | |||
As this process is currently in alpha phase, we will update this section, when it is clearer how to join the python-sig... | |||
The current list of packages maintained by the python-sig can be found at the [https://admin.fedoraproject.org/pkgdb/packager/group::python-sig/ package database]. | |||
=== Members === | === Members === | ||
[[User: | [[MartinBacovsky| Martin Bacovsky]] <BR> | ||
[[User:lbazan | Luis Bazán]] <BR> | |||
[[AurelienBompard| Aurelien Bompard]] <BR> | |||
[[User:Ncoghlan | Nick Coghlan]] <BR> | |||
[[User:Kushal | Kushal Das]] <BR> | |||
[[User:Lupinix | Christian Dersch]] <BR> | |||
[[TejasDinkar| Tejas Dinkar]] <BR> | |||
[[User:Tadej | Tadej Janež]] <BR> | |||
[[User:Bkabrda | Bohuslav Kabrda]] <BR> | |||
[[User:Mstuchli | Matej Stuchlik]] <BR> | |||
[[User:topdog| Andrew Colin Kissa]] <BR> | |||
[[ToshioKuratomi| Toshio Kuratomi]] <BR> | |||
[[AlexLancaster| Alex Lancaster]] <BR> | |||
[[TimLauridsen| Tim Lauridsen]] <BR> | [[TimLauridsen| Tim Lauridsen]] <BR> | ||
[[JoseMatos| José Matos]] <BR> | |||
[[LukeMacken| Luke Macken]] <BR> | |||
[[User:potty | Abdel Martínez]] <BR> | |||
[[DaveMalcolm| Dave Malcolm]]: interested in core Python runtimes and low-level implementation details <BR> | |||
[[PaulNasrat| Paul Nasrat]] <BR> | [[PaulNasrat| Paul Nasrat]] <BR> | ||
[[ | [[User:Jamielinux | Jamie Nguyen]] <BR> | ||
[[ | [[User:Tradej | Tomas Radej]] <BR> | ||
[[MichelSalim| Michel Salim]] <BR> | [[MichelSalim| Michel Salim]] <BR> | ||
[[ | [[FelixSchwarz| Felix Schwarz]] <BR> | ||
[[ | [[User:Tomspur| Thomas Spura]] <BR> | ||
[[ChristosTrochalakis| Christos Trochalakis]] <BR> | [[ChristosTrochalakis| Christos Trochalakis]] <BR> | ||
[[ | [[User:Ramkrsna | Ramakrishna Reddy Yekulla]] <BR> | ||
[[ | [[User:Ivazquez| Ignacio Vazquez-Abrams]] <BR> | ||
[[ | [[User:Kumarpraveen | Praveen Kumar]] <BR> | ||
[[User:raphgro | Raphael Groner]] <BR> | |||
[[User:Athmane | Athmane Madjoudj]] <BR> | |||
[[User:rkuska | Robert Kuska]] <BR> | |||
=== Python packages awaiting review === | === Python packages awaiting review === | ||
* [https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&short_desc=python&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&bug_status=POST&short_desc_type=allwordssubstr&component=Package%20Review&product=Fedora List of most python packages awaiting review] - Bugzilla query for packages which have not passed review with "python" in the name or summary. | |||
* [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 === | ||
* [http://chandlerproject.org Chandler PIM] | * [http://chandlerproject.org 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. | ||
* [http://www.hforge.org/itools/ 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 | * [http://www.hforge.org/itools/ 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 | ||
[https://bugzilla.redhat.com/show_bug.cgi?id=1181317 review request] | |||
* [http://code.google.com/p/python-multiprocessing/ python-multiprocessing] - multiprocessing backport useful for EL-5 | * [http://code.google.com/p/python-multiprocessing/ python-multiprocessing] - multiprocessing backport useful for EL-5 [https://bugzilla.redhat.com/show_bug.cgi?id=716667 review request] | ||
* [http://pypi.python.org/pypi/repoze.profile repoze.profile] - WSGI profiling middleware | * [http://pypi.python.org/pypi/repoze.profile repoze.profile] - WSGI profiling middleware | ||
* [http://code.google.com/p/tgscheduler/ tgscheduler] - TurboGears scheduler | * [http://code.google.com/p/tgscheduler/ tgscheduler] - TurboGears scheduler | ||
| Line 51: | Line 90: | ||
[[PackagingDrafts/TGApps| Packaging TurboGears Applications]] <BR> | [[PackagingDrafts/TGApps| Packaging TurboGears Applications]] <BR> | ||
[[Packaging:Python Eggs| Packaging Python Eggs]] <BR> | [[Packaging:Python Eggs| Packaging Python Eggs]] <BR> | ||
Parallel installable [[Python26]] information (mainly EPEL5).<br/> | |||
[http://farmdev.com/talks/unicode/ Unicode in Python, Completely Demystified] | [http://farmdev.com/talks/unicode/ Unicode in Python, Completely Demystified] | ||
| Line 58: | Line 98: | ||
=== Upstream Release Schedules === | === Upstream Release Schedules === | ||
[http://python.org/dev/peps/pep- | [http://www.python.org/dev/peps/pep-0429/ Python 3.4] | ||
=== Python Features === | === Python Features === | ||
==== | ==== Future work ==== | ||
* [[Features/Python3ForCriticalComponents|port anaconda and yum to python 3]] | |||
* [[Features/DebugPythonStacks|debug versions of Python 2 and Python 3 in addition to the traditional optimized builds]] | * [[Features/DebugPythonStacks|debug versions of Python 2 and Python 3 in addition to the traditional optimized builds]] | ||
* [[Features/PyPyStack|add PyPy to Fedora, possibly with a stack of extensions]] | |||
* [[Features/JythonStack|add a stack of extensions to Jython, in RPM form]] | |||
* [[Features/PythonNamingDependingOnImplementation | Rename python packages to reflect python implementation in the name]] | |||
==== Under development (Fedora 18) ==== | |||
* [[Features/Python_3.3|upgrade of the Python 3 stack to 3.3]] | |||
==== Added in Fedora 17 ==== | |||
* [[Features/StaticAnalysisOfPythonRefcounts| further work on static analysis of refcounting]] | |||
==== Added in Fedora 16 ==== | |||
* [[Features/GccPythonPlugin|GCC plugin embedding Python, for writing GCC extensions in Python]] | |||
* [[Features/StaticAnalysisOfCPythonExtensions|Static analysis tool to detect common mistakes made in Python extension modules written in C]] | |||
==== Added in Fedora 15 ==== | |||
* [[Features/Python_3.2|upgrade of the Python 3 stack to 3.2]] | * [[Features/Python_3.2|upgrade of the Python 3 stack to 3.2]] | ||
==== | ==== Added in Fedora 14 ==== | ||
* [[Features/Python_2.7|upgrade of the Python 2 stack to 2.7]] | * [[Features/Python_2.7|upgrade of the Python 2 stack to 2.7]] | ||
* pypy was packaged, available prebuilt via rpm | |||
==== Added in Fedora 13 ==== | ==== Added in Fedora 13 ==== | ||
| Line 79: | Line 135: | ||
==== Added in Fedora 10 ==== | ==== Added in Fedora 10 ==== | ||
* [[Features/PythonNSS|created and packaged bindings for the FIPS-validated NSS cryptographic library]] | * [[Features/PythonNSS|created and packaged bindings for the FIPS-validated NSS cryptographic library]] | ||
==== Stalled features ==== | |||
* [[Features/SystemPythonExecutablesUseSystemPython]] | |||
=== Python Runtimes === | === Python Runtimes === | ||
'''Within Fedora:''' | '''Within Fedora:''' | ||
* {{package|python}} - The standard "CPython" implementation of Python 2 | * {{package|python}} - The standard "CPython" implementation of Python 2 | ||
* {{package|python3}} - As above, for Python 3 | * {{package|python3}} - As above, for Python 3. There's a separate page detailing the [[Python3|status of building up a stack of pre-packaged Python 3 modules]] | ||
* {{package|jython}} - Python 2 implementation on top of the Java virtual machine | * {{package|jython}} - Python 2 implementation on top of the Java virtual machine | ||
* {{package| | * {{package|pypy}} - An alternate [http://pypy.org/ python 2 interpreter (with a JIT-compiler) written in a subset of python, compiled to .c]. The interpreter has [http://morepypy.blogspot.com/2009/10/gc-improvements.html better memory] use than CPython and speed is closing in on CPython. The JIT'd version is faster than CPython in many [http://speed.pypy.org benchmarks]. It is growing the ability to [http://morepypy.blogspot.com/2010/04/using-cpython-extension-modules-with.html load CPython extension modules], though this is in an "alpha" state right now. | ||
'''Within EPEL:''' | |||
* {{package|python26}} - [[Python26|Python 2.6 stack for EPEL5]], parallel-installable with the system Python 2.4 stack | |||
'''Awaiting review:''' | '''Awaiting review:''' | ||
* [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] | ||
'''Awaiting packaging''' | '''Awaiting packaging''' | ||
* IronPython | * IronPython | ||
** [http://code.google.com/p/ironclad/ Ironclad] CPython extensions from IronPython | |||
* [http://code.google.com/p/python-on-a-chip/ Python-on-a-Chip (p14p)] | |||
=== Python Compilers === | |||
'''Within Fedora:''' | |||
* {{package|pyjamas}} - Python-to-JavaScript compiler, implemented in Python | |||
* {{package|shedskin}} - Python to C++ compiler (for a subset of Python with "implicit types") | |||
[[Category:Fedora special-interest groups|Python SIG]] | [[Category:Fedora special-interest groups|Python SIG]] | ||
Revision as of 10:22, 15 January 2015
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 for general discussions: 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.
To apply for the group, please apply:
- at the FAS group
- for the python-sig mailing list.
Unfortunately, this python-sig group is restricted because there are also security sensitive mails send out. As this process is currently in alpha phase, we will update this section, when it is clearer how to join the python-sig...
The current list of packages maintained by the python-sig can be found at the package database.
Members
Martin Bacovsky
Luis Bazán
Aurelien Bompard
Nick Coghlan
Kushal Das
Christian Dersch
Tejas Dinkar
Tadej Janež
Bohuslav Kabrda
Matej Stuchlik
Andrew Colin Kissa
Toshio Kuratomi
Alex Lancaster
Tim Lauridsen
José Matos
Luke Macken
Abdel Martínez
Dave Malcolm: interested in core Python runtimes and low-level implementation details
Paul Nasrat
Jamie Nguyen
Tomas Radej
Michel Salim
Felix Schwarz
Thomas Spura
Christos Trochalakis
Ramakrishna Reddy Yekulla
Ignacio Vazquez-Abrams
Praveen Kumar
Raphael Groner
Athmane Madjoudj
Robert Kuska
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
Within EPEL:
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: