Changes/Platform Python Stack

Platform Python Stack

Summary

A revisit of the System Python change from Fedora 24. It has been renamed from System Python to Platform Python not to collide with upstream PEP 432.

Platform Python will be a separate stack fo Python packages aimed to provide all necessary dependencies to run and build dnf. In Fedora 27 this will be Python 3.6 (same version as python3, but this might change in the future with the Modularity effort).

Owner

• Name: Miro Hrončok
• Email: <python-maint at redhat.com>
• Release notes owner:

Current status

• Targeted release: Fedora 27
• Last updated: 2017-07-20
• Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The changes made during the System Python change from Fedora 24 will be reverted.

A new platform-python (source) package will be created as a copy of the python3 package. Unlike python3, it will be changed so that:

• the location of files will not be /usr/lib/python3.6/ but /usr/lib/platform-python/
  • the script that generates the python(abi) requirement will be adapted to generate platform-python(abi) requirement for that location
• the location of the binary will be /usr/libexec/platform-python
• all the macros will use the platform python binary and will be renamed
• all subpackages will be named platform-python-*
• the debug build will be disabled
• the modules that are (before this change) not part of system-python-libs but rather python3-libs will relocate to platform-python-libs-devel to be available only on build-time
• platform-python-libs will provide platform-python(abi) instead of python(abi)

Several packages (see bellow) will introduce a new platform-python- subpackage. Example specfile of such package:

%global pypi_name foo

Name:           python-%{pypi_name}
Version:        0.13
Release:        1%{?dist}
Summary:        Python %{pypi_name} module

License:        GPLv2
URL:            https://github.com/fedora-python/%{pypi_name}
Source0:        https://files.pythonhosted.org/packages/source/f/%{pypi_name}/%{pypi_name}-%{version}.tar.gz

BuildRequires:  python2-devel
BuildRequires:  python2-setuptools

BuildRequires:  python3-devel
BuildRequires:  python3-setuptools

BuildRequires:  platform-python-devel
BuildRequires:  platform-python-setuptools

BuildArch:      noarch

%description
...

%package -n     python2-%{pypi_name}
Summary:        %{summary}
Requires:       python2-bar
%{?python_provide:%python_provide python2-%{pypi_name}}

%description -n python2-%{pypi_name}
...

%package -n     python3-%{pypi_name}
Summary:        %{summary}
Requires:       python3-bar
%{?python_provide:%python_provide python3-%{pypi_name}}

%description -n python3-%{pypi_name}
...


%package -n     platform-python-%{pypi_name}
Summary:        %{summary}
Requires:       platform-python-bar

%description -n platform-python-%{pypi_name}
...


%prep
%autosetup -n %{pypi_name}-%{version}


%build
%py2_build
%py3_build
%plpy_build

%install
%py2_install
rm %{buildroot}%{_bindir}/%{pypi_name}

%plpy_install
rm %{buildroot}%{_bindir}/%{pypi_name}

%py3_install


%check
export PYTHONPATH=%{buildroot}%{python2_sitelib}
%{__python2} -m unittest discover -v

export PYTHONPATH=%{buildroot}%{python3_sitelib}
%{__python3} -m unittest discover -v

export PYTHONPATH=%{buildroot}%{platformpython_sitelib}
%{__platformpython} -m unittest discover -v


%files -n python2-%{pypi_name}
%doc README.rst CHANGES.rst
%license COPYING
%{python2_sitelib}/%{pypi_name}.so
%{python2_sitelib}/%{pypi_name}-%{version}-py?.?.egg-info

%files -n python3-%{pypi_name}
%doc README.rst CHANGES.rst
%license COPYING
%{_bindir}/%{pypi_name}
%{python3_sitelib}/%{pypi_name}.cpython-%{python3_version_nodots}*.so
%{python3_sitelib}/%{pypi_name}-%{version}-py?.?.egg-info

%files -n platform-python-%{pypi_name}
%doc README.rst CHANGES.rst
%license COPYING
%{platformpython_sitelib}/%{pypi_name}.cpython-%{platformplatformpython_version_nodots}*.so
%{platformpython_sitelib}/%{pypi_name}-%{version}-py?.?.egg-info

%changelog
...

The complete list of affected packages is not final yet. It should be all the Python build dependencies of dnf and their build dependencies as well, excluding packages only needed to build the documentation (normal python3- (or even python2-) packages will be used to build the documentation as it is now).

Currently, we have established this as a list of packages:

dbus-python
gpgme
libcomps
libdnf
librepo
pytest
python-argcomplete
python-cffi
python-contextlib2
python-coverage
python-cryptography
python-decorator
python-extras
python-fixtures
python-funcsigs
python-hypothesis
python-idna
python-iniparse
python-jinja2
python-jsonschema
python-keyring
python-linecache2
python-markupsafe
python-mimeparse
python-mock
python-nose
python-pbr
python-pexpect
python-pip
python-ply
python-ptyprocess
python-py
python-pyasn1
python-pycparser
python-pygpgme
python-pytest-timeout
python-rpm-macros
python-SecretStorage
python-setuptools
python-setuptools_scm
python-six
python-testtools
python-traceback2
python-unittest2
python-wheel
pyxattr
pyxdg
rpm

Only the following list will be installable from the platform module (the rest is merely meant as a build dependency):

platform-python
platform-python-dnf
platform-python-gpg
platform-python-hawkey
platform-python-iniparse
platform-python-libcomps
platform-python-librepo
platform-python-libs
platform-python-pyparsing
platform-python-rpm
platform-python-six

(And other subpackages from their source RPMs needed as dependencies for those, such as gpgme etc.)

Benefit to Fedora

With the Modularity effort a minimal stack of Python only needed to run dnf is needed to be part of the Platform. Changing System/Platform Python to be a separate stack will allow us to do that. In the future that allows us to have different version of Python in platform and in the "Python 3" module.

TODO: The Modularity team to extend this section.

Scope

• Proposal owners:
  • identify a list of runtime and build dependencies of dnf
  • create a platform-python source package
  • change the script that generates the python(abi) requirements to also generate platform-python(abi) requirements
  • revert system-python related things from the python3 package (add appropriate provides/obsoletes)
  • add a platform-python- subpackage to identified list of packages
  • switch dnf to use that stack

• Other developers: N/A (not a System Wide Change)

• Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
  • List of deliverables: N/A (not a System Wide Change)

• Policies and guidelines: N/A (not a System Wide Change)

• Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

Nothing should change for the user, except a slightly larger amount of packages will be installed on the system.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? No (not a System Wide Change)
• Blocks product? No

If not done on time: Keep dnf running on python3. Finish the work in time of Fedora 28.

If proven not to work as designed: Retire platform-python package and remove all the platform-python- subpackages. Provide/obsolete platform-python- subpackages from their python3- counterparts.

Documentation

N/A (not a System Wide Change)