From Fedora Project Wiki

Multiple Python Runtimes

In Fedora we have multiple python runtimes, one for each supported major release. At this point that's one for Python 2.7 and one for Python 3.4

Each runtime corresponds to a binary of the form /usr/bin/python$MAJOR.$MINOR

One of these python runtimes is the "system runtime" which is what we run when invoking /usr/bin/python. On Fedora 22 this is /usr/bin/python3.4

All python runtimes have a virtual provide for python(abi) = $MAJOR-$MINOR. For example, the python-3.4 runtime rpm has:

 $ rpm -q --provides python3 |grep -i abi
 python(abi) = 3.4

python modules using these runtimes should have a corresponding "Requires" line on the python runtime that they are used with. This is done automatically for files below /usr/lib[^/]*/python${PYVER}

Test your work
Remember to test the built RPMs and verify that they actually work! For instance, when you're packaging a python module that builds for both Python 2 and Python 3, don't test the Python 3 module but ship the Python 2 module without testing that it does what it's supposed to.
For packagers of the python interpreter
Unlike the Requires lines, the "Provides" for each runtime are manually entered into the specfile for each runtime. In theory /usr/lib/rpm/ would also automatically generate "Provides" lines for the runtime, but in practice rpmbuild only invokes it for files in the rpm payload identified as "python" by the file utility, and the runtime is an ELF binary, not a python script, hence it isn't passed. It's simplest to manually supply the Provides line, rather than change these innards of rpmbuild. See Red Hat Bug 532118.


To build a package containing Python 2 files, you need to have

BuildRequires: python2-devel

Similarly, when building a package which ships Python 3 files, you need

BuildRequires: python3-devel

A package that has both Python 2 and Python 3 files will need to BuildRequire both.


Note that the use of %{!? [...]} does allow this to work without the check for rhel versions but putting the conditional in documents when we can remove the entire stanza from the spec file.

In Fedora 13 and greater, the following macros are defined for you:

Macro Normal Definition Notes
__python2 /usr/bin/python2 Python 2 interpreter. Also the default python interpreter
__python3 /usr/bin/python3 Python 3 interpreter
python2_sitelib /usr/lib/python2.X/site-packages Where pure python2 modules are installed
python2_sitearch /usr/lib64/python2.X/site-packages on x86_64
/usr/lib/python2.X/site-packages on x86
Where python2 extension modules that are compiled C are installed
python3_sitelib /usr/lib/python3.X/site-packages Where pure python3 modules are installed
python3_sitearch /usr/lib64/python3.X/site-packages on x86_64
/usr/lib/python3.X/site-packages on x86
Where python3 extension modules that are compiled C are installed
py3dir %{_builddir}/python3-%{name}-%{version}-%{release} Directory to use when building python3 modules from the same source tarball as python2 modules
py_byte_compile (script) Defined in python3-devel. See the [#Bytecompiling_with_the_correct_python_version bytecompiling] section for usage

Additionaly, in Fedora 22 and greater, the following macros are defined:

Macro Normal Definition Notes
py2dir %{_builddir}/python2-%{name}-%{version}-%{release} Builddir for Python2 subpackage
%{__python} deprecated
The unversioned macros, %{__python}, %{python_sitelib}, and %{python_sitearch} are deprecated. You should use %{__python3}, %{python3_sitelib}, and %{python3_sitearch} to explicitly reference the python3 interpreter instead.

During %install or when listing %files you can use the python3_sitearch and python3_sitelib macros to specify where the installed modules are to be found. For instance:

# A pure python3 module
# A compiled python2 extension module
# A compiled python3 extension module

Using the macros has several benefits.

  1. It ensures that the packages are installed correctly on multilib architectures.
  2. Using these macros instead of hardcoding the directory in the specfile ensures your spec remains compatible with the installed python version even if the directory structure changes radically (for instance, if python2_sitelib moves into %{_datadir})

Files to include

When installing python modules we include several different types of files.

  • *.py source files because they are used when generating tracebacks
  • *.pyc and *.pyo byte compiled files
    • python will try to create them at runtime if they don't exist which leads to spurious SELinux AVC denials in the logs
    • If the system administrator invokes python with -OO, .pyos will be created with no docstrings. This can break some programs.
  • *.egg-info files or directories. If these are generated by the module's build scripts they must be included in the package because they might be needed by other applications and modules at runtime.

Source files

Source files (*.py) must be included in the same packages as the byte-compiled versions of them.

Byte compiling

Python will automatically try to byte compile files when it runs in order to speed up startup the next time it is run. These files are saved in files with the extension of .pyc (compiled python) or .pyo (optimized compiled python). These files are a byte code that is portable across OSes. If you do not include them in your packages, python will try to create them when the user runs the program. If the system administrator uses them, then the files will be successfully written. Later, when the package is removed, the .pyc and .pyo files will be left behind on the filesystem. To prevent that the byte compiled files need to be compiled and included in the %files section. Normally, byte compilation is done for you by the brp-python-bytecompile script. This script runs after the %install section of the spec file has been processed and byte compiles any .py files that it finds (this recompilation puts the proper filesystem paths into the modules otherwise tracebacks would include the %{buildroot} in them). All that you need to do is include the files in the %files section. The following are all acceptable ways to accomplish this:

install -d $RPM_BUILD_ROOT%{python3_sitelib}/foo
install -pm 0644 $RPM_BUILD_ROOT%{python3_sitelib}/foo/




%dir %{python3_sitelib}/foo

Or even:

%dir %{python3_sitelib}/foo
python's distutils has an INSTALLED_FILES feature that lists which files are installed when you run python install. Do not use it for packaging as that will not list the directories which need to be specified in the %files section as well. Using globs in the %files section is simpler and safer.
Including egg info
When you run %{__python3} install in any current Fedora, distutils generates a .egg-info file with metadata about the python module that is installed. These files need to be included as well. (See Packaging eggs and setuptools concerns )

Bytecompiling with the correct python version

When byte compiling a .py file, python embeds a magic number in the byte compiled files that correspond to the runtime. Files in %{python?_sitelib} and %{python?_sitearch} must correspond to the runtime for which they were built. For instance, a pure python module compiled for the 3.4 runtime needs to be below %{_usr}/lib/python3.4/site-packages

The brp-python-bytecompile script tries to figure this out for you. The script determines which interpreter to use when byte compiling the module by following these steps:

  1. what directory is the module installed in? If it's /usr/lib{,64}/pythonX.Y, then pythonX.Y is used to byte compile the module. If pythonX.Y is not installed, then an error is returned and the rpm build process will exit on an error so remember to BuildRequire the proper python package.
  2. the script interpreter defined in %{__python} is used to compile the modules. This defaults to the latest Python 3 version on Fedora. If you need to compile this module for Python 2, set it to /usr/bin/python2 instead:
    %global __python %{__python2}

    Doing this is useful when you have a Python 2 application that's installing a private module into its own directory. For instance, if the foobar application installs a module for use only by the command line application in %{_datadir}/foobar. Since these files are not in one of the Python 2 library paths (ie. /usr/lib/python2.7) you have to override %{__python} to tell brp-python-bytecompile to use the Python 2 interpreter for byte compiling.

These settings are enough to properly byte compile any package that builds python modules in %{python?_sitelib} or %{python?_sitearch} or builds for only a single python interpreter. However, if the application you're packaging needs to build with both Python 2 and Python 3 and install into a private module directory (perhaps because it provides one utility written in Python 2 and a second utility written in Python 3) then you need to do this manually. Here's a sample spec file snippet that shows what to do:

# Turn off the brp-python-bytecompile script
%global __os_install_post %(echo '%{__os_install_post}' | sed -e 's!/usr/lib[^[:space:]]*/brp-python-bytecompile[[:space:]].*$!!g')
# Buildrequire both Python 2 and Python 3
BuildRequires: python2-devel python3-devel

# Installs the Python 2 private module into %{buildroot}%{_datadir}/mypackage/foo
# and installs the Python 3 private module into %{buildroot}%{_datadir}/mypackage/bar
make install DESTDIR=%{buildroot}

# Manually invoke the python byte compile macro for each path that needs byte
# compilation.
%py_byte_compile %{__python2} %{buildroot}%{_datadir}/mypackage/foo
%py_byte_compile %{__python3} %{buildroot}%{_datadir}/mypackage/bar

The %py_byte_compile macro takes two arguments. The first is the Python interpreter to use for byte compiling. The second is a file or directory to byte compile. If the second argument is a directory, the macro will recursively byte compile any *.py file in the directory.

No %{} for py_byte_compile
RPM macros can only take arguments when they do not have curly braces around them. Therefore, py_byte_compile won't work correctly if you write: %{py_byte_compile} %{__python3}

Common SRPM vs split SRPMs

Many times when you package a Python module you will want to create a module for Python 2 and a module for Python 3. There are two ways of doing this: either from a single SRPM or from multiple. The rule to choose which method is simple: if the Python 2 and Python 3 modules are distributed as a single tarball (many times as a single directory of source where the /usr/bin/2to3 program is used to transform the code at buildtime) then you must package them as subpackages built from a single SRPM. If they come in multiple tarballs then package them from multiple SRPMs.

Python Bindings
python bindings are sometimes built as part of the C library's build. The ideal for these is to patch the code so it will build against both Python 2 and Python 3. Then take a copy of the sources during the %prep phase, and configure one subdirectory to build against Python 2, another to build against Python 3. These changes should be upstreamed. Example: the build of rpm itself emits an rpm-python subpackage (see Red Hat Bug 531543.)

Multiple SRPMS

When upstream ships multiple tarballs with one tarball containing Python 2 code and a different tarball containing Python 3 code, we should ship those as multiple SRPMs. The two SRPMs could have different maintainers within Fedora and the two packages need not upgrade at the same time. Building from multiple SRPMs has some advantages and disadvantages:


  • There can be separate maintainers for Python 2 and Python 3 so each maintainer can concentrate on one stack.
  • The two packages can evolve separately; if 2 and 3 need to have different versions, they can.


  • The two specfiles have to be maintained separately
  • When upstream releases e.g. security fixes, they have to be tracked in two places

The following practices are designed to help mitigate the disadvantages listed above:

  • When packaging a module for Python 3 contact the maintainers for the Python 2 module (or vice versa) and try to coordinate with them.
  • Request at least watchbugzilla and watchcommit acls on each other's packages so you're aware of outstanding bugs.
  • Complete any Python 2 Merge Review when doing the Python 3 version. Doing this gets issues that apply to both packages addressed at the same time.
  • Add a link to the Python 2 Merge Review/Package Review to the Python 3 Package Review


Do not build Python 3 modules without upstream support
If upstream is shipping a module for Python 2 and does not support making that module run on Python 3, do not package a Python 3 version of it in Fedora (or vice versa). If running 2to3 or adding a patch enables the code to work, you can certainly tell upstream that it works to encourage them to support Python 3. However, doing this on our own in Fedora is essentially creating a fork. That has a large burden for maintaining the code, fixing bugs, porting when a new version of upstream's code appears, managing a release schedule, and other tasks normally handled by upstream. It's much better if we can cooperate with upstream to share this work than doing it all on our own.

Sometimes upstream will ship one tarball that builds both a Python 2 and a Python 3 module. There's several ways that upstream can structure this. When upstream writes their build scripts to build both Python 2 and Python 3 modules in a single build this is just like building subpackages for any other package. You expand the tarball and patch the source in %prep, run upstream's build scripts to build the package in %build, and then run upstream's build scripts to install it in %install.


  • Single source rpm to review and build
  • Avoids having to update multiple packages when things change.


  • The Fedora maintainer needs to care about both Python 2 and Python 3 modules which makes more work to maintain that package.
  • The 2 and 3 versions are in lockstep. Bugfixes need to apply to Python 2 while not breaking the translation into Python 3 and vice versa.
  • Bugzilla components are set up according to source RPM, so they will have a single shared bugzilla component. This could be confusing to end-users, as it would be more difficult to figure out e.g. that a bug with python3-foo needs to be filed against python-foo. There's a similar problem with checking out package sources from CVS, though this is less serious as it is less visible to end users.

Two other ways exist for the upstream to support building Python 3 modules from a single source:

Building more than once

One way that's currently very common is for the build scripts to create either a Python 2 or Python 3 module based on which interpreter is used to run the script. (The python-setuptools package is currently built this way).

Example Specfile

Example of what a specfile would look like follows. Everything works in the same way as it does now with building python3-* subpackages; the same approach is applied to python2-* subpackages.

Existing Python 2 packages Provides and Obsoletes
Every existing Python 2 package must have virtual provides for its previous name (and proper Obsoletes). For most packages, this will be Provides: python2-foo, but some packages haven't had the python prefix historically (PyYAML), so these will just have Provides: foo.

This specfile will produce two binary RPMs, python2-six and python3-six. The Python 2 subpackage can be disabled by setting with_python2 to 0:

%global with_python2 1

# this macro is defined here only for testing purposes, it would
# be defined in macros.python2 provided by python2-devel
%global py2dir %{_builddir}/python2-%{name}-%{version}-%{release}

Name:           python-six
Version:        1.4.1
Release:        1%{?dist}
Summary:        Python 2 and 3 compatibility utilities

Group:          Development/Languages
License:        MIT

BuildArch:      noarch
%if 0%{?with_python2}
BuildRequires:  python2-devel
# For use by selftests:
BuildRequires:  python2-pytest
BuildRequires:  python2-tkinter

BuildRequires:  python3-devel
# For use by selftests:
BuildRequires:  python3-pytest
BuildRequires:  python3-tkinter

Provide descriptions for both packages (and for the main package, since rpmbuild enforces that).

python-six provides simple utilities for wrapping over differences between
Python 2 and Python 3.

%if 0%{?with_python2}
%package -n python2-six
Summary:        Python 2 and 3 compatibility utilities
Group:          Development/Languages
Provides:       python-six = %{version}-%{release}
Obsoletes:      python-six < 1.4.1-1

%description -n python2-six
python-six provides simple utilities for wrapping over differences between
Python 2 and Python 3.

%package -n python3-six
Summary:        Python 2 and 3 compatibility utilities
Group:          Development/Languages

%description -n python3-six
python-six provides simple utilities for wrapping over differences between
Python 2 and Python 3.

This is the Python 3 build of the module.

%prep, %build, %install and %check sections look pretty much the same, each has to explictly switch the directory to the respective py{2,3}dir. I believe we could come up with some macros that would make this easier and more readable (TODO).

%setup -q -n six-%{version}
# possibly apply patches here

%if 0%{?with_python2}
rm -rf %{py2dir}
cp -a . %{py2dir}

rm -rf %{py3dir}
cp -a . %{py3dir}

%if 0%{?with_python2}
pushd %{py2dir}
%{__python2} build

pushd %{py3dir}
%{__python3} build

pushd %{py3dir}
%{__python3} install -O1 --skip-build --root $RPM_BUILD_ROOT

%if 0%{?with_python2}
pushd %{py2dir}
%{__python2} install -O1 --skip-build --root $RPM_BUILD_ROOT

There is no default %files section, only %files sections for python{2,3}-six packages.

%if 0%{?with_python2}
%files -n python2-six
%doc LICENSE README documentation/index.rst

%files -n python3-six
%doc LICENSE README documentation/index.rst
Example spec file
%if 0%{?fedora} > 12
%global with_python3 1
%{!?__python2: %global __python2 /usr/bin/python2}
%{!?python2_sitelib: %global python2_sitelib %(%{__python2} -c "from distutils.sysconfig import get_python_lib; print (get_python_lib())")}

%global srcname distribute

At the top of our spec file we have the standard define for python2_sitelib on older RHEL releases. We also define with_python3 which we'll use to conditionalize the build whenever we have a section that is only useful when building a python3 module. Using with_python3 allows us to do two things:

  1. It makes it easy to turn off the python3 build when tracking down problems.
  2. The conditionals also make it easy to use the same spec for older releases of Fedora and EPEL.
  3. .
Leave python3 module enabled in releases
Once python 3 support has been added to a package, you must leave it enabled. End users could be using the python3 subpackage that is being built. If you turn the subpackage build on and off it will cause the package to unexpectedly disappear from the repos. You should only turn off with_python3 as a debugging measure within scratch builds, for releases that do not support python 3, or when moving a python3 module into its own, independent package.
Name:           python-setuptools
Version:        0.6.10
Release:        2%{?dist}
Summary:        Easily build and distribute Python packages

Group:          Applications/System
License:        Python or ZPLv2.0
URL:  {srcname}
# Fix a failing test case
Patch0:         python-setuptools-test.patch
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildArch:      noarch
BuildRequires:  python2-devel
%if 0%{?with_python3}
BuildRequires:  python3-devel
%endif # if with_python3

When we build the python3 module in addition to the python3 module we need both python2-devel and python3-devel.

Setuptools is a collection of enhancements to the Python distutils that allow
you to more easily build and distribute Python packages, especially ones that
have dependencies on other packages.

This package contains the runtime components of setuptools, necessary to
execute the software that requires

%if 0%{?with_python3}
%package -n python3-setuptools
Summary:        Easily build and distribute Python 3 packages
Group:          Applications/System

%description -n python3-setuptools
Setuptools is a collection of enhancements to the Python 3 distutils that allow
you to more easily build and distribute Python 3 packages, especially ones that
have dependencies on other packages.

This package contains the runtime components of setuptools, necessary to
execute the software that requires
%endif # with_python3

Here we define the python3 subpackage. Note that we use %package -n to name the module appropriately.

%setup -q -n %{srcname}-%{version}

%patch0 -p1 -b .testfix

find -name '*.txt' | xargs chmod -x

%if 0%{?with_python3}
rm -rf %{py3dir}
cp -a . %{py3dir}
find %{py3dir} -name '*.py' | xargs sed -i '1s|^#!python|#!%{__python3}|'
%endif # with_python3

find -name '*.py' | xargs sed -i '1s|^#!python|#!%{__python2}|'

Our method in building from the same code to make the two separate modules is to keep each build as independent as possible. To do that, we copy the source tree to %{py3dir} so that the python 2 sources are entirely independent from the python 3 sources. Some things to watch out for:

  • Be sure to clean up the %{py3dir} before performing the copy. It's easy to forget that since %setup does that automatically for the python2 module.
  • Make sure that you are copying the correct code. The example is copying the code from within the top directory of the untarred source. If the %prep has changed directory you will need to change back to the tarball location.
  • Patching the source code is done before copying to %{py3dir}. Since you have both a python2 and a python3 directory you might be tempted to patch each one separately. Resist! Upstream for your package has chosen to distribute a single source tree that builds for both python2 and python3. For your patches to get into upstream, you need to write patches that work with both as well.}}

rpmbuild resets the directory at the end of each phase, so you don't need to restore the directory at the end of %prep.

CFLAGS="$RPM_OPT_FLAGS" %{__python2} build

%if 0%{?with_python3}
pushd %{py3dir}
CFLAGS="$RPM_OPT_FLAGS" %{__python3} build
%endif # with_python3

rm -rf %{buildroot}

# Must do the python3 install first because the scripts in /usr/bin are
# overwritten with every install (and we want the python2 version
# to be the default for now).
%if 0%{?with_python3}
pushd %{py3dir}
%{__python3} install --skip-build --root $RPM_BUILD_ROOT

rm -rf %{buildroot}%{python3_sitelib}/setuptools/tests

find %{buildroot}%{python3_sitelib} -name '*.exe' | xargs rm -f
chmod +x %{buildroot}%{python3_sitelib}/setuptools/command/
%endif # with_python3

%{__python2} install --skip-build --root $RPM_BUILD_ROOT

rm -rf ${buildroot}%{python2_sitelib}/setuptools/tests

find %{buildroot}%{python2_sitelib} -name '*.exe' | xargs rm -f
chmod +x %{buildroot}%{python2_sitelib}/setuptools/command/

%{__python2} test

%if 0%{?with_python3}
pushd %{py3dir}
%{__python3} test
%endif # with_python3

You'll notice that the %build, %install, and %check sections follow a common pattern. They do the normal steps for building the python2 module but then they switch to %{py3dir} and run the same steps for python3. Creating the new sections is generally pretty easy. First copy the existing code. Then wrap it with a pushd/popd to %{py3dir}. The usage of pushd/popd commands will ensure that the directories are logged. Finally, convert all macro references:

  • %{__python2} becomes %{__python3}
  • %{python2_sitelib} becomes %{python3_sitelib}
  • %{python2_sitearch} becomes %{python3_sitearch}
Order can be important
As you can see in the %install section, the order in which you do the python2 versus python3 install can sometimes matter. You need to be aware of when the install is writing to the same file in both packages (in this example, a script in %{_bindir} and make sure that you're getting the version you expect.

%doc psfl.txt zpl.txt docs

%if 0%{?with_python3}
%files -n python3-setuptools
%doc psfl.txt zpl.txt docs
%endif # with_python3


In this final section, you can see that we once again switch macros from %{python2_sitelib} to %{python3_sitelib}. Since we chose to install the python2 version of %{_bindir}/easy_install earlier we need to include that file in the python2 package rather than the python3 subpackage.

Running 2to3 from the spec file

Sometimes, upstream hasn't integrated running 2to3 on the code into their build scripts but they support making a python3 module from it if you manually run 2to3 on the source. This is the case when it's documented on the upstream's website, in a file in the tarball, or even when email with the module's author has instructions for building a python3 module from the python2 source and the authors are willing to support the result. In these cases it's usually just a matter of the upstream not having written the build script that can turn the python2 source into python3. When this happens you can run 2to3 from the spec file. Once you have it working, you can also help upstream integrate it into their build scripts which will benefit everyone in the long term.

You should usually follow upstream's directions on how to run 2to3 and build the python3 module in these cases but there's a few things you should check to make sure upstream is doing it correctly.

  • Since the code is being built from a unified source, you need to copy the code to a new directory before invoking 2to3 just like the building more than once method.
  • If the 2to3 program is invoked instead of using the lib2to3 library functions, make sure it's invoked with --write --nobackups. --write is needed to make 2to3 actually change the files. --nobackups avoids leaving files in the module directories that then make it into the final package payload.
  • Be sure to run 2to3 on the correct directory. When you run 2to3 you need to run it on the whole tree. A common mistake here for distutils packages has been to run it on the directory below, missing the file itself. This leads to errors when python3 tries to execute
  • If you need to run 2to3 to fix code, use 2to3 or /usr/bin/2to3. At the moment, this program is coming from the python-tools rpm. Using 2to3 means that you'll be using a name that is supported upstream and across distros rather than /usr/bin/python3-2to3 which we have renamed in Fedora to avoid filesystem conflicts. This also makes it easier for us to test and eventually change from using the python2 2to3 to the python3 2to3. We just need to change the python3 package to provide the /usr/bin/2to3 program instead of python and all of our python packages will start using that version instead.
  • If 2to3 runs into a problem, please file a Fedora bug. Please try to isolate a minimal test case that reproduces the problem when doing so.

Avoiding collisions between the Python 2 and Python 3 stacks

The Python 2 and Python 3 stacks are intended to be fully-installable in parallel. When generalizing the package for both Python 2 and Python 3, it is important to ensure that two different built packages do not attempt to place different payloads into the same path.

Executables in /usr/bin

The problem

Many existing Python packages install executables into /usr/bin.

For example if we have a console_scripts in a shared between Python 2 and Python 3 builds: these will spit out files in /usr/bin/, and these will collide.

For example python-coverage has a that contains:

    entry_points = {
        'console_scripts': [
            'coverage = coverage:main',

which thus generates a /usr/bin/coverage executable (this is a Python script that runs another Python script whilst generating code-coverage information on the latter).

Similarly for the 'scripts' clause; see e.g. python-pygments: Pygments-1.1.1/ has:

    scripts = ['pygmentize'],

which generates a /usr/bin/pygmentize (this is a Python script that leverages the pygments syntax-highlighting module, giving a simple command-line interface for generating syntax-highlighted files)


If the executables provide the same functionality independent of whether they are run on top of Python 2 or Python 3, then only the Python 3 version of the executable should be packaged.

Examples of this:

  • /usr/bin/pygmentize ought to generate the same output regardless of whether it's implemented via Python 2 or Python 3, so only one version needs to be shipped.

If the executables provide different functionality for Python 2 and Python 3, then both versions should be packaged.

Examples of this:

  • /usr/bin/coverage runs a python script, augmenting the interpreter with code-coverage information. Given that the interpreter itself is the thing being worked with, it's reasonable to package both versions of the executable.
  • /usr/bin/bpython augments the interpreter with a "curses" interface. Again, it's reasonable to package both versions of this.
  • /usr/bin/easy_install installs a module into one of the Python runtimes: we need a version for each runtime.

As an exception, for the rpms that are part of a python runtime itself, we plan to package both versions of the executables, so that e.g. both the python 2 and python 3 versions of 2to3 are packaged.


Many executables already contain a "-MAJOR.MINOR" suffix, for example /usr/bin/easy_install-3.4. These obviously can be used as-is, as they won't conflict.

For other executables, the general rule is:

  • if only one executable is to be shipped, then it owns its own slot
  • if executables are to be shipped for both Python 2 and Python 3, then the Python 2 version of the executable gains a Python2.7- prefix. For example, the python 3 version of "coverage" remains /usr/bin/coverage and the Python 2 version is /usr/bin/python2.7-coverage.

Packaging eggs and setuptools concerns

Eggs can mean several different things because they can be placed on disk in several formats:

  • A module and a file with a .egg-info extension that contains the metadata. Created by distutils in Fedora 9 and above.
  • As a module and a directory with a .egg-info extension that contains the metadata. Created using setuptools and also the invocation of in our examples below.
  • As a directory with a .egg extension that contains the module and egg metadata. Created when we use easy_install -m to allow installing multiple versions of a module.
  • As a single zip file with a .egg extension that contains the module and the egg metadata.

In Fedora packages, these will be installed to %{python2_sitelib} or %{python2_sitearch} directories. We do not install the single zip file version of eggs in Fedora but the three other formats are used.

How to package

The following are a summary of the guidelines for reviewers to go over when a python module is packaged. The complete policy includes examples and rationale for the way we do things.

  • Must: Python eggs must be built from source. They cannot simply drop an egg from upstream into the proper directory. (See prebuilt binaries Guidelines for details)
  • Must: Python eggs must not download any dependencies during the build process.
  • Must: When building a compat package, it must install using easy_install -m so it won't conflict with the main package.
  • Must: When building multiple versions (for a compat package) one of the packages must contain a default version that is usable via "import MODULE" with no prior setup.
  • Should: A package which is used by another package via an egg interface should provide egg info.

Filtering Requires: and Provides:

RPM's dependency generator can often throw in additional dependencies and will often think packages provide functionality contrary to reality. To fix this, the dependency generator needs to be overriden so that the additional dependencies can be filtered out. See Packaging:AutoProvidesAndRequiresFiltering for details.

PyGTK2 and Numpy

This workaround is necessary until [Gnome bug #591745] is fixed.

If your package uses pygtk2, and calls the gtk.gdk.get_pixels_array() function, that package needs to explicitly Require: numpy. In the past, pygtk2 had a Requires on numpy, but since it is only used for that one function (and that function is not commonly used), the Requires has been removed to minimize the install footprint of pygtk2.