Platform Python Stack
This change was reverted, because it was a bad idea entirely. See RHBZ#1483342 and the link below this box.
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
Owner
- Name: Miro Hrončok
- Name: Charalampos Stratakis
- Name: Tomáš Orsava
- Email: <python-maint at redhat.com>
- Release notes owner:
Current status
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
- the location of files will not be
/usr/lib/python3.6/but/usr/lib/platform-python3.6/- the script that generates the
python(abi)requirement will be adapted to generateplatform-python(abi)requirement for that location
- the script that generates the
- 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-libsbut ratherpython3-libswill relocate toplatform-python-libs-develto be available only on build-time platform-pythonwill provideplatform-python(abi)instead ofpython(abi)
Several packages (see bellow) will introduce a new platform-python- subpackage. Example specfile of such package:
%global pypi_name foo
%bcond_without python2
%bcond_without python3
%bcond_without platform_python
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
%if %{with python2}
BuildRequires: python2-devel
BuildRequires: python2-setuptools
%endif
%if %{with python3}
BuildRequires: python3-devel
BuildRequires: python3-setuptools
%endif
%if %{with platform_python}
BuildRequires: platform-python-devel
BuildRequires: platform-python-setuptools
%endif
BuildArch: noarch
%description
...
%if %{with python2}
%package -n python2-%{pypi_name}
Summary: %{summary}
Requires: python2-bar
%{?python_provide:%python_provide python2-%{pypi_name}}
%description -n python2-%{pypi_name}
...
%endif
%if %{with python3}
%package -n python3-%{pypi_name}
Summary: %{summary}
Requires: python3-bar
%{?python_provide:%python_provide python3-%{pypi_name}}
%description -n python3-%{pypi_name}
...
%endif
%if %{with platform_python}
%package -n platform-python-%{pypi_name}
Summary: %{summary}
Requires: platform-python-bar
%description -n platform-python-%{pypi_name}
...
%endif
%prep
%autosetup -n %{pypi_name}-%{version}
%build
%if %{with python2}
%py2_build
%endif
%if %{with python3}
%py3_build
%endif
%if %{with platform_python}
%platform_py_build
%endif
%install
%if %{with python2}
%py2_install
rm %{buildroot}%{_bindir}/%{pypi_name}
%endif
%if %{with platform_python}
%platform_py_install
rm %{buildroot}%{_bindir}/%{pypi_name}
%endif
%if %{with python3}
%py3_install
%endif
%check
%if %{with python2}
export PYTHONPATH=%{buildroot}%{python2_sitelib}
%{__python2} -m unittest discover -v
%endif
%if %{with python3}
export PYTHONPATH=%{buildroot}%{python3_sitelib}
%{__python3} -m unittest discover -v
%endif
%if %{with platform_python}
export PYTHONPATH=%{buildroot}%{platform_python_sitelib}
%{__platform_python} -m unittest discover -v
%endif
%if %{with python2}
%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
%endif
%if %{with python3}
%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
%endif
%if %{with platform_python}
%files -n platform-python-%{pypi_name}
%doc README.rst CHANGES.rst
%license COPYING
%{platform_python_sitelib}/%{pypi_name}.cpython-%{platform_python_version_nodots}*.so
%{platform_python_sitelib}/%{pypi_name}-%{version}-py?.?.egg-info
%endif
%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:
dnf gpgme libcomps libdnf librepo pytest python-coverage python-hypothesis python-iniparse python-nose python-py python-rpm-generators python-rpm-macros python-setuptools python-setuptools_scm python-six 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-iniparse platform-python-gpg platform-python-rpm platform-python-dnf platform-python-libs platform-python-six platform-python-libcomps platform-python-librepo platform-python-hawkey
(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 (and potentially other system management utilities later on) 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.
Splitting the full Python stack away from Platform allows for flexible and fast paced, upstream-driven delivery, independent of the main Fedora release cycle. See Modularity for more information about this concept in general and the Host and Platform change proposal to learn more about the abovementioned Platform module.
Scope
- Proposal owners:
- A Roadmap has been created
- identify a list of runtime and build dependencies of dnf
- create a
platform-pythonsource package - change the script that generates the
python(abi)requirements to also generateplatform-python(abi)requirements - revert system-python related things from the
python3 - 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: #6917 (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
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)