Open picca opened 7 years ago
I can confirm that
- env["PYTHONPATH"] = os.pathsep.join(path)
+ #env["PYTHONPATH"] = os.pathsep.join(path)
solve the issue during the Debian build
We anyway have to inject the build_lib path to the subprocess. The env of the setup is not the same as the env needed for help2man. How do you execute the BuildMan BTW? I don't understand this part.
We uses
python setup.py build build_man
This is how I need to build the manpages.
override_dh_auto_build:
dh_auto_build
PYBUILD_SYSTEM=custom \
PYBUILD_BUILD_ARGS="PYTHONPATH={build_dir} xvfb-run -a --server-args=\"-screen 0 1024x768x24\" {interpreter} setup.py build_man" dh_auto_build
indeed this is done with the PYTHONPATH commented explained previously.
I just discoverd that the build_man failed with python3 when I do not use xvfb. So it seems that with python3 the --help command request a working X windows system. This is not true with python2
Hello, now thaht I can run the BuildMan via
python setup.py build and the right options during the Debian build, I get this in the generated manpages.
As you can see I get a RuntimeError, So the pyFAI loaded by the script is the one from the source. I need to figure out why this is the case.
The first culprite could be the PYTHONPATH modification done in the BuildMan
I would say. never ever modify an USER env in a setup.py script.
this is why in the autotolls you have
CFLAGS and AM_CGLAGS for the maintainer.
this is the principe of less surpise ;)