You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
c7n-policystream is currently pinned to 1.9.x which prevents it from making use of 3.11-compatible wheels that became available starting with 1.10.1
Feels like a dependency bump should cover us for policystream. The c7n-gcp/ratelimiter issue has more history than I was aware of, and the best next step isn't clear to me.
What did you expect to happen?
Pip installs of releases and poetry installs at dev time should work under Python 3.11.
Cloud Provider
Amazon Web Services (AWS)
Cloud Custodian version and dependency information
No response
Policy
No response
Relevant log/traceback output
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered:
As far as I can tell we're good here now - with the 0.9.21 release I'm seeing clean installs from pip and poetry on 3.11. I've got no real allegiance to a specific ratelimiter package, but pyrate seemed to be actively maintained with solid docs and minimal code changes on our side.
Describe the bug
There are a couple issues with upstream dependencies that break installs under Python 3.11:
c7n-gcp
had a known issue related to ratelimiter (see also Fix warning that coroutine decorator is deprecated since Python 3.8 RazerM/ratelimiter#10)c7n-policystream
is currently pinned to 1.9.x which prevents it from making use of 3.11-compatible wheels that became available starting with 1.10.1Feels like a dependency bump should cover us for policystream. The c7n-gcp/ratelimiter issue has more history than I was aware of, and the best next step isn't clear to me.
What did you expect to happen?
Pip installs of releases and poetry installs at dev time should work under Python 3.11.
Cloud Provider
Amazon Web Services (AWS)
Cloud Custodian version and dependency information
No response
Policy
No response
Relevant log/traceback output
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered: