[PICCA Frederic-Emmanuel, 2016-08-30]
> dh_python add a dependency to python-pytango and not python-tango
Did you add dh-python to Build-Depends of that package?
Did you add python{,3}-tango to Build-Depends?
.oO( did you try to turn it off and on again? ;)
--
Piotr Ożarowski
Hello
I am using this snipset when I want to build the sphinx documentation for all
python available. (this is a sort of unit test).
Usually the sphinx doc use auto-doc and then it allows to check that all
modules can be imported.
override_dh_sphinxdoc:
ifeq (,$(findstring nodocs, $(DEB_BUILD_
Here for itango
Build-Depends: debhelper (>= 9),
dh-python,
python-all-dev,
python-setuptools,
python-tango,
python3-all-dev,
python3-setuptools,
python3-tango
Package: python3-itango
Architec
Ah, right, `dpkg -S foo.egg-info` (i.e. search for locally installed
eggs) has lower priority than fallback files. I will give fallback files
provided by dh-python package (those without versioned dependency) a
lower priority in next upload. Until then, please use
debian/py3dist-overrides to fix it
[PICCA Frederic-Emmanuel, 2016-08-30]
> I am using this snipset when I want to build the sphinx documentation for all
> python available. (this is a sort of unit test).
> Usually the sphinx doc use auto-doc and then it allows to check that all
> modules can be imported.
>
> override_dh_sphinxdo
> how about doing it outside pybuild? Do you really need to build it for
> each interpreter / version?
It is a sort of unit test during the build that auto-doc works for all versions
of the interpreter.
th eunit test is
try to import all the modules provided by a packages.
Is there something w
PICCA Frederic-Emmanuel
writes:
> > how about doing it outside pybuild? Do you really need to build it for
> > each interpreter / version?
>
>
> It is a sort of unit test during the build that auto-doc works for all
> versions of the interpreter.
You're only installing one version of the documen
7 matches
Mail list logo
