Re: Test changing the backend / export - import

On Thu, Nov 04, 2021 at 10:33:42AM +0000, SCHLEMMER Norbert wrote:
> The problem seems to be the "empty lines" of the *.csv files.
> 
> Have done an export of TurnKey Roundup, added CRs to issue.csv and the
> error is reproducible
> 
> How can we change the export function of our Roundup under Windows to
> avoid these lines ?
> 
> Please find attached status.csv as example

There are no empty lines. Every line in your status.csv is terminated by
*two* carriage returns and *one* linefeed. This is a variant of
Microsoft windows newline conventions with another carriage return. I
don't know where the additional CR comes from. So I guess the
export/import should use the 'universal newline' feature of python to be
able to read exports from windows. I guess nobody has ever tested if
cross-platform export/import works. The additional carriage return is
probably ignored when evaluating the last column (which always contains
the 'is retired' flag in all exports I've seen over the years).

I consider this a bug that cross-platform imports do not work.

@Norbert, can you create an issue with the status.csv attached on
roundups issue-tracker at https://issues.roundup-tracker.org/ ?
I think you might need to register before being able to create an issue.

To make this work for you with versions of roundup where the bug is not
yet fixed you may want to pass all .csv files of your export through
some DOS2UNIX utility. Alternatively you can do it on linux with:

sed -i -e 's/\r//g' *.csv

Thanks
Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]