English Italian
Python
Python 2 is deprecated in Fedora 30
Many Python 2 modules were removed from the distribution: packages that only provide Python 2 importable modules, if they are not used by any other package (leaf packages).
While this change should not affect regular users, it will affect developers that use system-packaged Python modules.
If you are developing software that needs to run with Python 2, we recommend using a virtual environment and installing dependencies from the Python Package index (`PyPI`). See details at: https://developer.fedoraproject.org/tech/languages/python/python-installation.html
We also recommend using a virtual environment (`venv`) for Python 3, if your software targets the wider Python ecosystem rather than Fedora specifically. Using `venv` will decouple your development environment from the system.
If you are developing for a Fedora package, please port to Python 3 as soon as possible. Almost complete Python 2 removal is planned for the next release.
Automatically generated dependencies for Python packages
The generator which generates Provides and Requires for Python RPM packages based on the `setup.py` file has been enabled by default. This makes the packaging of Python packages easier and more automatic by reusing information provided by the upstream project, and should result in fewer unecessary or missing dependencies in RPMs.
Python progressbar replaced with progressbar2
The `progressbar` package has been updated to use the `progressbar2` fork, which is newer and better maitained.
Nautilus extensions now use Python 3
As part of the general move to Python 3, extensions for the file browser and graphical shell Nautilus are now executed using Python 3, and extensions compatible only with Python 2 are no longer supported. Extensions packaged in the distribution have been updated for Python 3 compatiblity. Users who have installed their own extensions should check that they are compatible with Python 3 or remove them.
Avoid Fedora-specific build flags in non-RPM Python extensions
When extension modules are built, the `distutils` module provides a set of compilation and link flags to ensure that modules are compiled in a way which is compatible with Python executable itself. When building modules in Fedora, the same set of flags was used for modules which are part of the distribution (i.e. part of an RPM package) and for modules compiled by users *using* Fedora. Those flags included custom GCC plugins and additional linker options to "harden" the code and add `annobin` annotations, which is appropriate for the distribution, but unexpected and unnecessary for user code. A distinct and smaller set of flags is now provided for extension modules compiled by users.
The build flags (`CFLAGS`, `CXXFLAGS` and `LDFLAGS`) saved in the Python's `distutils` module for building extension modules are switched from:
`%\{build_cflags}`,
`%\{build_cxxflags}` and
`%\{build_ldflags}`
to