wlav

I can reproduce it, but haven't been able to formulate a hypothesis as to why the behavior is such. My best guess is that placing `set_debug()` also disables switching off...

Found the source ... it's a piece of code that explicitly checks whether classes are complete (and thus can be bound). Still not sure how the debugging level plays into...

Cling uses this command `LC_ALL=C x86_64-conda-linux-gnu-c++ -O3 -DNDEBUG -xc++ -E -v /dev/null 2>&1 | sed -n -e '/^.*include/,${' -e '/^ \/.*include/p' -e '}'` to find the standard headers. I'm surprised...

What does executing: ``` LC_ALL=C x86_64-conda-linux-gnu-c++ -O3 -DNDEBUG -xc++ -E -v /dev/null 2>&1 | sed -n -e '/^.*include/,${' -e '/^ \/.*include/p' -e '}' ``` on the command line in the...

Sorry for being dense, but picking up on this "I am using a jupyter server hosted by my collaboration." to make sure we're on the same page: the jupyter server...

My guess for the code "getting stuck" is a bad interaction between signal handlers. Does the code still hang if you remove these lines: ``` import cppyy.ll cppyy.ll.set_signals_as_exception(True) ``` As...

Sorry, yes, just setting `EXTRA_CLING_ARGS` does not always cause a rebuild of the PCH (setting the envar `CLING_REBUILD_PCH` forces a rebuild). I thought that (effectively) removing `-march=native` was one of...

For the C++ std flag, can you check the location where the `cppyy_backend` python module is installed? There should be a directory called `etc` which has a file `dictpch/allCppflags.txt`. This...

I'm not sure about the first. You can check with: ``` import cppyy cppyy.cppxec("std::cerr

Having that `#include ` in the headers is definitely the same as explicitly including it with eg. `cppyy.include()`. I misremembered the process: the flags are picked up by `rootcling` when...