Friday, 2025-01-24

*** mhen_ is now known as mhen02:12
*** tosky_ is now known as tosky08:53
hberaud[m]damani: tkajinam : Please can you recheck https://review.opendev.org/c/openstack/futurist/+/939361 and https://review.opendev.org/c/openstack/oslo.utils/+/939233 when you have 2 min. Thanks in advance10:05
opendevreviewStephen Finucane proposed openstack/pbr master: Add openstack-tox-py313 job  https://review.opendev.org/c/openstack/pbr/+/94011710:30
damani[m]hberaud, done12:39
hberaud[m]thx12:39
*** tosky is now known as Guest686313:19
*** tosky_ is now known as tosky13:19
damani[m]can we get some new code review here please https://review.opendev.org/c/openstack/oslo.service/+/93578315:38
opendevreviewJeremy Stanley proposed openstack/pbr master: Add openstack-tox-py313 job  https://review.opendev.org/c/openstack/pbr/+/94011717:07
opendevreviewGhanshyam proposed openstack/whereto master: DNM: Testing ubuntu noble  https://review.opendev.org/c/openstack/whereto/+/93540818:37
gmannfungi: clarkb: any plan to release pbr soon? for the py312 setuptool things needed by the doc noble jobs 19:00
clarkbgmann: so again I want to stress that you don't need a pbr update to solve that problem19:03
clarkbbut yes we're releasing bindep today so that we can update bindep to use the latest pbr pyproject.toml support next, thne we'll update that to use a beta release of pbr and ifthat works we can release pbr for real19:03
gmannack19:04
clarkbthe updates to pbr make this stuff easier but they aer not required19:04
clarkbfungi: where did we end up with the beta release of pbr. That can happen concurrently right?19:05
clarkbI don't think we need to wait for the docs updates for that (would be good to have docs in place before the actual release but not a strong requirement for the beta release)19:05
gmannyeah, that will help to do things in easy way. I am trying to finish noble migration with min we can. 19:05
fungigmann: i've had a pbr pre-release request pending for weeks, waiting on the oslo ptl to +1: 19:08
fungihttps://review.opendev.org/93850519:08
fungiwe just wanted to make sure we tested it out as a pyproject build backend before tagging a full release19:09
fungii should probably just get more persistent about pinging people on stuff like that19:10
gmannfungi: ah thanks.  Daniel is on PTO maybe but let's see if we can get +1 damani[m] ^^ or I will ping Takashi  on monday19:11
fungibut as clarkb says that's not going to change the missing setuptools on python 3.12, just makes it possible for projects to declare they need setuptools for building if they use a pyproject.toml file19:12
fungier, and even that was already possible anyway, this just makes pbr do the same for itself too19:12
fungiin order to provide a demonstration that it works19:12
clarkbfungi: I think it will pull in setuptools on python3.12 due to the requirements.txt addition19:12
clarkbwhcih will noop on python 3.11 and older and might work for 3.12 and newer19:13
fungioh, right i guess that will work around the issue19:13
gmanntrue but use of pyproject.toml can take time and having setuptools from pbr requirement file will help but agree to have project start using  pyproject.toml 19:13
fungithe experimental bindep change series ending at https://review.opendev.org/938570 also demonstrates doing it19:15
fungi(i could have squashed them all, but this was good for untangling the different aspects and making it clearer to review the first time around)19:16
fungiclarkb: with pbr declaring setuptools as a requirement, what do you think about dropping setuptools from the build-system.requires list since pbr will pull it in now?19:18
clarkbfungi: you need it in both places I think?21:59
clarkbfungi: one determines what goes into isolated build environments to build pbr and the other specifies what packages to install alongside pbr for runtime needs?22:00
clarkbor maybe you only need it in both places for pbr itself but requirements is sufficient for everyone else?22:00
fungiclarkb: sorry, i meant in examples for projects using pbr, but in theory it would likely work that way for pbr itself too22:21
clarkbfungi: it isn't clear to me of `build` and similar tools will bundle setuptools for python<3.1222:23
clarkbso I think having it in the example is good belts and suspenders22:23
fungiit will install pbr, which declares that it depends on setuptools, so will install setuptools22:24
clarkbright but only for python3.12 or newer22:24
fungibut now that you mention it, we made the dependency on setuptools limited to newer python only22:24
fungisorry, tiny blackberry-type keyboard at the moment22:25
clarkbwe could drop that rule from requierments.txt but I did it that way to avoid unexpected interactiosn with older python. By limiting it to 3.12 and newer we're makign the problem space smaller and in a place where people are most likely to be willing to debug the problems because it is forward looking22:25
clarkbbut if we don't think that is a major risk we could drop the rule and do it globally22:25
clarkbit should still noop I think?22:25
clarkber I mean on python <3.12 it would see setuptools is already prsent and move along22:26
fungiyeah, it didn't seem necessary to me to limit it, if pbr gets installed somewhere that lacks setuptools it won't work anyway22:26
clarkbya I think the main concern was that we'd accidentally try to install something that would make things worse than if we just used what was already there22:28
clarkbI'd be happy to drop the limitation from requirements.txt and then use a beta release to do our best to try and catch any cases like that22:29
fungiwell, we can do a second beta too22:37
clarkbgood point22:38

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!