You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed when writing to CSV files in 0.5, it changes numbers and no longer puts them in scientific notation.
In the code below, the issue is reproduced.
1.9263083035570026e-11 is displayed as 1.9263083035570026e-11, but when looking at the written file, it is written as 19263083035570026e-27. This makes written files a bit more difficult to scan through.
using DataFrames, CSV
y = collect(1.0:4.0)
x = [1.0, 0.0, 1.9263083035570026e-11, 0.5]
df = DataFrame(y = y, x = x)
CSV.write("test.csv", df)
The text was updated successfully, but these errors were encountered:
Thanks for reporting @chris-german; this changed because we're trying to use a lower-level float printing algorithm to customize the decimal point we print (',' for european locales, for example).
Luckily, I recently worked on porting/writing an entirely new (and faster!) float printing algorithm to Julia, and I'm planning on completely re-writing the CSV.write machinery under the hood to be much much faster. So sorry for the delay in responding here, and I'm sorry I don't have an immediate solution, but it's coming soon.
I've noticed when writing to CSV files in 0.5, it changes numbers and no longer puts them in scientific notation.
In the code below, the issue is reproduced.
1.9263083035570026e-11
is displayed as1.9263083035570026e-11
, but when looking at the written file, it is written as19263083035570026e-27
. This makes written files a bit more difficult to scan through.The text was updated successfully, but these errors were encountered: