-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changed file opens to binary mode for to_csv calls. #521
Conversation
…serialized in isatab2json conversion
… writer to constant.py
We need a very small discussion on this matter since the functions changed were not |
@terazus Does "we" include me, or do you mean you guys? |
@ptth222 It means whoever wants to participate :) you are warmly welcome to discuss this with us. |
@terazus It can include me or not. I took "small discussion" to me like a voice communication meeting, so we would need to coordinate that if I needed to be in there. |
Fix to determining JSON directory location.
The last changes were initially tested and created on Windows, but had errors on GitHub. I fixed those errors, but didn't retest on Windows. This has been tested on both and is problem free.
Fixed parts of the code that needed to be changed to work with bytes. There are no more errors in testing.
40579e1
to
0f7b791
Compare
Closing, dupe of #547 |
When writing dataframes using the to_csv method on Windows, blank rows are inserted after every row. There is a decent Stack Overflow post about the issue here: https://stackoverflow.com/questions/56398306/using-pandas-to-write-file-creates-blank-lines. The 2 best fixes are either to open the file in binary mode or don't open the file manually and just pass the filename to the method directly. I went through the package and found instances of "to_csv" usage and changed the opening style to "wb".
I initially only encountered this problem when writing study and assay files, so I know changing to "wb" fixes the issue there, but I did not test the other instances I found.