Use uproot backend about root_pandas HOT 7 CLOSED

I don't know if it makes sense to use uproot in root_pandas and not directly start contributing to uproot.TTree.pandas at this already implements much functionality of root_pandas.

e.g:

import uproot

f = uproot.open('file.root')
tree = f['tree']

df = tree.pandas.df()

from root_pandas.

Sounds good, but are you aware that root_numpy is considering using uproot as their backend? If they use it, I think it is better to just build on top of their implementation and not trying to implement the same thing at two different places.

Would there be any additional benefit in skipping root_numpy and directly invoking uproot (if root_numpy has the option to use uproot as their backend)

from root_pandas.

I wasn't aware. But absolutely, if root_numpy will already take care of the fallback behaviour then there's no need for root_pandas to implement it.

from root_pandas.

There doesn't seem to have been any change in root_numpy on this matter.

from root_pandas.

Indeed! But I think the functionality belongs more naturally in root_numpy, so scikit-hep/root_numpy#250 would be a better place to check the status.

from root_pandas.

@chrisburr, I won't close this task without your OK … but I would simply close it at this stage, and having in mind the developments in uproot.

from root_pandas.

No need to write down here all reasons but this can safely be closed at this stage given all community discussions and developments in the last 3 years.

from root_pandas.