-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Handle European decimal formats in to_csv #781
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
Comments
Need to build a low-level CSV-emitter at some point. tabling this to future release |
closed by #584, 2 years ago. |
Should this issue really be closed? If I'm not wrong, the support of "," as decimal separtor is now (=pandas 0.14) only supported in "read_csv" and not in "to_csv". DataFrame.to_csv only supports the float_format argument which does not allow to specify a particular decimal separtor. |
well float format can be a function so you can do anything u want that said this issue was closed several years ago pull requests are welcome. |
Isn't the feature request quite clear? Just to be able to specify
The linked issues which would have closed this, did not yet actually close it, as that handled about the parser, not to write. |
Indeed Joris has my point. For me the closed linked issue does not answer to the initial demand stated in this particular issue. Concerning the ability of the float_format to handle a function, it seems a little too complex. If I do a
I get
I have to do the following in order to have it working
Not very intuitive |
I can try implement this feature. Does anybody has a better proposal that just adding a:
after the application of the float_format function ? |
start with adding the keyword to the top fo the call stack: https://github.com/pydata/pandas/blob/master/pandas/core/frame.py#L1071 (then need to propogate downwards) add ulitamtely to |
I've created a pull request for this issue: #8448 It's my first contribution to pandas and first use of git: feel free to comment. |
closed by #8448 |
Add bugfix pandas-dev#777 to changelog
Counterpart to issue #584
The text was updated successfully, but these errors were encountered: