>> No releases will be removed from PyPI, but if pre v3 syntax is still >> used, Sphinx 6.0 would fail to properly parse it. > And that's the crux of the problem. From kernel POV I'd very much prefer > not setting an upper bound for the Sphinx version. I think it's > important to be able to build the documentation using the latest Sphinx, > and gradually iron out the inevitable quirks that arise. > However, if you decide to drop support for pre v3 syntax in Sphinx v6, > and we decide to stick to being able to use pre v3 Sphinx, we can't move > forward to newer versions until we bump the lower bound for the Sphinx > version to v3+. (Or we need to hack around Sphinx version differences in > kernel, but I think that would be best avoided.) I don't want to be in the position of knowingly breaking the documentation tooling for the kernel. A strawman of a compromise would be for us (Sphinx) to delay the removal to Sphinx 7.0, and the kernel to increase the minimum to Sphinx 3.1 (required for ".. c:namespace::"). That would enable the kernel to gradually update the syntax over a longer period, as I believe you won't be able to use the v3 syntax currently. Equally, Jonathan said he was hesitant to increase the minimum to Sphinx 3, so perhaps that wouldn't work. A
