| tkajinam | fungi, note that we'll see more and more oslo components release without python 3.8 support, because we removed it according to update in the test runtime. | 02:20 |
|---|---|---|
| tkajinam | we can hold on requirement bump for a while but we eventually need to get rid of py38 jobs during this cycle otherwise we have to revert removal of py38 support which looks incorrect for me. | 02:20 |
| fungi | tkajinam: just because a version of python isn't included in the pti doesn't mean libraries are required to drop support for it. the pti says what versions must be tested, but that isn't necessarily mean that projects can't also test with other versions | 02:57 |
| fungi | also i'm particularly surprised that tooz would choose to break support for non-eol python versions, since i thought it was used by some non-openstack projects too, but maybe i'm mistaken in that | 02:58 |
| tkajinam | We can add back support for older python versions with proper test coverage if needed. | 03:03 |
| tkajinam | fungi, we didn't really discuss that point in detail when we merged the patch to transition supported runtimes, though in the past we removed py36/37 support during zed cycle so external usage is not something we did care at that time. tooz has stable branches so users can use older python versions as long as they need only bug fixes | 03:04 |
| fungi | yeah, i expect what we'll end up doing is add environment markers in requirements to limit tooz<4 when python<3.9, which will work until newer versions of other things start having conflicting dependency versions | 03:08 |
| fungi | but hopefully that will be enough to unblock projects who are trying to work on dropping their 3.8 testing | 03:08 |
| tkajinam | My main concern is that we are facing some problems with Ubuntu Jammy which is part of the tested runtimes. We can keep optional testing with Ubuntu Focal but we should ideally have the full test coverage in Jammy. | 03:08 |
| tkajinam | I mean the tests with Ubuntu Focal should be additional ones and should not replace something not working in Jammy | 03:09 |
| fungi | in the past we didn't merge requires-python changes in libs (or ended up reverting them) while projects depending on them were transitioning off those versions | 03:09 |
| tkajinam | yeah that's an option | 03:10 |
| fungi | but yes, jammy was part of the pti for 2023.1 so projects should have already been testing on it successfully before the last release (even if they were still required to also test on focal) | 03:10 |
| tkajinam | yeah | 03:14 |
| tkajinam | anyway what I was trying to tell first is that tooz is not only one dropping python 3.8 support and we likely face the same problem when a new oslo release is made | 03:14 |
| tkajinam | If we need some treatment (like reverting the strict minimum version requirement) then we likely have to make that change consistently to all oslo repos. | 03:14 |
| tkajinam | probably we have to ask the requirements team to hold on approving any bump of oslo libraries for now. | 03:15 |
| fungi | that might make sense, agreed | 03:17 |
| fungi | tkajinam: looks like even though tooz merged a change to set 3.8 as required early during zed (around week r-21), it didn't release that until just before the coordinated release (during r-6) | 03:22 |
| fungi | this time around, we're in week r-23, only about a month into the cycle | 03:23 |
| fungi | so the python version break was released about 4.5 months earlier than the one in zed | 03:25 |
| tkajinam | yeah. I guess no one required early adhoc release | 03:28 |
| frickler | ftr this affects most if not all of oslo https://review.opendev.org/q/topic:oslo-drop-py38, just a question of releases being made and u-c job failures getting resolved | 04:43 |
| tobias-urdin | imo removing py38 for oslo that early is wrong, i'm not sure on policy on that but i think libraries should trail projects on minimum version and not enforce it | 05:24 |
| sahid | o/ tkajinam | 06:51 |
| sahid | i have updated the change https://review.opendev.org/c/openstack/osprofiler/+/877358/12 according your suggestion | 06:52 |
| sahid | if you have a moment to have a look :-) | 06:52 |
| MaxLamprecht[m] | Hey openstack-oslo o/, can someone review https://review.opendev.org/c/openstack/oslo.privsep/+/873513 ? | 08:18 |
| opendevreview | Sahid Orentino Ferdjaoui proposed openstack/osprofiler master: profiler: add python requests profile https://review.opendev.org/c/openstack/osprofiler/+/879318 | 09:08 |
| opendevreview | Sahid Orentino Ferdjaoui proposed openstack/osprofiler master: profiler: add python requests profile https://review.opendev.org/c/openstack/osprofiler/+/879318 | 12:03 |
| fungi | bauzas mentioned in https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033468.html that there are now more libs with versions appearing in the constraints list that don't work with python 3.8, but no specifics as to which ones | 15:51 |
| fungi | oh, one of the commit messages says neutron | 15:53 |
| fungi | which they then backed out with https://review.opendev.org/881430 | 15:54 |
| fungi | seems like the only clean way to do this is to get everyone to stop running python 3.8 jobs and *then* everyone can merge the python_requires>=3.9 changes | 15:55 |
| fungi | otherwise everyone has to do it at the exact same moment | 15:56 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!