[BUG] Add support for `force_ascii=False` when writing to JSON with cuDF engine
#15.211 geöffnet am 1. März 2024
Repository-Metriken
- Stars
- (6.000 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 17T 21h) (230 gemergte PRs in 30 T)
Beschreibung
Describe the bug
Ideally, we should eventually support engine="cudf" and force_ascii=False together with to_json. For now, we should update the documentation and/or provide a warning for users.
Steps/Code to reproduce bug
import cudf
df = cudf.DataFrame({"a": [1,2,3], "b": ["4","5","🌱"]})
df.to_json("test.jsonl", orient="records", lines=True, engine="cudf", force_ascii=False)
produces a TypeError: write_json() got an unexpected keyword argument 'force_ascii'.
I can do a df.to_json("test.jsonl", orient="records", lines=True, force_ascii=False) and see the emoji in the .jsonl file, and I can also do a df.to_json("test.jsonl", orient="records", lines=True, engine="cudf") and see the emoji represented as "\ud83c\udf31" in the .jsonl file. But I am unable to see the emoji represented as is in the file, while also writing with the cuDF engine.
Environment details I tested this with the latest cuDF version.