On 9/22/19, Albert-Jan Roskam wrote:
>
> Do you think it's a deliberate design choice that decimal and thousands
> where used here as params, and not a 'locale' param? It seems nice to be
> able to specify e.g. locale='dutch' and then all the right lc_numeric,
> lc_monetary, lc_time where used. Or
On 22Sep2019 07:39, Albert-Jan Roskam wrote:
On 22 Sep 2019 04:27, Cameron Simpson wrote:
On 21Sep2019 20:42, Markos wrote:
I have a table.csv file with the following structure:
, Polyarene conc ,, mg L-1 ,,,
Spectrum, Py, Ace, Anth,
1, "0,456", "0,120", "0,168"
2, "0,456", "0,040", "0,2
On 22 Sep 2019 04:27, Cameron Simpson wrote:
On 21Sep2019 20:42, Markos wrote:
>I have a table.csv file with the following structure:
>
>, Polyarene conc ,, mg L-1 ,,,
>Spectrum, Py, Ace, Anth,
>1, "0,456", "0,120", "0,168"
>2, "0,456", "0,040", "0,280"
>3, "0,152", "0,200", "0,280"
>
>I
On 21Sep2019 20:42, Markos wrote:
I have a table.csv file with the following structure:
, Polyarene conc ,, mg L-1 ,,,
Spectrum, Py, Ace, Anth,
1, "0,456", "0,120", "0,168"
2, "0,456", "0,040", "0,280"
3, "0,152", "0,200", "0,280"
I open as dataframe with the command:
data = pd.read_csv ('
