Closed as not planned
Description
Based on this thread, there is some willingness to provide Python 3.9 support for this library.
As much as we'd like to migrate to Python 3.10+, it's difficult to migrate enterprise codebases before official EOL status.
I'm curious what the process would be for making such a change? I'm assuming there's more work beyond just putting up a PR with 3.9 compatible code.
Happy to assist in this effort if necessary.
Metadata
Metadata
Assignees
Labels
No labels