You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.
which is expected. However when calling awkward.save I get:
TypeError: failed to encode <uproot.tree._LazyFiles object at 0x7fda9b511908> (type: <class 'uproot.tree._LazyFiles'>)
The second piece is intended to be used for chaining some files instead of using only one as in the code shown. Is the virtualness expected to work in this case?
The text was updated successfully, but these errors were encountered:
In the latest uproot, _LazyTree fails, and _LazyFiles fails differently! So, first off, update to the latest uproot because something changed. I'll dig into the error, though.
Actually, I don't see anything in here that would enable persistence of lazily loaded trees or sets of trees from uproot. As far as I can see, it just hasn't been implemented, and there are a few subtleties that we'd have to solve to do it right.
This also bothers me because I remember saving lazy data from uproot. I don't remember when, but I see no evidence that it has been implemented (Mandela Effect?). For the moment, however, I think you should consider this not an existing feature.
The following code works as expected:
However, if I use
uproot.lazyarrays
directly:The second piece yields to:
which is expected. However when calling
awkward.save
I get:The second piece is intended to be used for chaining some files instead of using only one as in the code shown. Is the virtualness expected to work in this case?
The text was updated successfully, but these errors were encountered: