Jordan Cook

I haven't been able to get to this yet, but I still plan to as soon as I have the time.

Yes, this is a sensible feature request. I generally consider patching a last resort because of the [limitations mentioned here](https://requests-cache.readthedocs.io/en/stable/user_guide/general.html#patching-limitations-potential-issues), but when working with another package you don't control, you...

@meetps That's strange. I don't have a paid OpenAI account to test that out right now, but from looking over the openapi-python code, your example looks correct. This example verifies...

Back to the topic of a global `install_cache()` feature... Any suggestions for the best way to go about this? In 2023, is there a more sophisticated way to accomplish this...

It looks like the actual requests are sent by the `grafana-client` library, so I'm guessing that's why `install_cache()` is being used here. That's a convenient way to patch an external...

@amotl I looked over your changes and they look good to me. This issue could potentially be fixable with some backend settings, for example SQLite [write-ahead logging](https://sqlite.org/wal.html). This comes with...

I also just encountered this in a case where a request parameter value contains a reserved character: ```python >>> from url_normalize import url_normalize >>> url_normalize('https://www.google.com/?where=code%3D123') 'https://www.google.com/?where=code=123' ```

Good suggestions. For nested objects, it looks like you have to specify every single sub-field you want to get, otherwise it defaults to an ID only, for example: ```bash curl...

> to avoid confusion with v2 api default behavior, which does not return them That's a good point. I'll consider the wildcard/glob format. A problem with both that and my...

There are some changes in the main branch to add basic support for GET /observations v2. * currently, `fields` is just passed directly to the API * `fields='all'` will get...