Comment 7 for bug 1840507

Yes, it does get a little weird since the bug in question appeared in a release only on the master branch of a project which maintains stable branches as well. There would be no guarantee of a means for distributors of 2.22.0 to backport a clean fix, though I suppose that could still be possible depending on how much they care about the related unit test issue. Regardless, since Python 3 support in 2.22.0 was marked as experimental, that means we could similarly consider it covered by class B3 in our report taxonomy as well.

As this plan has the consent of both the original reporter and the Swift PTL (being one and the same person), I won't delay further in switching it to public. Thanks, Tim!