Hi Sandro! On Sun, Dec 22, 2019 at 02:47:10PM -0500, Sandro Tosi wrote: > > The current version packaged in Debian is very outdated, > > even in unstable. Please consider packaging the current > > upstream release. > > I'm echoing this request: the just released numpy/1.18.0 requires > sphinx >= 2.2.0, so we cannot upgrade numpy without an updated sphinx. > please consider package it at the earliest.
Unfortunately sphinx ≥ 2.0 dropped support for Python 2. So I should either wait until all blocking bugs of #938528 are resolved, or introduce a new source package like sphinx-python2 for the old version. However the latter solution will mean that we can no longer have shared sphinx-common and libjs-sphinxdoc packages, and we will need to have two versions of dh_sphinxdoc too (or one version that will generate different dependencies for old and new sphinx). This is something I wanted to avoid, because it is extra work for supporting a Python 2 version that will be dead in a few days. Recently your script bumped many Python 2 removal bugs to RC, with the intention to accelerate porting those packages to Python 3 (or getting them removed). Maybe better to wait a couple of months and then just upload new Sphinx and break its Python 2 reverse build-dependencies? Can you patch old Sphinx support into numpy for the time being? -- Dmitry Shachnev
signature.asc
Description: PGP signature
