Time to drop python2 support? #4624

Open
opened 2026-07-15 06:24:43 +00:00 by tkopecek · 2 comments
Owner

@mikem Maybe it is really time to branch py2 and do the cleanup? As 1.37 was pretty big release, maybe this is the window to do that?

@mikem Maybe it is really time to branch py2 and do the cleanup? As 1.37 was pretty big release, maybe this is the window to do that?
Author
Owner

Part of that sh/could be move to pyproject.toml

Part of that sh/could be move to pyproject.toml
Author
Owner

Another proposal - maybe we can specify minimal required version for mock? We then could drop/replace e.g. --new-chroot/--old-chroot and use --isolation instead, etc.

Another proposal - maybe we can specify minimal required version for mock? We then could drop/replace e.g. ``--new-chroot/--old-chroot`` and use ``--isolation`` instead, etc.
tkopecek referenced this issue from a commit 2026-08-14 11:30:37 +00:00
tkopecek referenced this issue from a commit 2026-08-14 11:34:58 +00:00
tkopecek referenced this issue from a commit 2026-08-14 11:44:45 +00:00
tkopecek referenced this issue from a commit 2026-08-14 11:46:15 +00:00
tkopecek referenced this issue from a commit 2026-08-14 12:25:56 +00:00
tkopecek referenced this issue from a commit 2026-08-18 07:15:22 +00:00
tkopecek referenced this issue from a commit 2026-08-19 06:46:07 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
koji/koji#4624
No description provided.