From Fedora Project Wiki
m (Submitted to FESCo)
m (Add trackers)
 
(3 intermediate revisions by 2 users not shown)
Line 20: Line 20:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1661309 #1661309]
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/268 #268]


== Detailed Description ==
== Detailed Description ==
Line 54: Line 55:


== How To Test ==
== How To Test ==
TBD
# Make sure that python-rpm-generators >= 7-1.fc30 is installed
<!--
# Make sure that python-rpm-macros >= 3-25 is installed
# Remove all requires for python modules
# Remove all requires for python modules
# Rebuild package
# Rebuild package


Every dependency mentioned in egg/wheel (e.g. generated by setuptools/distutils from setup.py) should be automatically added.
Every dependency mentioned in egg/wheel (e.g. generated by setuptools/distutils from setup.py) should be automatically added.
-->
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  


Line 104: Line 102:
-->
-->


[[Category:ChangeReadyForFesco]]
[[Category:ChangeAcceptedF30]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 19:15, 20 December 2018

Enabling Python Generators by default

Summary

This change enables the Python module dependency generator for packages that provide Python Egg/Wheel metadata by default (this was opt-in since Fedora 28).

Owner

Current status

Detailed Description

Please see detailed description from original change for information how it works and implemented.

In this change we will switch opt-in into opt-out.

Benefit to Fedora

All the benefits as stated in original change will be turned on for all packages (unless they opt-out).

Scope

  • Proposal owners: Flip the switch (in python-rpm-generators) and adjust python-rpm-macros to make feature be opt-out. Send patches to packages to remove unnecessary manual-specified dependencies.
  • Other developers: Packagers are strongly advised to remove manually-specified python dependencies if they are set in egg/wheel metadata.
  • Release engineering: #7965 (change should be implemented before mass rebuild)
  • Policies and guidelines: Python Guidelines needs to be updated with the now default. Instructions how to disable the feature are already there.
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

Some new dependencies might be automatically added, but this is rather good because it fixes real bugs.

How To Test

  1. Make sure that python-rpm-generators >= 7-1.fc30 is installed
  2. Remove all requires for python modules
  3. Rebuild package

Every dependency mentioned in egg/wheel (e.g. generated by setuptools/distutils from setup.py) should be automatically added.

User Experience

Users will see less number of packages with missing dependency information.

Dependencies

None.

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) Owners will revert change and postpone it to next release.
  • Contingency deadline: Beta freeze.
  • Blocks release? No.
  • Blocks product? product

Documentation

Packaging guidelines already contain information how this feature work.

Release Notes