Re: Bug#1004331: pytorch: b-d on python3-all-dev, but not built for all supported Python3 versions
PyTorch's setup.py + CMake build system is complicated.
I'm only building it for a single python version, and
there is no plan for supporting more than that.
If we don't separate the entangled setup.py and CMake
building process, we have to build 2400+ C++ objects
twice to support two python3 versions.
Should anyone be interested in this I'm willing
to review patch and merge, but I don't recommend doing so.
And possibly pytorch 1.8.X LTS release does not support
python 3.10. In that case supporting both would be
pointless.
On Wed, 2022-01-26 at 12:52 +0100, Gard Spreemann wrote:
>
> Graham Inggs <ginggs@debian.org> writes:
>
> > Source: pytorch
> > Version: 1.8.1-3
> > Severity: serious
> > Tags: ftbfs
> > User: debian-python@lists.debian.org
> > Usertags: python3.10 python3-all-dev
> >
> > Hi Maintainer
> >
> > This package build-depends on python3-all-dev, but does not build
> > extensions/libraries for all supported python3 versions. This is
> > seen
> > on the transition tracker for adding python3.10 support [1] and
> > creates false positives.
> >
> > Please either replace the b-d python3-all-dev with python3-dev, or
> > build for all supported Python3 versions. With the former solution
> > yet get later exposure to a new python3 version, with
> > the latter solution you get early exposure.
>
>
> I took a look at this, and I'm not sure why dh_python3 isn't able to
> build for all supported versions in this case. Relatedly: I'm puzzled
> by
> why we have an override_dh_auto_build with an empty rule. Can someone
> enlighten me?
>
>
> -- Gard
>
Reply to: