| *** jhorstmann is now known as Guest4786 | 10:52 | |
| *** jhorstmann is now known as Guest4789 | 11:21 | |
| clarkb | this is fun it appears that the latest pip that runs with python3.6 vendors a pep517 that understands pep660 but the latest setuptools that runs under python3.6 does not | 17:09 |
|---|---|---|
| clarkb | so now I'm down a big rabbit hole of vendoring the pep660 implementation in setuptools into pbr so that we can continue to have python3.6 support | 17:09 |
| fungi | that's a rather odd, and surprising, gap | 17:11 |
| fungi | i really wish "editable" installs just weren't a thing, but lots of people seem to find them useful | 17:14 |
| clarkb | https://zuul.opendev.org/t/openstack/build/92784bf21bf24cd39de0bee7528e1a66/log/job-output.txt#694 that is my takeaway from this error anyway | 17:29 |
| clarkb | setuptools 64.0.0 or newer is needed for pep660 but python3.6 can only do setuptools 59.x.y | 17:30 |
| clarkb | but the pip there is happily using this code path instead of the legacy one | 17:30 |
| clarkb | then it explodes | 17:30 |
| clarkb | this is quickly becoming whackamole where you fix the python3 problem by vnedoring newer python3 code but that breaks python2... | 17:49 |
| clarkb | I'm hoping that we can kinda flip the script though and make modern python use of pbr less hacky even if it means making old python use of pbr more hacky | 18:05 |
| fungi | yeah, ideally pbr has to do a lot less since modern python packaging is starting to catch up to pbr's features | 18:06 |
| clarkb | side note it is interesting to see how python3 isms "pollute" code bases when they don't really add any value. Like ['foo', *opts, *otherlist] vs ['foo'] + opts + otherslist | 18:06 |
| tonyb | at what point do we "give up" and create pbr2 that supports python 2.7 and keep pbr for python3? | 23:02 |
| tonyb | and could that actually help? | 23:02 |
| fungi | it doesn't seem like python 2.7 is causing any real problem, it's that for pip and setuptools there is a nexus at python 3.6 where projects with a pyproject.toml can't be installed in editable mode | 23:16 |
| fungi | and pbr wants to have a pyproject.toml and be installed in editable mode for certain tests while supporting python 3.6 | 23:17 |
| clarkb | tonyb: fungi: right in the thread that brought this all up (its a pbr change) I basically said we can/should consider that when pbr on python2 becomes a problem | 23:56 |
| clarkb | so far it hasn't been a problem. The reason to avoid it is then everything using it has to flip flop the dep one way or the other dependning on how we do it | 23:56 |
| clarkb | the problem I've run up against today is pypa not making their releases align between tools | 23:57 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!