|Summary:||devel/py-setuptools: Update to 56.0.0|
|Product:||Ports & Packages||Reporter:||Goran Mekić <meka>|
|Component:||Individual Port(s)||Assignee:||freebsd-python (Nobody) <python>|
|Status:||Closed Overcome By Events|
|Severity:||Affects Only Me||CC:||meka, rudolphfroger|
|Bug Depends on:|
Description Goran Mekić 2021-04-23 09:04:57 UTC
Created attachment 224369 [details] setuptools.diff QA: * testport: OK (poudriere: 13.0, amd64 tested)
Comment 1 Antoine Brodin 2021-04-23 09:08:51 UTC
Does it work at runtime with python 2.7?
Comment 2 Goran Mekić 2021-04-23 09:27:38 UTC
Ah, I thought py27 is gone completely. My bad. Newer setuptools don't work with py27 based on https://setuptools.readthedocs.io/en/latest/python%202%20sunset.html, but some ports require it (for example, setuptools-rust requires setuptools>=46.1). Is there any resolution for this?
Comment 3 Rudolph 2021-05-05 06:15:36 UTC
Since a couple of big ports still depend on python 2.7 (like chromium), I think the way forward is creating a py27-setuptools port explicitly for these few cases (not sure how this works together with the PY FLAVORS) and setup the py-setuptools port explicitly for python 3 versions only. Currently other ports are now stuck because of this issue and I assume their number will slowly grow. I assume it can take many months before a thing like chromium decides to support python 3 which is not really acceptable but their's not much we can do about.