2 ms·
As someone who used to use ROOT, I would strongly recommend against it. Its C++ implementation has all manner of hidden state, and this leaks into PyROOT. For
by MereInterest 8y ago
As someone who used to use ROOT, I would strongly recommend against it. Its C++ implementation has all manner of hidden state, and this leaks into PyROOT.
For example, ROOT has the concept of ownership, entirely distinct from the python sense of references. A file owns the histograms that were read from it. Closing the file changes all references to histograms read from that file to None. It took a large amount of digging to figure out how that was even possible (overwriting an existing object from within the C API), but I cannot for the life of me understand why.
ROOT has way too many gotchas for me to ever recommend it.
- cozzyd 8y agoYeah it has a lot of state that's not very pythonic (and I almost always use it from c++ or cling) but it is very good for semiinteractive plotmaking that's not possible in something like matplotlib. A lot of ROOT's legacy from the 90's shows, but ROOT6 has made a lot of progress.