)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5196,"name":"Matthew Treinish","email":"mtreinish@kortar.org","username":"treinish"},"change_message_id":"004e611995fb86d891cfa56452829468fd55c1a8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"524343a4_f0ee69ae","updated":"2022-10-05 15:42:23.000000000","message":"I actually think it\u0027ll work fine, the import structure is opportunistically use the stdlib import `importlib.metadata` and fallback to `importlib_metadata` on a `ImportError`, so for python \u003e 3.7 we\u0027ll never try using the pypi package because the stdlib import is present. This means capping the version on 3.7 only like this will maintain compatibility for the supported Python versions on stevedore 3.5.x. That being said updating the API usage to use the new API is fine from my perspective I just assumed it was too big/risky a change for a stable branch backport which is why I opted to just cap on the stable branch where we still support 3.7.\n\nI don\u0027t have a strong preference either way as long as we get a release out for Python 3.7 that works, because right now unless you manually cap importlib-metadata stevedore will error on 3.7.","commit_id":"f974e5fc42caf38880e39153f5c4bee498b944db"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"bf8c2ed5609480e8550f429f953df97fcf827f6c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f48f31f6_e8d6dd40","updated":"2022-10-04 16:37:56.000000000","message":"This won\u0027t work. While stevedore will only install importlib-metadata on Python 3.7, other packages can install it and we\u0027ll use it opportunistically. I\u0027ve proposed [1]. I think that\u0027s probably a better, long-term fix?\n\n[1] https://review.opendev.org/c/openstack/stevedore/+/860105/","commit_id":"f974e5fc42caf38880e39153f5c4bee498b944db"}]}