Bug 1924123 - Deprecate python-mock
Summary: Deprecate python-mock
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F34Changes
TreeView+ depends on / blocked
 
Reported: 2021-02-02 16:25 UTC by Ben Cotton
Modified: 2021-02-09 15:50 UTC (History)
2 users (show)

Fixed In Version: python-mock-3.0.5-14.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-09 15:50:51 UTC
Type: ---


Attachments (Terms of Use)

Description Ben Cotton 2021-02-02 16:25:53 UTC
This is a tracking bug for Change: Deprecate python-mock
For more details, see: https://fedoraproject.org/wiki/Changes/DeprecatePythonMock

The python-mock (python3-mock) package will be deprecated in Fedora 34. The package is a standard library backport for older Pythons, Fedora packages should use unittest.mock instead. Many still depend on mock, so we cannot remove it yet. Packagers are encouraged to work with upstream to switch to unittest.mock when available. A simple sed can be applied in %prep as a temporary (or even permanent) downstream solution.

Comment 1 Ben Cotton 2021-02-09 14:58:47 UTC
Today we reached the Completion deadline (testable) milestone in the Fedora schedule. All approved changes should be in a testable state. If you change is testable, please indicate this by setting the status to MODIFIED.

If you need to defer the change to Fedora 35 or withdraw the change entirely, please indicate this in a comment and NEEDINFO bcotton.

The 100% code complete deadline is Tuesday 23 February. By that date, your change should be fully implemented and the tracking bug set to ON_QA.

For other Fedora 34 milestones, see https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html

Comment 2 Miro Hrončok 2021-02-09 15:50:51 UTC
Sorry, just forgot to close this.


Note You need to log in before you can comment on or make changes to this bug.