Open jeanfeydy opened 2 years ago
Hello Jean,
I just did modifications in branch redirect_stderr
to get the stderr output, using subprocess.run
with the option redirect_output=True
. The only problem is that this option appeared in Python 3.7 only. Do you think we can impose Python version >= 3.7 for KeOps ? Or someone know how to do without this option ?
Hi @joanglaunes ,
Since this is a fairly minor issue, do you think that we could simply detect the Python version and use the option if and only if Python >= 3.7? The main purpose of the fix would be to help as many users as possible to fix their configuration without creating an issue, so having a hard dependency on Python >= 3.7 would be counter-productive I think.
Ok it's done now in master.
Hi @joanglaunes, Thanks a lot, I will try this today!
Hi @joanglaunes, @bcharlier,
I am currently making final checks for the KeOps v2.0 release, and am noticing again a pretty cumbersome issue: C++ configuration issues are impossible to diagnose from a Jupyter notebook.
For instance, these two error messages:
and
are completely hidden from Jupyter notebook users (i.e. most data scientists), who only see:
in their notebooks cells when running e.g.
import pykeops; pykeops.test_numpy_bindings()
.In order to ease installation and configuration issues, do you think that we could redirect these "stderr" messages towards the Jupyter cells?
See you soon, Jean