Re: Packaging pytango 9.2.0
[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 Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
how to build sphinx doc when there is extension
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_OPTIONS)))
PYBUILD_SYSTEM=custom \
PYBUILD_BUILD_ARGS="cd doc && PYTHONPATH={build_dir}
http_proxy='127.0.0.1:9' {interpreter} -c \"import sys;from sphinx import
main;sys.exit(main(sys.argv))\" -N -bhtml source build/html" dh_auto_build #
HTML generator
dh_installdocs "doc/build/html" -p python-pyfai-doc
dh_sphinxdoc -O--buildsystem=pybuild
endif
I would like your opinion about this and if there is better way to do this ?
thanks
Frederic
RE:Packaging pytango 9.2.0
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
Architecture: any
Section: python
Depends: ${shlibs:Depends},
${misc:Depends},
${python3:Depends}
Provides: ${python3:Provides}
Description: An interactive Tango client (Python 3)
ITango works like a normal python console, but it provides a nice set of
features from IPython. It also adds set of PyTango specific features:
.
* automatic import of Tango objects
* device and attribute name completion
* list tango devices, classes, servers
* customized tango error message
* database utilities
.
This is the Python 3 version of the package.
the generated dependencies are
Package: python3-itango
Source: itango
Version: 0.1.3-1
Architecture: i386
Maintainer: Debian Science Maintainers
Installed-Size: 212
Depends: ipython3, python3-pytango, python3:any (>= 3.3.2-2~)
Section: python
Priority: extra
Homepage: http://www.tango-controls.org/static/PyTango/latest/doc/html/
Description: An interactive Tango client (Python 3)
ITango works like a normal python console, but it provides a nice set of
features from IPython. It also adds set of PyTango specific features:
.
* automatic import of Tango objects
* device and attribute name completion
* list tango devices, classes, servers
* customized tango error message
* database utilities
.
This is the Python 3 version of the package.
Re: Packaging pytango 9.2.0
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 (with "pytango pytohn3-tango" inside) in all packages that build depend on python3-tango or ship "pytango python3-tango" in debian/python3-tango.pydist (in pytango source package only). If upstream is sane WRT versioning, you can use "pytango python3-tango; PEP386" -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Re: how to build sphinx doc when there is extension
[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_sphinxdoc:
> ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS)))
> PYBUILD_SYSTEM=custom \
> PYBUILD_BUILD_ARGS="cd doc && PYTHONPATH={build_dir}
> http_proxy='127.0.0.1:9' {interpreter} -c \"import sys;from sphinx import
> main;sys.exit(main(sys.argv))\" -N -bhtml source build/html" dh_auto_build #
> HTML generator
> dh_installdocs "doc/build/html" -p python-pyfai-doc
> dh_sphinxdoc -O--buildsystem=pybuild
> endif
>
>
> I would like your opinion about this and if there is better way to do this ?
how about doing it outside pybuild? Do you really need to build it for
each interpreter / version?
If you need the build dir:
override_dh_sphinxdoc:
ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS)))
PYTHONPATH=$(pybuild --system=custom -i python3 --build
--build-args="echo {build_dir}") \
cd doc && http_proxy='127.0.0.1:9' sphinx-build -N -bhtml source
build/html
dh_installdocs "doc/build/html" -p python-pyfai-doc
dh_sphinxdoc -O--buildsystem=pybuild
endif
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
RE:how to build sphinx doc when there is extension
> 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 whcih can be automatise at the autodep8 level for python ?
> If you need the build dir:
> override_dh_sphinxdoc:
> ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS)))
> PYTHONPATH=$(pybuild --system=custom -i python3 --build
> --build-args="echo {build_dir}") \
>cd doc && http_proxy='127.0.0.1:9' sphinx-build -N -bhtml source
> build/html
the problem with sphinx-build is that it use python2
#!/usr/bin/python
this is why I extract the content of sphinx-build directly nthe rules file.
but this is ugly since I have no garantie that this snipset willnot chang ein
the near futur.
cheers
Frederic
Re: how to build sphinx doc when there is extension
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 documentation, though. Correct? If so, this package is not a good place to do the test you describe. > th eunit test is > try to import all the modules provided by a packages. That isn't a good fit for “build the documentation”. It also does not explain why you try to do it with every interpreter. > Is there something whcih can be automatise at the autodep8 level for > python ? You can start with the tests I have in ‘python-coverage’ https://sources.debian.net/src/python-coverage/4.2%2Bdfsg.1-1/debian/tests/> which allows you to specify the module names to test. -- \ “Education is learning what you didn't even know you didn't | `\ know.” —Daniel J. Boorstin, historian, 1914–2004 | _o__) | Ben Finney
