@ysagon We should make this change consistent across all ROOT easyconfigs where ROOT.py is available?

It seems that this got moved from /lib/root/ to /lib/ in a recent version of ROOT:

$ find software/ROOT -name ROOT.py
software/ROOT/v6.06.02-intel-2016b-Python-2.7.12/lib/root/ROOT.py
software/ROOT/v5.34.13-ictce-5.5.0/lib/root/ROOT.py
software/ROOT/v5.34.34-intel-2016a-Python-2.7.11/lib/root/ROOT.py
software/ROOT/v5.34.36-intel-2016a-Python-2.7.11/lib/root/ROOT.py
software/ROOT/v5.34.34-intel-2015b-Python-2.7.10/lib/root/ROOT.py
software/ROOT/v6.08.02-foss-2016a-Python-2.7.11/lib/ROOT.py

@boegel I have no idea! And I even don't know how people where importing ROOT.py without the PYTHONPATH set? Maybe it's not the correct way?

@ysagon Well, maybe nobody was, or they were just updating $PYTHONPATH themselves after loading the ROOT module?

I see no other way to make the import work...

BTW, I think it makes sense to also add an additional sanity check command to verify that import ROOT works, as follows:

sanity_check_commands = ["python -c 'import ROOT'"]

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2151.delcatty.os - Linux centos linux 7.3.1611, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.7.5
See https://gist.github.com/fb2e633319aed0ee75219fb43dd79fe1 for a full test report.

@ysagon Looks good!

So, shall we apply this to all ROOT easyconfigs for consistency?

@boegel I think so. Do you want me to do it?

@ysagon Yes, that would be nice, I can take care of submitting a test report.

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2569.golett.os - Linux centos linux 7.3.1611, Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz, Python 2.7.5
See https://gist.github.com/3eabcd7b0268208ab85f2cfd36c58e5e for a full test report.

lgtm

Going in, thanks @ysagon!