Update to a new upstream release of python-setuptools that is not completely compatible with previous releases. Since version 58+ upstream removed support for 2to3 during builds. This is a breaking change and projects are encouraged to port to a unified codebase.
(Opening on behalf of @bcotton who is on vacation today, we really want to proceed with this.)
+1
Eh, dropping support for 2to3 is just going to cause issues with old projects that haven't released in a while. The justification is that upstream is deprecating and dropping lib2to3, because it's incompatible with the new code parser introduced recently. But a) lib2to3 is only deprecated right now, it'll be there for a while yet, and b) the code that 2to3 is used on is old code that is not using any of the new fancy features, so some slight deficiencies in the old parser are of little relevance. I think this is a pretty poor decision by the setuptools upstream. (In Fedora it's just a bunch of packages, so we can fix them fairly easy… But for non-packages stuff this is just creating pain out of thin air.)
I see that the Change page contains an error:
lib2to3 was removed from Python 3 in version 3.10
AFAICS, it's only deprecated, and is still slated for removal in Python 3.12.
Anyway, +1 to the Change in Fedora. We don't have much choice but to follow upstream.
I see that the Change page contains an error: lib2to3 was removed from Python 3 in version 3.10 AFAICS, it's only deprecated, and is still slated for removal in Python 3.12.
I am sorry about this mistake. I've edited the Change.
APPROVED (+6,0,-0)
Metadata Update from @churchyard: - Issue tagged with: pending announcement
Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ETLLAT5A322SFOPRR3O52VUIB6IO3Q46/
Metadata Update from @zbyszek: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.