elaird/supy — pull request #181 by davidegerbaudo (2013-07-03 11:45:33+00:00)
Title: fix batch issue seen on screen session

These lines make sure that root is started in batch mode, no matter
which one is the first module to be pulled in. Without these lines I
observe (but not with all analyses) the error below:

X connection to localhost:32.0 broken (explicit kill or server shutdown).

For some reason, which I don't understand, this error seems to show up
only when running supy within a screen session (i.e. it doesn't show
up with the same analysis running within ssh). However, I can
reproduce this error message on lxplus and on other machines (most of
them running SLC5).

An alternative solution, maybe less invasive, would be to make sure that one
module is always imported before the other ones, and have the
`SetBatch(True)` only there.

Please let me know what you think.

Davide