Metadata-Version: 2.2
Name: reclm
Version: 0.0.2
Summary: Record your llm calls and make your notebooks fast again.
Home-page: https://github.com/AnswerDotAI/reclm
Author: Tommy
Author-email: tc@answer.ai
License: Apache Software License 2.0
Keywords: nbdev jupyter notebook python
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Natural Language :: English
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: License :: OSI Approved :: Apache Software License
Requires-Python: >=3.7
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: fastcore
Requires-Dist: httpx
Requires-Dist: nbdev
Provides-Extra: dev
Requires-Dist: openai; extra == "dev"
Requires-Dist: anthropic; extra == "dev"
Dynamic: author
Dynamic: author-email
Dynamic: classifier
Dynamic: description
Dynamic: description-content-type
Dynamic: home-page
Dynamic: keywords
Dynamic: license
Dynamic: provides-extra
Dynamic: requires-dist
Dynamic: requires-python
Dynamic: summary

# reclm


<!-- WARNING: THIS FILE WAS AUTOGENERATED! DO NOT EDIT! -->

When building AI based tooling and packaging we often call LLMs while
prototyping and testing our code. A single LLM call can take 100’s of ms
to run and the output isn’t deterministic. This can really slow down
development especially if our notebook contains many LLM calls 😞.

While LLMs are new, working with external APIs in our code isn’t. Plenty
of tooling already exists that make working with APIs much easier. For
example, Python’s unittest mock object is commonly used to simulate or
mock an API call so that it returns a hardcoded response. This works
really well in the traditional Python development workflow and can make
our tests fast and predictable.

However, it doesn’t work well in the nbdev workflow where oftentimes
we’ll want to quickly run all cells in our notebook while we’re
developing our code. While we can use mocks in our test cells we don’t
want our exported code cells to be mocked. This leaves us with two
choices:

- we temporarily mock our exported code cells but undo the mocking
  before we export these cells.
- we do nothing and just live with notebooks that take a long time to
  run.

Both options are pretty terrible as they pull us out of our flow state
and slow down development 😞.

`reclm` builds on the underlying idea of mocks but adapts them to the
nbdev workflow.

## Usage

To use `reclm`

- install the package:
  `pip install git+https://github.com/AnswerDotAI/reclm.git`
- import the package `from reclm.core import enable_reclm` in each
  notebook
- add
  [`enable_reclm()`](https://AnswerDotAI.github.io/reclm/core.html#enable_reclm)
  to the top of each notebook

*Note:
[`enable_reclm`](https://AnswerDotAI.github.io/reclm/core.html#enable_reclm)
should be added after you import the OpenAI and/or Anthropic SDK.*

Every LLM call you make using OpenAI/Anthropic will now be cached in
`nbs/reclm.json`.

### Tests

`nbdev_test` will automatically read from the cache. However, if your
notebooks contain LLM calls that haven’t been cached, `nbdev_test` will
call the OpenAI/Anthropic APIs and then cache the responses.

### Cleaning the cache

It is recommended that you clean the cache before committing it.

To clean the cache, run `update_reclm_cache` from your project’s root
directory.

*Note: Your LLM request/response data is stored in your current working
directory in a file called `reclm.json`. All request headers are removed
so it is safe to include this file in your version control system
(e.g. git). In fact, it is expected that you’ll include this file in
your vcs.*
