I sometimes need to split a CSV into batches of rows, process them, and then recombine them. It would be convenient if the --filename argument allowed for {} to be zero padded to preserve file sort ordering (during shell scripting; eg., the ls ordering).
For example, when batching into blocks of 30 rows, I'd like to see 000.csv, 030.csv, and so on. Currently, I might see 0.csv, 120.csv, as the ordering with 30.csv appearing later.
I sometimes need to split a CSV into batches of rows, process them, and then recombine them. It would be convenient if the
--filenameargument allowed for{}to be zero padded to preserve file sort ordering (during shell scripting; eg., thelsordering).For example, when batching into blocks of 30 rows, I'd like to see
000.csv,030.csv, and so on. Currently, I might see0.csv,120.csv, as the ordering with30.csvappearing later.