Hello,
Was there any change with csvWrite function between 2026.0.0 and 2026.0.1 ?
I have an error message in one of our function using this function now
csvWrite: can not open file result.inp.
BR
F
Hello,
Was there any change with csvWrite function between 2026.0.0 and 2026.0.1 ?
I have an error message in one of our function using this function now
csvWrite: can not open file result.inp.
BR
F
Hello,
You may have an unexpected permission problem (check that you have write access on the path you are trying to write file). Last example of the doc runs fine with Scilab 2026.0.1 (tested on macOS and Windows):
A = [
1 0 200 %inf 0
1 1.e-300 200 %inf 0
9.99999999999990010e-001 9.99999999999999980e-201 200 3.15e300 102
9.99999999899999990e-001 1.e-100 200 296 117
1 %inf -%inf %nan 0
];
// Write into a file
filename = fullfile(TMPDIR,"foo.csv");
csvWrite(A, filename);
edit(filename)
S.
Hello S.,
Yes, this example is also working fine on my 2026.0.1.
One of our function is calling csvWrite.
Working fine with 2026.0.0
Error message with 2026.0.1
Not dramatic for us as we are (officially) still under 2025.1.0, but if we want to move to 2026.1.0 in ~May/June, we need to understand where this is coming from.
BR
F.
The latest commit that affected csvWrite was done in 2013.
S.
The function was tested on 2 other computers … no issue.
The function was again tested on the 1st computer … gone.
![]()
We will leave it as “write access” issue (temporary)
BR
F
Hello, couldn’t the file be locked in read only because of OneDrive? (or perhaps any similar application)
Just saying this because I sometimes have read only issue when opening files with my text editor (vim), and I strongly suspected onedrive, though I didn’t know how to prove it but don’t know what else it could be.
In this case, the file might be read-only, but it was very temporary : I could open it read/write a few seconds later.
Aurélien
True … Google Drive.
Maybe, some connection issues (short term)
BR
F