Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] please switch du sphinx with python3 #124

Open
picca opened this issue Oct 8, 2017 · 7 comments
Open

[doc] please switch du sphinx with python3 #124

picca opened this issue Oct 8, 2017 · 7 comments

Comments

@picca
Copy link
Contributor

picca commented Oct 8, 2017

Hello, it would be nice to switch from sphinx (python2) to sphinx python3 in order to use a less deprecated python version.

thanks

@matze
Copy link
Contributor

matze commented Oct 8, 2017

I don't understand how this is affected by our code and not the build environment? Isn't Sphinx picking up whatever Python interpreter is currently installed? The only thing I do is looking for a sphinx-build script.

@picca
Copy link
Contributor Author

picca commented Oct 8, 2017

sorry matthias, I was updating the Debina package and needed to switch from python2 to python3.
It is trivial for the documentation :) python3-sphinx

now there is some code like the ufod and I would like to know how if it is python3 ready ? so I just need to switch from pyton-dev to python3-dev

@matze
Copy link
Contributor

matze commented Oct 8, 2017

It is trivial for the documentation :) python3-sphinx

Yes, that's what I mean, that's a build environment thing not something I could influence. The only Python piece we provide for the manual is conf.py and that looks sane to me.

now there is some code like the ufod and I would like to know how if it is python3 ready ?

ufod is C. The only offenders are ufo-mkfilter and ufo-prof, and seem to be okay. But I can check tomorrow morning.

@picca
Copy link
Contributor Author

picca commented Oct 8, 2017

I can confirm that ufo-launch is linked against libpython2.7, So It would be nice if we should link against the python3 version. Maybe to add a compile option in ordert to use python2 instead of the default python3 ;)

@picca
Copy link
Contributor Author

picca commented Oct 8, 2017

No I miss read the build log.

here the log

   dh_shlibdeps -a -O--buildsystem=cmake
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo0/usr/lib/x86_64-linux-gnu/libufo.so.0.13.0 was not linked against libgthread-2.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo-bin/usr/bin/ufo-query debian/libufo-bin/usr/bin/ufo-launch debian/libufo-bin/usr/bin/ufo-runjson were not linked against libgio-2.0.so.0 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo-bin/usr/bin/ufo-query debian/libufo-bin/usr/bin/ufo-launch debian/libufo-bin/usr/bin/ufo-runjson were not linked against libm.so.6 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo-bin/usr/bin/ufo-query debian/libufo-bin/usr/bin/ufo-launch debian/libufo-bin/usr/bin/ufo-runjson were not linked against libzmq.so.5 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo-bin/usr/bin/ufo-query debian/libufo-bin/usr/bin/ufo-launch debian/libufo-bin/usr/bin/ufo-runjson were not linked against libpython2.7.so.1.0 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo-bin/usr/bin/ufo-query debian/libufo-bin/usr/bin/ufo-launch debian/libufo-bin/usr/bin/ufo-runjson were not linked against libOpenCL.so.1 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo-bin/usr/bin/ufo-query debian/libufo-bin/usr/bin/ufo-launch debian/libufo-bin/usr/bin/ufo-runjson were not linked against libgthread-2.0.so.0 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo-bin/usr/bin/ufo-query debian/libufo-bin/usr/bin/ufo-launch debian/libufo-bin/usr/bin/ufo-runjson were not linked against libgmodule-2.0.so.0 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libufo-bin/usr/bin/ufo-query debian/libufo-bin/usr/bin/ufo-launch debian/libufo-bin/usr/bin/ufo-runjson were not linked against libjson-glib-1.0.so.0 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ufod/usr/bin/ufod was not linked against libOpenCL.so.1 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ufod/usr/bin/ufod was not linked against libgthread-2.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ufod/usr/bin/ufod was not linked against libzmq.so.5 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ufod/usr/bin/ufod was not linked against libjson-glib-1.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ufod/usr/bin/ufod was not linked against libgio-2.0.so.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ufod/usr/bin/ufod was not linked against libm.so.6 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ufod/usr/bin/ufod was not linked against libpython2.7.so.1.0 (it uses none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ufod/usr/bin/ufod was not linked against libgmodule-2.0.so.0 (it uses none of the library's symbols)

so I need some rest ;)

@picca
Copy link
Contributor Author

picca commented Oct 8, 2017

I just rebuild all the packages with --as-needed and I end up with a libufo package which depends on libpython2.7

@matze
Copy link
Contributor

matze commented Oct 9, 2017

I just pushed a reversion of an old commit. Now, libufo.so should only link against the Python development libs you set as the default. I will try to disentangle the build flags for the binaries from the lib itself (one more reason for meson ... ;-) )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants