(→Scope) |
|||
| Line 89: | Line 89: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
*# Test affected packages in Copr. | *# Test affected packages in Copr. | ||
*# Do mass | *# Do the mass spec update to introduce missing BuildRequire to them. | ||
* Other developers: There should be no additional work for other developers. BuildRequiring setuptools might not be enough for all packages, but we will take care of them manually if it happens. | * Other developers: There should be no additional work for other developers. BuildRequiring setuptools might not be enough for all packages, but we will take care of them manually if it happens. | ||
Revision as of 09:24, 11 March 2021
python3.10 won't pull in setuptools by default in rpmbuild
Summary
python3.10 currently requires python-setuptools if rpmbuild is used. Due to a change in RPM generators, this is not needed anymore hence we are removing it.
Owner
- Name: Tomáš Hrnčiar
- Name: Miro Hrončok
- Email: python-maint@redhat.com
Current status
- Targeted release: Fedora Linux 35
- Last updated: 2021-03-11
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
python3.10 currently requires python-setuptools if rpmbuild is used. This was needed for RPM generators but since it adapted pyparsing, this is not needed anymore hence we are removing it. We tested this change in python3.10 COPR and it showed us 140 packages affected by this change. To avoid any breakages we plan to do a mass spec update to explicitly BuildRequire python-setuptools.
Feedback
Benefit to Fedora
From Fedora Packaging Guidelines: It is important that your package list all necessary build dependencies using the BuildRequires: tag. As our testing showed, this is not true for many packages. Some of them can successfully build either with or without setuptools (they use try-except import and fallback to distutils from the standard library). Such packages are especially dangerous when not BuildRequiring setuptools -- they can produce different results depending on the presence of setuptools: either an .egg-info metadata directory (w/setuptools) or .egg-info text file (w/distutils). RPM has troubles when upgrading directories to files.
Scope
We will coordinate the work in a side tag and merge when ready.
- Proposal owners:
- Test affected packages in Copr.
- Do the mass spec update to introduce missing BuildRequire to them.
- Other developers: There should be no additional work for other developers. BuildRequiring setuptools might not be enough for all packages, but we will take care of them manually if it happens.
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
All affected packages needs rebuild after the mass spec update.
How To Test
Interested testers can push explicit BuildRequire on setuptools to the distgit and see in our Python 3.10 COPR whether the package starts to build again. Webhook should trigger rebuild automatically on new commit in rawhide branch.
User Experience
Regular distro users shouldn't notice any change in system behaviour.
Dependencies
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? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)