From Fedora Project Wiki
(IRC -> Matrix)
 
(30 intermediate revisions by 9 users not shown)
Line 4: Line 4:
-->
-->


{{admon/important | Help wanted! | You can help with this stuff! Join us on '''<nowiki>#fedora-python </nowiki>''' on Freenode! }}
{{admon/important | Help wanted! | You can help with this stuff! Join us on [https://chat.fedoraproject.org/#/room/#python:fedoraproject.org Fedora Python Matrix]! }}


== Python Special Interest Group ==
== Python Special Interest Group (SIG) ==


[https://www.python.org/ Python] is a high-level, interpreted programming language which emphasizes on code readability. [https://pagure.io/fedora-loves-python/ Fedora loves Python] and this SIG is for people who would like to see this relationship flourish. We aim to address the issues and tasks related to '''everything-Python''' on Fedora which includes:
[https://www.python.org/ Python] is a high-level, interpreted programming language which emphasizes on code readability. [https://fedoralovespython.org Fedora loves Python] and this SIG is for people who would like to see this relationship flourish. We aim to address any and all issues and tasks related to Python in Fedora, including:


* Packaging and optimizing the various Python 2 and Python 3 [[#Python_Runtimes|runtimes]]
* packaging and optimizing the various [[#Python_Runtimes|Python runtimes]],
* Packaging Python libraries and applications
* packaging Python libraries and applications,
* Setting and improving [[Packaging:Python|standards for packaging them as RPMs]]
* setting and improving [[Packaging:Python|standards for packaging them as RPMs]],
* Maintaining Python packages for Fedora
* maintaining Python packages for Fedora


and much more...
and much more...
Line 21: Line 21:
=== Mailing lists ===
=== Mailing lists ===


{|
{| class="wikitable"
! Address !! Function
! Address !! Function
|-
|-
| [https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/ python-devel] || General mailing list for all things Python related
| {{fplist|python-devel}} || General mailing list for all things Python related
|-
|-
|}
|}




=== IRC ===
=== Matrix ===


{|
{| class="wikitable"
! Address !! Function
! Address !! Function
|-
|-
| [https://webchat.freenode.net/?channels=#fedora-python  #fedora-python] || [https://fedoraproject.org/wiki/SIGs/Python Python SIG] official channel
| [[https://chat.fedoraproject.org/#/room/#python:fedoraproject.org Fedora Python] || [https://fedoraproject.org/wiki/SIGs/Python Python SIG] official channel
|}
|}
{{admon/tip|Zodbot|Read the [[Zodbot]] page for helpful [[IRC]] commands.}}




Line 58: Line 56:
=== Packaging and maintaining Python applications ===
=== Packaging and maintaining Python applications ===


If you're just getting started with packaging Python modules for Fedora, here's some hints to get you started:
If you're just getting started with packaging Python modules for Fedora, here are 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.
* The [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Fedora Packaging Guidelines] must be followed for any package.  The [https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ Python specific guidelines] are a good starting point.
* You can generate a spec template for your new python package like this: <pre>dnf install rpmdevtools && rpmdev-newspec -t python</pre> 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 [https://src.fedoraproject.org/rpms/pyp2rpm pyp2rpm] tool.
* When packaging PyPI project you can generate the initial SPEC file using [https://apps.fedoraproject.org/packages/pyp2rpm pyp2rpm] tool.
* You can generate a spec template for your new python package like this: <pre>dnf install rpmdevtools && rpmdev-newspec -t python</pre> That will generate a spec file template that is a good starting point to making your package. (Beware, the template might be outdated.)


==== Python SIG FAS group ====
==== Python SIG FAS group ====


You can add [https://admin.fedoraproject.org/pkgdb/packager/group::python-sig/ group::python-sig] to your package so the [https://fedoraproject.org/wiki/SIGs/Python/Members_list 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.
You can add [https://src.fedoraproject.org/group/python-packagers-sig python-packagers-sig] group to your package so the [https://fedoraproject.org/wiki/SIGs/Python/Members_list core members] of the python-packagers-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 [https://admin.fedoraproject.org/accounts/group/members/python-sig/*/sponsor in FAS].)
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-packagers-sig. (You can find a list of those [https://accounts.fedoraproject.org/group/python-packagers-sig/ in FAS].)


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].
The current list of packages maintained by the python-packagers-sig can be found at the [https://src.fedoraproject.org/group/python-packagers-sig src.fedoraproject.org].
 
The [https://packager-dashboard.fedoraproject.org/dashboard?groups=python-packagers-sig packaging dashboard of the Python SIG FAS group] might serve as a place to start contributing.


=== Review Python packages ===
=== Review Python packages ===
Line 77: Line 77:
* Bugzilla query for packages which have not passed review with "python" in the name or summary.
* Bugzilla query for packages which have not passed review with "python" in the name or summary.


=== Porting to Python3 ===
=== 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. This effort aims to completely shift to Python 3 before [https://pythonclock.org/ Python 2 retires in 2020].
 
Contributors interested in porting packages are encouraged to read the [http://python-rpm-porting.readthedocs.io Python RPM Porting Guide]


People who successfully port a number of packages are awarded the [https://badges.fedoraproject.org/badge/parselmouth parselmouth badge], and a separate wiki page is maintained with contributor's names and the packages they ported:  [[Open_Badges/Python3Log| Python 3 Log]]
Python 2 is dead upstream as of January 2020. Thankfully the switch from Python 2 to Python 3 in Fedora is nearly finished, see our [http://fedora.portingdb.xyz/ Fedora Porting Database].


You can track the overall progress at [http://fedora.portingdb.xyz/ Fedora Porting Database].
If your project still doesn't work on Python 3, we recommend trying the [https://portingguide.readthedocs.io/ Conservative Python 3 Porting Guide].


=== Other ===
=== Other ===
Line 100: Line 96:
[https://www.python.org/dev/peps/pep-0494/ Python 3.6]
[https://www.python.org/dev/peps/pep-0494/ Python 3.6]


[https://www.python.org/dev/peps/pep-0537/ Python 3.7]


== Python Features ==
[https://www.python.org/dev/peps/pep-0569/ Python 3.8]
 
=== Future work ===
 
* [[Features/PythonNamingDependingOnImplementation | Rename Python packages to reflect Python implementation in the name]].


=== Under development (Fedora 26) ===
[https://www.python.org/dev/peps/pep-0596/ Python 3.9]


* [[Changes/python3.6|Update of the Python3 stack to 3.6]]
[https://www.python.org/dev/peps/pep-0619/ Python 3.10]


=== Older Changes ===
== Python Fedora Changes ==


See the [[SIGs/Python/features_history| History of Python Changes]]
See the [[SIGs/Python/features_history| History of Python Changes]]


== Toolbox ==
== Toolbox ==
Line 122: Line 114:
==== Within Fedora: ====
==== Within Fedora: ====


* {{package|python}} - The standard "CPython" implementation of Python 2
 
* {{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|python3}} RPM package - The standard CPython implementation of Python 3
** The component name changes based on the version, currently {{package|python3.9}}
* {{package|python2}} - The legacy CPython implementation of Python 2
* {{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|pypy}} and {{package|pypy3}} - An alternate [http://pypy.org/ Python 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].
* {{package|pypy}} and {{package|pypy3}} - An alternate [http://pypy.org/ Python 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].
* {{package|python35}}, {{package|python34}}, {{package|python33}} and {{package|python26}} are there so you can test you code on all of those. Just <code>dnf install tox</code> on Fedora 25+ to get it all.
* Alternative Python versions so you can test you code on all of them. Just <code>dnf install tox</code> on Fedora 25+ to get them all.
** {{package|python3.9}}
** {{package|python3.8}}
** {{package|python3.7}}
** {{package|python3.6}}
** {{package|python3.5}}
** {{package|python34}} (retired in F33+)
** {{package|python33}} (retired on F29+)
** {{package|python2.7}}
** {{package|python26}} (retired in F33+)


==== Within EPEL: ====
==== Within EPEL: ====


* {{package|python26}} - [[Python26|Python 2.6 stack for EPEL5]], parallel-installable with the system Python 2.4 stack
* {{package|python34}} - Python 3.4 stack for EPEL6 and EPEL7
* {{package|python34}} - Python 3.4 stack for EPEL7
* {{package|python36}} - Python 3.6 stack for EPEL7
 
 
<!--
'''Awaiting review:'''


'''Awaiting packaging:''' -->
=== Python Compilers ===
=== Python Compilers ===


Line 143: Line 141:
* {{package|pyjamas}} - Python-to-JavaScript compiler, implemented in Python
* {{package|pyjamas}} - Python-to-JavaScript compiler, implemented in Python
* {{package|shedskin}} -  Python to C++ compiler (for a subset of Python with "implicit types")
* {{package|shedskin}} -  Python to C++ compiler (for a subset of Python with "implicit types")


== Important Links ==
== Important Links ==
 
* Python in Fedora
* [http://www.python.org/ Python website] <BR>
** [[Packaging:Python| Python packaging Guidelines]]
* [[Packaging:Python| Python packaging Guidelines]] <BR>
** [https://fedoralovespython.org/ Fedora Loves Python] site ([https://github.com/fedora-python/fedoralovespython.org source repo])
* [[Packaging:Python Eggs|  Packaging Python Eggs]] (outdated – needs update to <code>pip</code> & friends)<BR>
** [https://developer.fedoraproject.org/tech/languages/python/python-installation.html Python section in the Fedora Developer Portal] (remember to update this as recommendations and the available tooling change!
* [[SIGs/Python/PythonPatches| Python Patches]] – patches to <code>python2</code> and <code>python3</code> in Fedora and EL <BR>
** [[SIGs/Python/PythonPatches| Python Patches]] – registry of patch numbers for Python interpreters in Fedora and EL
* [http://farmdev.com/talks/unicode/ Unicode in Python, Completely Demystified] (somewhat outdated)
** [https://hackmd.io/9f64YNIZTCy0ZzKb5wKtqQ?view Fedora Python interpreters maintenance guide]
* General Python links
** [http://www.python.org/ Python website]
** [https://portingguide.readthedocs.io The Conservative Python 3 Porting Guide]
* Obsolete
** [http://farmdev.com/talks/unicode/ Unicode in Python, Completely Demystified] (somewhat outdated)
** [[Packaging:Python Eggs|  Packaging Python Eggs]] (outdated – needs update to <code>pip</code> & friends)
** [https://python-rpm-porting.readthedocs.io/ Python RPM Porting Guide]


[[Category:SIGs]]
[[Category:SIGs]]

Latest revision as of 11:14, 20 February 2024


Help wanted!
You can help with this stuff! Join us on Fedora Python Matrix!

Python Special Interest Group (SIG)

Python is a high-level, interpreted programming language which emphasizes on code readability. Fedora loves Python and this SIG is for people who would like to see this relationship flourish. We aim to address any and all issues and tasks related to Python in Fedora, including:

and much more...

Communicate

Mailing lists

Address Function
python-devel General mailing list for all things Python related


Matrix

Address Function
[Fedora Python Python SIG official channel


Core Members

See SIGs/Python/Members_list for a list of our current core members.


Join Python SIG

We're always looking for new members to join us. Whether you're a new contributor or someone that's been around since the beginning, there are definitely ways you can help. Join Python SIG and:

  • Learn how to package new Python software
  • Work with teammates from the four corners of the world
  • Broaden your scope of working in open source communities and gain experience interacting in different areas
  • Build your portfolio by working on real-world projects

Join the Python SIG now

Areas of contribution

Packaging and maintaining Python applications

If you're just getting started with packaging Python modules for Fedora, here are 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.
  • When packaging PyPI project you can generate the initial SPEC file using pyp2rpm tool.
  • 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. (Beware, the template might be outdated.)

Python SIG FAS group

You can add python-packagers-sig group to your package so the core members of the python-packagers-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-packagers-sig. (You can find a list of those in FAS.)

The current list of packages maintained by the python-packagers-sig can be found at the src.fedoraproject.org.

The packaging dashboard of the Python SIG FAS group might serve as a place to start contributing.

Review Python packages

If you are one of the experienced Python packagers, you can help with the list of Python packages awaiting review.

  • Bugzilla query for packages which have not passed review with "python" in the name or summary.

Porting to Python 3

Python 2 is dead upstream as of January 2020. Thankfully the switch from Python 2 to Python 3 in Fedora is nearly finished, see our Fedora Porting Database.

If your project still doesn't work on Python 3, we recommend trying the Conservative Python 3 Porting Guide.

Other

Interested for more? Check out our github repositories for various projects related to Python and Fedora.

Upstream Release Schedules

Python 2.7

Python 3.4

Python 3.5

Python 3.6

Python 3.7

Python 3.8

Python 3.9

Python 3.10

Python Fedora Changes

See the History of Python Changes

Toolbox

Python Runtimes

Within Fedora:

Within EPEL:

  • python34 - Python 3.4 stack for EPEL6 and EPEL7
  • python36 - Python 3.6 stack for EPEL7

Python Compilers

Within Fedora:

  • pyjamas - Python-to-JavaScript compiler, implemented in Python
  • shedskin - Python to C++ compiler (for a subset of Python with "implicit types")

Important Links

Retrieved from "https://fedoraproject.org/w/index.php?title=SIGs/Python&oldid=701586"