)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"2a683326aae87ce92e92f2da05eb6d6c3571b8ea","unresolved":true,"context_lines":[{"line_number":9,"context_line":"pip 23.1 removed the \"setup.py install\" fallback for projects"},{"line_number":10,"context_line":"that do not have pyproject.toml and now uses a pyproject.toml"},{"line_number":11,"context_line":"which is vendored in pip."},{"line_number":12,"context_line":"To address that, this change adds the minimal pyproject.toml"},{"line_number":13,"context_line":"to enable pbr to be properly used to build editable wheels."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"This is required to support installing devstack on"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"acdf13ab_6052dba3","line":12,"updated":"2023-11-02 19:16:47.000000000","message":"Why minimal? If we want to move to using `pyproject.toml`, why wouldn\u0027t we do our best to minimize/remove `setup.cfg` and `setup.py`? (Maybe even `requirements.txt`?)\n\nI don\u0027t particularly *like* the proliferation of packaging/install-related files, and (perhaps naively) thought that `pyproject.toml` could be part of the solution to that...","commit_id":"ff7dcee1371c899a74816e1223dcdede30b8df1e"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"27b2d5b768af08c23e6defa67ba327ac9e4b2add","unresolved":true,"context_lines":[{"line_number":9,"context_line":"pip 23.1 removed the \"setup.py install\" fallback for projects"},{"line_number":10,"context_line":"that do not have pyproject.toml and now uses a pyproject.toml"},{"line_number":11,"context_line":"which is vendored in pip."},{"line_number":12,"context_line":"To address that, this change adds the minimal pyproject.toml"},{"line_number":13,"context_line":"to enable pbr to be properly used to build editable wheels."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"This is required to support installing devstack on"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"06491020_544ee104","line":12,"in_reply_to":"acdf13ab_6052dba3","updated":"2023-11-15 15:27:20.000000000","message":"we dont want to remvoe supprot for setup.py\n\nwe just want to enabel pyproject.toml\n\nremoving setup.py/setup.cfg would be a much large change and im not sure everyoen will be ok with that as it will break peopel that depend on setup.py today.","commit_id":"ff7dcee1371c899a74816e1223dcdede30b8df1e"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"2a683326aae87ce92e92f2da05eb6d6c3571b8ea","unresolved":true,"context_lines":[{"line_number":15,"context_line":"This is required to support installing devstack on"},{"line_number":16,"context_line":"centos stream 9 and related distros with GLOBAL_VENV\u003dTrue"},{"line_number":17,"context_line":"Without this change the wsgi scripts are not generated in"},{"line_number":18,"context_line":"editable mode. i.e. pip install -e /opt/stack/keystone"},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"See https://pip.pypa.io/en/stable/news/#v23-1"},{"line_number":21,"context_line":"and https://github.com/pypa/pip/issues/8368 for more"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"ab2d8fc5_a122e778","line":18,"updated":"2023-11-02 19:16:47.000000000","message":"OK, this seems like the driving issue -- do all projects need this, or only those with `wsgi_scripts` entry points?\n\nIs running pip with `SETUPTOOLS_ENABLE_FEATURES\u003dlegacy-editable` off the table? I don\u0027t think I\u0027ve seen that discussed anywhere, and having that in my environment gets me an editable keystone install with wsgi scripts.","commit_id":"ff7dcee1371c899a74816e1223dcdede30b8df1e"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"27b2d5b768af08c23e6defa67ba327ac9e4b2add","unresolved":true,"context_lines":[{"line_number":15,"context_line":"This is required to support installing devstack on"},{"line_number":16,"context_line":"centos stream 9 and related distros with GLOBAL_VENV\u003dTrue"},{"line_number":17,"context_line":"Without this change the wsgi scripts are not generated in"},{"line_number":18,"context_line":"editable mode. i.e. pip install -e /opt/stack/keystone"},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"See https://pip.pypa.io/en/stable/news/#v23-1"},{"line_number":21,"context_line":"and https://github.com/pypa/pip/issues/8368 for more"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"ef035d29_e486a5a7","line":18,"in_reply_to":"ab2d8fc5_a122e778","updated":"2023-11-15 15:27:20.000000000","message":"all projects shoudl supprot pip install -e as we rely on that for devstack\n\nonly project that have wsgi_scripts need ot wait till we extend pbr to supprot generatign the wsgi_scripts\n\nSETUPTOOLS_ENABLE_FEATURES\u003dlegacy-editable is deprecated and will eventually be removed so ya it kind of is at least in terms of a long term solution.\n\nit woudl be a posible short term solution for devstack but we will eventrually need to make this change when that is remvoed form setuptools.\n\n\non alternivie to extending pbr to make wsgi_script work again is just to vendor thw wsgi script in the relevent projects and expecort it as a console script.\n\nmost installer depened on the wsgi scripts being exported to ${prifix}/bin\nso if we proceed with adding supprot for pyproject.toml we cant regress that without a deprecation cycle.","commit_id":"ff7dcee1371c899a74816e1223dcdede30b8df1e"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"6ff0c184d9146bbf72a3b25f566de5a1f3c6922e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fbc89530_9f06c738","updated":"2023-11-02 15:57:50.000000000","message":"check experimental","commit_id":"ff7dcee1371c899a74816e1223dcdede30b8df1e"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"85d58dad461a3662d50d5e1ff9d834b86db92198","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"28d482e5_3ba6cb95","updated":"2024-01-25 18:14:31.000000000","message":"recheck\n\nI\u0027d like to refresh my memory on the check failures...","commit_id":"ff7dcee1371c899a74816e1223dcdede30b8df1e"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"27b2d5b768af08c23e6defa67ba327ac9e4b2add","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e157cdd0_4cb5432b","updated":"2023-11-15 15:27:20.000000000","message":"recheck swift does not use wsgi_scripts so the current pbr functionality should actully be all that is required for swift.\n\nwe could also elect to deprecate setup.py/setup.cfg goign forward but i dont think we shoudl remove that this cycle.","commit_id":"ff7dcee1371c899a74816e1223dcdede30b8df1e"},{"author":{"_account_id":1179,"name":"Clay Gerrard","email":"clay.gerrard@gmail.com","username":"clay-gerrard"},"change_message_id":"638f1c7a32aac4fff06bec035878c6d9ee0c60c1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ebbc64b4_f89d44de","updated":"2025-02-12 15:08:49.000000000","message":"I recently discovered that this is very helpful on py38","commit_id":"7f5333e6fc79c5e6151e44e9c4a34b6f16c687ab"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"06bd84063238e7868549651bc1cbaea2f5852dc0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"dce14e54_504cf0af","updated":"2025-02-12 21:23:26.000000000","message":"Interesting:\n```\n  Getting requirements to build editable: started\n  Getting requirements to build editable: finished with status \u0027error\u0027\n  ERROR: Command errored out with exit status 1:\n   command: /home/zuul/src/opendev.org/openstack/swift/.tox/py36/bin/python /home/zuul/src/opendev.org/openstack/swift/.tox/py36/lib/python3.6/site-packages/pip/_vendor/pep517/in_process/_in_process.py get_requires_for_build_editable /home/zuul/xfstmp/tmpey4b8kbo\n       cwd: /home/zuul/src/opendev.org/openstack/swift\n  Complete output (10 lines):\n  Traceback (most recent call last):\n    File \"/home/zuul/src/opendev.org/openstack/swift/.tox/py36/lib/python3.6/site-packages/pip/_vendor/pep517/in_process/_in_process.py\", line 363, in \u003cmodule\u003e\n      main()\n    File \"/home/zuul/src/opendev.org/openstack/swift/.tox/py36/lib/python3.6/site-packages/pip/_vendor/pep517/in_process/_in_process.py\", line 345, in main\n      json_out[\u0027return_val\u0027] \u003d hook(**hook_input[\u0027kwargs\u0027])\n    File \"/home/zuul/src/opendev.org/openstack/swift/.tox/py36/lib/python3.6/site-packages/pip/_vendor/pep517/in_process/_in_process.py\", line 144, in get_requires_for_build_editable\n      return hook(config_settings)\n    File \"/home/zuul/xfstmp/pip-build-env-i3m0w11q/overlay/lib/python3.6/site-packages/pbr/build.py\", line 95, in get_requires_for_build_editable\n      return build_meta.get_requires_for_build_editable(\n  AttributeError: module \u0027setuptools.build_meta\u0027 has no attribute \u0027get_requires_for_build_editable\u0027\n```","commit_id":"7f5333e6fc79c5e6151e44e9c4a34b6f16c687ab"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"7d02a031e9f3507981ddcc69cae7cc5003c3d68c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e9ce8c78_a46154ae","updated":"2025-02-12 20:55:24.000000000","message":"recheck\n\nWhy didn\u0027t I take notes last time!?","commit_id":"7f5333e6fc79c5e6151e44e9c4a34b6f16c687ab"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"b15b03dd58be62d8ab8fb33c37d2f9cee999a30d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"81e7316e_5dac6186","updated":"2025-05-07 00:34:01.000000000","message":"check experimental","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f937b53d20f016c704deb0ba2cb9d3d5a48e401d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"807b1a5e_556cab3d","updated":"2025-05-06 23:39:29.000000000","message":"this is just a rebase to get some recent resutl given most project (all that used wsgi_script and didnt have pyproject.toml) were broken when py 39 was dropped form requiremnts and we unpind a bunch of depdecies as a result\n\n\nim not sure if this is neded by swift or not but its once of the service enabled in our devstack josb by default os i wanted to pull this into \n\nhttps://review.opendev.org/c/openstack/devstack/+/898845\nwhich is testing if we have finally gotten to the point where we can enabel installing in a venv for all distos.\n\nthat no-longer the main driving force for this work.\n\nwith the release of setuptools 80 and pip 25.1 the fallback to calling setup.py when pyproject.toml is not present is gone\n\nthat means without this swift will be instaleld using setuptools without pbr enabeld\n\nso all the pbr funtionatliy liek recording the git sha the package was built form\nis currently not being used on master.\n\nswift does not use the wsgi_script extension so its not brken by that under devstack but its proably relying implictly on some other pbr functionatliy.","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"f7838da4f8a59c261e30c2a1469b82e319f93c21","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"e258cec5_0b71a46a","in_reply_to":"11457048_cd530d60","updated":"2025-05-07 19:18:08.000000000","message":"Oh yeah, I didn\u0027t mean to imply that this should wait on a PTI update! I was just curious to know what the plan was, and\n\n\u003e `python3 -m build --sdist` or `python3 -m build --wheel`\n\nseems like a perfectly reasonable path to work toward.\n\n\u003e You will note that they have been more aggressive in also moving content form\nsetup.cfg to pyproject.toml\n\nFWIW, I took a similarly maximalist approach when [experimenting with it for pyeclib](https://review.opendev.org/c/openstack/pyeclib/+/947543).","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"de13dfab2745fd4c07a5f621fd6b66e5a321a226","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"11457048_cd530d60","in_reply_to":"22892f1d_59d80821","updated":"2025-05-07 10:04:51.000000000","message":"we do not need to update the PTI\nwe can but this is a purely additive change they can still install it the old way if there tooling still supports it.\n\nThis change is making the modern version enable our pbr funtionatliy.\nThis does not impact the operator at all.\n\ni didnt remove setup.py so any workflows that used it directly still work\nsince pip wont use setup.py any more this patch just makes sure that a pyproject.tomls is avaiable that uses pbr like setup.py does today.\n\n\nthe command listed here https://github.com/openstack/governance/blob/master/reference/pti/python.rst#specific-commands\nstill work\n\nits not the recommended way to build python package by the python package athtority\nbut i went out of my way to make sure that was not broken when first looking into this.\n\nin a future releas we may decided its time to stop supproting \n\n`python setup.py sdist` or `python setup.py bdist_wheel`\n\nthe current recomemnd way to build packates is to use\n\n`python3 -m build --sdist` or `python3 -m build --wheel`\n\nwe may as a community want to move to that but this change does not force use to do that it just makes the new way work too.\n\nhttps://packaging.python.org/en/latest/guides/modernize-setup-py-project/#how-to-modernize-a-setup-py-based-project\nhttps://packaging.python.org/en/latest/discussions/setup-py-deprecated/#setup-py-deprecated\n\nThe infra team are primarly using bindep as there testing ground for moving to pyproject.toml as the primary way we encode our packaging metadta\n\nYou will note that they have been more aggressive in also moving content form\nsetup.cfg to pyproject.toml as they add suprpto in pbr and drop older python verions.\nhttps://opendev.org/opendev/bindep/src/branch/master/pyproject.toml\n\nI\u0027m intentionally not doing that in this patch to make the minimum possible, meaning incremental change.\nproject are free to move content to pyproject.toml later if they want to.","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"f098436b9336485132070e289b4f0c71e6b22896","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"22892f1d_59d80821","in_reply_to":"807b1a5e_556cab3d","updated":"2025-05-07 00:33:52.000000000","message":"\u003e with the release of setuptools 80 and pip 25.1 the fallback to calling setup.py when pyproject.toml is not present is gone\n\nI feel like this has implications for the [PTI](https://governance.openstack.org/tc/reference/pti/python.html#specific-commands) -- at the very least, it indicates that the PTI is in need of updating so it reflects how operators actually install and consume our software. What\u0027s the plan there?","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"6a1376ad53052d6c4c1ba718b10ac62abccbec47","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"1da4deae_cc83806d","updated":"2025-05-14 18:03:09.000000000","message":"Dropped py36 support in https://review.opendev.org/c/openstack/swift/+/949684 -- do we want to just roll this back to PS3? I think that should work now.","commit_id":"aa259d9e11379e4ed5d081cd0c7e228e4604f4fa"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"d701c7d86212c00a06ca879ba3d7349e96a9ac42","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":6,"id":"b937c86d_b6a15cb4","in_reply_to":"1da4deae_cc83806d","updated":"2025-05-15 10:16:42.000000000","message":"sure ill do that shortly.","commit_id":"aa259d9e11379e4ed5d081cd0c7e228e4604f4fa"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"a87b950025116fb6d0402f4ee28b1d53b8c07ffc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"e81e9eca_b3f57e5f","updated":"2025-05-15 21:43:31.000000000","message":"Hmm. I\u0027ll need a bit to dig into why the lower-constraints job is still running on py36 when [it should be on py37](https://github.com/openstack/swift/blob/4e2d08041ade8005d2552783f0b34161f797a718/.zuul.yaml#L489-L498)...\n\nBut otherwise this is looking good!","commit_id":"0b23aae25aa6612442fa1fa0f1c5c85b151a107f"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"b9a382faa7e8407a11af46d736a5599a2e4f9850","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"807c4d3d_a52bd597","updated":"2025-05-15 19:24:22.000000000","message":"check experimental","commit_id":"0b23aae25aa6612442fa1fa0f1c5c85b151a107f"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"64e6a0988a3d7cc5917191b038b4baad2223f4ad","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"a1a7c45f_82b9580c","updated":"2025-05-16 16:12:50.000000000","message":"oh you already reverted it back :) sorry i didnt get to it yesterday","commit_id":"43aa7ec26155ccc72d1213b4b9c61c272f607a2a"}],"pyproject.toml":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"f098436b9336485132070e289b4f0c71e6b22896","unresolved":true,"context_lines":[{"line_number":1,"context_line":"[build-system]"},{"line_number":2,"context_line":"requires \u003d [\"pbr\u003e\u003d6.0.0\", \"setuptools\u003e\u003d64\"]"},{"line_number":3,"context_line":"build-backend \u003d \"pbr.build\""}],"source_content_type":"text/x-toml","patch_set":3,"id":"b9e3c353_7051b737","line":2,"range":{"start_line":2,"start_character":27,"end_line":2,"end_character":41},"updated":"2025-05-07 00:33:52.000000000","message":"Looks like we might need to drop support for some older python versions; [`setuptools\u003d\u003d64.0.0`](https://pypi.org/project/setuptools/64.0.0/) has a `Requires: Python \u003e\u003d3.7`","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bdaf89d0461fc0461b7e25b2b2ef33ad50059ad2","unresolved":true,"context_lines":[{"line_number":1,"context_line":"[build-system]"},{"line_number":2,"context_line":"requires \u003d [\"pbr\u003e\u003d6.0.0\", \"setuptools\u003e\u003d64\"]"},{"line_number":3,"context_line":"build-backend \u003d \"pbr.build\""}],"source_content_type":"text/x-toml","patch_set":3,"id":"713aef6b_f92832c9","line":2,"range":{"start_line":2,"start_character":27,"end_line":2,"end_character":41},"in_reply_to":"0c134b10_82c4882a","updated":"2025-05-07 10:17:44.000000000","message":"this should readd 3.6 support but keep in mind that went end of life on 2021-12-23\nhttps://devguide.python.org/versions/#unsupported-versions\nyou can still use rocky/almalinux 8 to have 3.6 in a semi supproted state by the disto but even rocky/almalinux 9 is nolonger offically tested/supproted by the rest of openstack so this is strictly true only for swift and perhaps a hand fuloe of tools like pbr  bindep even requires 3.7 at this point.","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"6385ae26ac8a102a2fe6932aa36935f8d02a3eea","unresolved":true,"context_lines":[{"line_number":1,"context_line":"[build-system]"},{"line_number":2,"context_line":"requires \u003d [\"pbr\u003e\u003d6.0.0\", \"setuptools\u003e\u003d64\"]"},{"line_number":3,"context_line":"build-backend \u003d \"pbr.build\""}],"source_content_type":"text/x-toml","patch_set":3,"id":"a2e23e46_0a46cc4d","line":2,"range":{"start_line":2,"start_character":27,"end_line":2,"end_character":41},"in_reply_to":"4d387ba0_1ad7f4c0","updated":"2025-05-12 17:24:51.000000000","message":"so swift may be able to continue at least for now without a pyporject.toml\n\nit looks like pbr 6.0.0 which is the first verion to supprot editable installs requires a newer verison of setup tools then py3.6 can provide\n\nthe first release of pbr to supprot pyporject.toml was 5.7.0 we could try droppign the requiremetn to that and see if it passes.\n\ni guess its reqly up to the swift team if they want ot keep pyporject.toml and drop py36 or keep py36 and potabllyt not be installable properly on  newer pythons.\n\nswift is not using the pbr extenion to provide wsgi files so you not really forced to move to pyproject.toml if its still insallyable without one.\n\nbut there is obviously a risk as time moves on that it will break.","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"f7838da4f8a59c261e30c2a1469b82e319f93c21","unresolved":true,"context_lines":[{"line_number":1,"context_line":"[build-system]"},{"line_number":2,"context_line":"requires \u003d [\"pbr\u003e\u003d6.0.0\", \"setuptools\u003e\u003d64\"]"},{"line_number":3,"context_line":"build-backend \u003d \"pbr.build\""}],"source_content_type":"text/x-toml","patch_set":3,"id":"4d387ba0_1ad7f4c0","line":2,"range":{"start_line":2,"start_character":27,"end_line":2,"end_character":41},"in_reply_to":"713aef6b_f92832c9","updated":"2025-05-07 19:18:08.000000000","message":"\u003e you should keep in mind that swift is very much an outlier and its probably that you will find that harder and harder to supprot over time\n\nOh believe me, I\u0027m aware :-/\n\n\u003e it looks like swift is not follow the supprote version that the rest of openstack supprots and support significantly older verions of python.\n\nIt\u0027s the one downside to our insistence that upgrading Swift should be easy -- we\u0027ve made it easier and lower-risk than upgrading OS or even Python. As a result I know of sizeable clusters running Swift basically off master while still on py37.\n\nMaybe we could drop py36 sooner rather than later, though?","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"de13dfab2745fd4c07a5f621fd6b66e5a321a226","unresolved":true,"context_lines":[{"line_number":1,"context_line":"[build-system]"},{"line_number":2,"context_line":"requires \u003d [\"pbr\u003e\u003d6.0.0\", \"setuptools\u003e\u003d64\"]"},{"line_number":3,"context_line":"build-backend \u003d \"pbr.build\""}],"source_content_type":"text/x-toml","patch_set":3,"id":"f71d7fd5_5743aca7","line":2,"range":{"start_line":2,"start_character":27,"end_line":2,"end_character":41},"in_reply_to":"b9e3c353_7051b737","updated":"2025-05-07 10:04:51.000000000","message":"we do not support python \u003c 3.10 on master\n\nsupport for 3.6 was removed years ago.\nyoga was the last release to supprot it\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/yoga.rst\nzed raised the min verion to 3.8\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/zed.rst\nand\ndalmation 2024.2 raised it to 3.9\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/2024.2.rst\nand flamingo raised ti to 3.10\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/2025.2.rst\n\nits not curenlty possible to install on 3.9 as the requriements repo removed the pins that make that possibel 2-3 weeks ago. but 3.6-3.8 have not been posible for much much longer.\n\nand no if you have python 3.6 for example you can still just use setup.py install directly.\n\nthis is a purly additive change.\n\nyou could confire this like pbr itself \n\nhttps://github.com/openstack/pbr/blob/master/pyproject.toml\nThe support 3.6 currently, but that would make neutron special, and should be something that the neutron core team does themselves.","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"a1ee1d57b2d89b15a184e35133f7dbdd748085c6","unresolved":true,"context_lines":[{"line_number":1,"context_line":"[build-system]"},{"line_number":2,"context_line":"requires \u003d [\"pbr\u003e\u003d6.0.0\", \"setuptools\u003e\u003d64\"]"},{"line_number":3,"context_line":"build-backend \u003d \"pbr.build\""}],"source_content_type":"text/x-toml","patch_set":3,"id":"0c134b10_82c4882a","line":2,"range":{"start_line":2,"start_character":27,"end_line":2,"end_character":41},"in_reply_to":"f71d7fd5_5743aca7","updated":"2025-05-07 10:09:50.000000000","message":"hum i see looking at https://github.com/openstack/swift/blob/master/setup.cfg\nit looks like swift is not follow the supprote version that the rest of openstack supprots and support significantly older verions of python.\n\nill quickly copy the supprot form pbr but you should keep in mind that swift is very much an outlier and its probably that you will find that harder and harder to supprot over time","commit_id":"d6b97a9470f032a8f5e226db1046884aabea17ae"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"a36a85e0ca01a42135f246b624836bfb8995befa","unresolved":true,"context_lines":[{"line_number":4,"context_line":"  \"pbr\u003e\u003d6.0.0;python_version\u003e\u003d\u00273.7\u0027\","},{"line_number":5,"context_line":"  \"setuptools\u003e\u003d64.0.0;python_version\u003e\u003d\u00273.7\u0027\","},{"line_number":6,"context_line":"  # Add a PEP517 interface"},{"line_number":7,"context_line":"  \"pbr\u003e\u003d5.7.0;python_version\u003c\u00273.7\u0027\","},{"line_number":8,"context_line":"  # Fallback to whatever we can get otherwise."},{"line_number":9,"context_line":"  # Note, this is not something projects should typically"},{"line_number":10,"context_line":"  # need. Swift attempts to support a wide range of Python"}],"source_content_type":"text/x-toml","patch_set":6,"id":"cd8d6e63_2a551ea3","line":7,"range":{"start_line":7,"start_character":2,"end_line":7,"end_character":36},"updated":"2025-05-12 18:33:52.000000000","message":"if this does not work on 3.6 it means there is no version of pbr that both supprot\npyproject.toml and can work with 3.6 and the version of setup tools that is aviabel in that job so lets see if ci works","commit_id":"aa259d9e11379e4ed5d081cd0c7e228e4604f4fa"}]}