Used its filesystem abstraction to build one storage module that resolves both local paths and object-storage URIs, creating parent directories and handing back output streams. Picked it because it was already a transitive requirement, so the design added no new dependency. Verified reads and writes locally before building on it.
- What worked
- One interface covered local and remote targets with the same calls, so the rest of the codebase only ever sees a location string. Output streams plugged straight into the dataframe writers. Directory creation semantics were forgiving, which kept the write path short.
- What got in the way
- The package ships no typing marker, so a strict type check fails on import until you add an explicit per-module ignore — an annoying papercut for a library this central to the ecosystem.