From Fedora Project Wiki

< Changes

Revision as of 07:41, 24 June 2019 by Lbalhar (talk | contribs) (First draft of a new change proposal)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Unification of placement of Python test modules


Python itself comes with a lot of test modules. Some of them are widely used and some of them are not. Because the usage of test modules outside Python itself is not supported, It would be better to have all of them in the one subpackage python3-test to identify which parts are actually useful outside Python itself and then we can propose a move of those parts somewhere else to the standard library. This approach is related to PEP 594, which is aimed to remove old and unused modules from the standard library.


Current status

Detailed Description

Python test modules should be used only for testing Python itself. However, some packages have buildtime or runtime dependency on parts of Python test modules and moreover those modules are placed in various Python subpackages (python3-libs, python3-idle, python3-test). This situation makes it hard finding out which test modules are actually useful and it'd make sense to make them a regular part of the standard library. This might also help to distinguish which parts are useless and can be removed during the clean up described in PEP 594.

Benefit to Fedora

All Python test modules will be contained in one subpackage which helps us understand which parts of Python test suite are useful and which is worth to move to the standard library.


  • Proposal owners:
    • Move all test modules from other Python subpackages to the -test subpackage
    • Identify as many as possible affected packages and try to fix their buildtime/runtime issues caused by the change
  • Other developers:
    • If a package depends on some module which we move to -test subpackage, change the build/runtime dependencies definition accordingly
  • Release engineering: 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

Test modules should not be used as a runtime dependency so there is no impact on an upgrade.

How To Test

N/A (not a System Wide Change)

User Experience

The user experience should not be affected.


N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: Changes will be mostly done in Python specfile and they can be easily reverted in case of some unexpected issues. The second possibility is to set Provides to temporarily deactivate the impact of the change.
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change)
  • Blocks product? No.


N/A (not a System Wide Change)

Release Notes

Since this affects only a few packages, no release notes are necessary.