From Fedora Project Wiki
(A new version of proposal for one Python module only)
Line 1: Line 1:
= Unification of placement of Python test modules =
+
= Move <code>test.support</code> module to <code>python3-test</code> subpackage =
  
 
== Summary ==
 
== Summary ==
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 <code>python3-test</code> 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 [https://www.python.org/dev/peps/pep-0594/ PEP 594], which is aimed to remove old and unused modules from the standard library.  
+
 
 +
Move <code>test.support</code> from <code>python3-libs</code> to <code>python3-test</code> subpackage.
  
 
== Owner ==
 
== Owner ==
Line 27: Line 28:
 
== Detailed Description ==
 
== 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 (<code>python3-libs</code>, <code>python3-idle</code>, <code>python3-test</code>). 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 [https://www.python.org/dev/peps/pep-0594/ PEP 594].
+
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. The aim of this change is to move the most popular Python test module <code>test.support</code> from <code>python3-libs</code> to <code>python3-test</code> subpackage which will help us discover packages which depend on it and also identify parts of the module which might be useful to move to standard library.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 35: Line 36:
 
== Scope ==
 
== Scope ==
 
* Proposal owners:
 
* Proposal owners:
** Move all test modules from other Python subpackages to the -test subpackage
+
** Move <code>test.support</code> from <code>python3-libs</code> to <code>python3-test</code> subpackage.
** Identify as many as possible affected packages and try to fix their buildtime/runtime issues caused by the change
+
** Identify as many as possible affected packages and try to fix their buildtime/runtime issues caused by the change.
  
 
* Other developers:  
 
* Other developers:  
** If a package depends on some module which we move to -test subpackage, change the build/runtime dependencies definition accordingly
+
** If a package depends on <code>test.support</code> module which we move to -test subpackage, change the build/runtime dependencies definition accordingly.
  
 
* Release engineering: N/A (not a System Wide Change)
 
* Release engineering: N/A (not a System Wide Change)

Revision as of 09:29, 24 June 2019

Move test.support module to python3-test subpackage

Summary

Move test.support from python3-libs to python3-test subpackage.

Owner

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. The aim of this change is to move the most popular Python test module test.support from python3-libs to python3-test subpackage which will help us discover packages which depend on it and also identify parts of the module which might be useful to move to standard library.

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.

Scope

  • Proposal owners:
    • Move test.support from python3-libs to python3-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 test.support 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.

Dependencies

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.

Documentation

N/A (not a System Wide Change)

Release Notes

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