On 2024-04-05 18:27:48 +0000 (+0000), Jeremy Stanley wrote:
Just a heads up that Chris is raising concerns about continued maintenance of the Paste library, which more than a few of our projects rely on:
https://github.com/cdent/paste/discussions/91
It's worth considering whether we would offer to adopt/fork it or if there are straightforward migration paths to actively maintained alternatives.
For the benefit of those not following the issue, here's the quick summary:
Chris had hoped that OpenStack and other users of the paste library would migrate off of it, but that doesn't ever seem to have finished (did it even get started?). Paste relies on some deprecated "dead batteries" which are being removed from the Python standard library in 3.13, so it will break without intervention.
There is now a PR to switch it to using an external version of the deprecated bits, but this is really a stop-gap. If OpenStack is going to continue using paste in the long term, that will require volunteers to actively maintain it; but the general recommendation is to replace our use of paste with some (non-drop-in) alternative better aligned with the current state of the Python ecosystem.