Many Python users use the following snippets to read Json File.

```
with oepn(filepath, 'r') as f:
    data = json.load(f)
```

I suggest providing this snippet as a function.


```
data = json.read(filepath)
```

Reading Json is very frequent task for python users. I think it is worth providing this with the High Level API.

Hi, using a file object is very common as it makes it possible to use something that is not a file, like an HTTP request or something already in memory. It makes the module serializing / de-serializing the data completely agnostic with regard to the actual physical storage which has some advantages, for example it will not raise FileNotFound.

If you want a oneliner to load data you already can use:



    with open(filepath) as f: data = json.load(f)

There was a previous issue to support filepath for json.load https://bugs.python.org/issue36378 . This just expands the json API that could already be done using one more operation.

json.load() is already a high level API. json.JSONDecoder is more low level API.

Not every two lines of code should be added as a function in the stdlib. Also, such API would be too complex because you would need to combine parameters of open() (8 parameters) and json.load() (7 parameters). If you use these two lines many times in your code you can just add a simple function that supports only options needed for you.

(Off topic) There is a very common mistake in this code:

```
with oepn(filepath, 'r') as f:
    data = json.load(f)
```

JSON file is encoded in UTF-8. But the default text encoding is locale encoding.

You should do this instead:

```
with oepn(filepath, 'rb') as f:
    data = json.load(f)
```

This works for legacy JSON with UTF-16 or UTF-32 (with/without BOM).too.