ENH: Deprecate literal json string input to `read_json`

[wence-]

Feature Type

• Adding new functionality to pandas

• Changing existing functionality in pandas

• Removing existing functionality in pandas

Problem Description

As seen in #29102 (the rejected #29104), and then #46718, determining user intent in user input from pd.read_json(some_string) is in general not possible. #46718 is a halfway house in that it explicitly marks some "file extensions" as "you probably wanted to read from a file", but is easily defeated by, for example pd.read_json("missing.jsonl", lines=True) (jsonl being a common extension for "lines"-formatted json files).

AFAICT, read_json is the only read_XXX function that accepts a literal representation of the data in its path_or_buf argument, so there doesn't seem to be a great deal of precedent here.

Feature Description

Deprecate literal json input to pd.read_json, if one wants to read from a string it should be wrapped in a StringIO.

e.g.

import pandas as pd
from io import StringIO
data = '{"a":{"0":1}}'
# old, proposed for deprecation
df = pd.read_json(data)
# new
df = pd.read_json(StringIO(data))

Alternative Solutions

None

Additional Context

No response

[mroeschke]

Agreed that being stricter here by only accepting a "file like object" is reasonable

[jbrockmendel]

xref #5924 can be closed as "no" if/when we restrict this consistently

[wence-]

Thanks for that cross-ref, to broaden the scope, here's an audit of the current state of play:

• read_clipboard: doesn't take input argument
• read_csv: pathlike, BinaryIO, StringIO
• read_excel: pathlike, BinaryIO, engine-specific objects, literal bytes
• read_feather: pathlike, BinaryIO
• read_fwf: pathlike, BinaryIO, StringIO
• read_gbq: SQL query (str)
• read_hdf: pathlike, pytables.HDFStore
• read_html: pathlike, BinaryIO, StringIO, literal bytes, literal string
• read_json: pathlike, BinaryIO, StringIO, literal string
• read_orc: pathlike, BinaryIO
• read_parquet: pathlike, BinaryIO
• read_pickle: pathlike, BinaryIO
• read_sas: pathlike, BinaryIO
• read_spss: pathlike (pyreadstat doesn't allow reading from a buffer)
• read_sql_query: SQL query (str)
• read_sql_table: name of database table (str)
• read_stata: pathlike, BinaryIO
• read_table: pathlike, BinaryIO, StringIO
• read_xml: pathlike, BinaryIO, StringIO, literal bytes, literal string

So some, but not all, of the textual formats support reading literally, some support reading bytes as well as strings, and some of the binary formats support reading literal bytes.

If deprecating literal input to read_json I would suggest it makes sense to therefore also do so for:

• read_excel
• read_html
• read_xml

I see in the past there's been some discussion about introducing utility reads_XXX functions to provide a slightly slicker experience for reading from literals than read_XXX(StringIO(foo)). I can introduce those as well with the deprecation if that is still considered a good idea.

[mroeschke]

If deprecating literal input to read_json I would suggest it makes sense to therefore also do so for:

Yeah makes sense to have API consistency among the other read functions too

I can introduce those as well with the deprecation if that is still considered a good idea.

I would opt for not introducing those methods personally

[rmhowe425]

take

[rmhowe425]

@mroeschke Do you think it would make sense to change the name of the path_or_buf parameter for read_json() to something more appropriate such as obj_or_buf?

I feel like path_or_buf insinuates that you can pass a string-type argument that represents a file path.