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
Is your feature request related to a problem? Please describe.
data movement in regridding routines is surprisingly tricky. When i rewrote the shell version of regrid-xy, i focused more on nailing down the overall functionality of the script and the underlying fregrid call. While that had benefits to getting the ball rolling, the current path handling scheme seems slightly prone to issues.
Describe the solution you'd like
A lot of the what the script currently does is handle paths/manipulations of such as strings, and then, at the last possible moment, type-cast those strings as pathlib.Path for e.g. a .unlink() or .exists() call.
Is your feature request related to a problem? Please describe.
data movement in regridding routines is surprisingly tricky. When i rewrote the shell version of
regrid-xy
, i focused more on nailing down the overall functionality of the script and the underlyingfregrid
call. While that had benefits to getting the ball rolling, the current path handling scheme seems slightly prone to issues.Describe the solution you'd like
A lot of the what the script currently does is handle paths/manipulations of such as strings, and then, at the last possible moment, type-cast those strings as
pathlib.Path
for e.g. a.unlink()
or.exists()
call.Additional context
@ceblanton took a whack at this in this PR here and described the issues in an issue here
The text was updated successfully, but these errors were encountered: