Skip to content

Commit e91e5fc

Browse files
ksoloksolo
authored
Merge pull request #8 from andrewyng/update-readme-with-base-usage-instructions
2 parents 43f8a8a + 3a64b00 commit e91e5fc

File tree

3 files changed

+306
-1
lines changed

3 files changed

+306
-1
lines changed

‎CONTRIBUTING.md

+214
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,214 @@
1+
<!-- omit in toc -->
2+
# Contributing to aimodels
3+
4+
First off, thanks for taking the time to contribute!
5+
6+
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents)
7+
for different ways to help and details about how this project handles them. Please make sure to read
8+
the relevant section before making your contribution. It will make it a lot easier for us maintainers
9+
and smooth out the experience for all involved. The community looks forward to your contributions.
10+
11+
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy
12+
> ways to support the project and show your appreciation, which we would also be very happy about:
13+
> - Star the project
14+
> - Tweet about it
15+
> - Refer this project in your project's readme
16+
> - Mention the project at local meetups and tell your friends/colleagues
17+
18+
<!-- omit in toc -->
19+
## Table of Contents
20+
21+
- [I Have a Question](#i-have-a-question)
22+
- [I Want To Contribute](#i-want-to-contribute)
23+
- [Reporting Bugs](#reporting-bugs)
24+
- [Suggesting Enhancements](#suggesting-enhancements)
25+
- [Your First Code Contribution](#your-first-code-contribution)
26+
- [Improving The Documentation](#improving-the-documentation)
27+
- [Styleguides](#styleguides)
28+
- [Commit Messages](#commit-messages)
29+
30+
31+
32+
33+
## I Have a Question
34+
35+
> If you want to ask a question, we assume that you have read the available
36+
> [Documentation](https://github.com/andrewyng/aimodels/blob/main/README.md).
37+
38+
Before you ask a question, it is best to search for existing [Issues](https://github.com/andrewyng/aimodels/issues)
39+
that might help you. In case you have found a suitable issue and still need clarification, you can write
40+
your question in this issue. It is also advisable to search the internet for answers first.
41+
42+
If you then still feel the need to ask a question and need clarification, we recommend the following:
43+
44+
- Open an [Issue](https://github.com/andrewyng/aimodels/issues/new).
45+
- Provide as much context as you can about what you're running into.
46+
- Provide project and platform versions (python, OS, etc.), depending on what seems relevant.
47+
48+
We (or someone in the community) will then take care of the issue as soon as possible.
49+
50+
51+
## I Want To Contribute
52+
53+
> ### Legal Notice <!-- omit in toc -->
54+
> When contributing to this project, you must agree that you have authored 100% of the content, that
55+
> you have the necessary rights to the content and that the content you contribute may be provided
56+
> under the project license.
57+
58+
### Reporting Bugs
59+
60+
<!-- omit in toc -->
61+
#### Before Submitting a Bug Report
62+
63+
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask
64+
you to investigate carefully, collect information and describe the issue in detail in your report. Please
65+
complete the following steps in advance to help us fix any potential bug as fast as possible.
66+
67+
- Make sure that you are using the latest version.
68+
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment
69+
components/versions (Make sure that you have read the [documentation](https://github.com/andrewyng/aimodels/blob/main/README.md).
70+
If you are looking for support, you might want to check [this section](#i-have-a-question)).
71+
- To see if other users have experienced (and potentially already solved) the same issue you are having,
72+
check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/andrewyng/aimodels?q=label%3Abug).
73+
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub
74+
community have discussed the issue.
75+
- Collect information about the bug:
76+
- Stack trace (Traceback)
77+
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
78+
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on
79+
what seems relevant.
80+
- Possibly your input and the output
81+
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
82+
83+
<!-- omit in toc -->
84+
#### How Do I Submit a Good Bug Report?
85+
86+
> You must never report security related issues, vulnerabilities or bugs including sensitive information to
87+
> the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <[email protected]>.
88+
<!-- You may add a PGP key to allow the messages to be sent encrypted as well. -->
89+
90+
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
91+
92+
- Open an [Issue](https://github.com/andrewyng/aimodels/issues/new). (Since we can't be sure at
93+
this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
94+
- Explain the behavior you would expect and the actual behavior.
95+
- Please provide as much context as possible and describe the *reproduction steps* that someone else can
96+
follow to recreate the issue on their own. This usually includes your code. For good bug reports you
97+
should isolate the problem and create a reduced test case.
98+
- Provide the information you collected in the previous section.
99+
100+
Once it's filed:
101+
102+
- The project team will label the issue accordingly.
103+
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction
104+
steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the
105+
issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
106+
- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other
107+
tags (such as `critical`), and the issue will be left to be
108+
[implemented by someone](#your-first-code-contribution).
109+
110+
Please use the issue templates provided.
111+
112+
113+
### Suggesting Enhancements
114+
115+
This section guides you through submitting an enhancement suggestion for aimodels,
116+
**including completely new features and minor improvements to existing functionality**. Following these
117+
guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
118+
119+
<!-- omit in toc -->
120+
#### Before Submitting an Enhancement
121+
122+
- Make sure that you are using the latest version.
123+
- Read the [documentation](https://github.com/andrewyng/aimodels/blob/main/README.md) carefully
124+
and find out if the functionality is already covered, maybe by an individual configuration.
125+
- Perform a [search](https://github.com/andrewyng/aimodels/issues) to see if the enhancement has
126+
already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
127+
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong
128+
case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
129+
130+
<!-- omit in toc -->
131+
#### How Do I Submit a Good Enhancement Suggestion?
132+
133+
Enhancement suggestions are tracked as [GitHub issues](https://github.com/andrewyng/aimodels/issues).
134+
135+
- Use a **clear and descriptive title** for the issue to identify the suggestion.
136+
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
137+
- **Describe the current behavior** and **explain which behavior you expected to see instead** and why.
138+
At this point you can also tell which alternatives do not work for you.
139+
- **Explain why this enhancement would be useful** to most aimodels users. You may also want to
140+
point out the other projects that solved it better and which could serve as inspiration.
141+
142+
143+
### Your First Code Contribution
144+
145+
#### Pre-requisites
146+
147+
You should first [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
148+
the `aimodels` repository and then clone your forked repository:
149+
150+
```bash
151+
git clone https://github.com/<YOUR_GITHUB_USER>/aimodels.git
152+
```
153+
154+
155+
156+
Once in the cloned repository directory, make a branch on the forked repository with your username and
157+
description of PR:
158+
```bash
159+
git checkout -B <username>/<description>
160+
```
161+
162+
Please install the development and test dependencies:
163+
```bash
164+
poetry install --with dev,test
165+
```
166+
167+
`aimodels` uses pre-commit to ensure the formatting is consistent:
168+
```bash
169+
pre-commit install
170+
```
171+
172+
**Make suggested changes**
173+
174+
Afterwards, our suite of formatting tests will run automatically before each `git commit`. You can also
175+
run these manually:
176+
```bash
177+
pre-commit run --all-files
178+
```
179+
180+
If a formatting test fails, it will fix the modified code in place and abort the `git commit`. After looking
181+
over the changes, you can `git add <modified files>` and then repeat the previous git commit command.
182+
183+
**Note**: a github workflow will check the files with the same formatter and reject the PR if it doesn't
184+
pass, so please make sure it passes locally.
185+
186+
187+
#### Testing
188+
`aimodels` tracks unit tests. Pytest is used to execute said unit tests in `tests/`:
189+
190+
```bash
191+
poetry run pytest tests
192+
```
193+
194+
If your code changes implement a new function, please make a corresponding unit test to the `test/*` files.
195+
196+
#### Contributing Workflow
197+
We actively welcome your pull requests.
198+
199+
1. Create your new branch from main in your forked repo, with your username and a name describing the work
200+
you're completing e.g. user-123/add-feature-x.
201+
2. If you've added code that should be tested, add tests. Ensure all tests pass. See the testing section
202+
for more information.
203+
3. If you've changed APIs, update the documentation.
204+
4. Make sure your code lints.
205+
206+
207+
208+
### Improving The Documentation
209+
We welcome valuable contributions in the form of new documentation or revised documentation that provide
210+
further clarity or accuracy. Each function should be clearly documented. Well-documented code is easier
211+
to review and understand/extend.
212+
213+
## Styleguides
214+
For code documentation, please follow the [Google styleguide](https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings).

‎LICENSE

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
MIT License
2+
3+
Copyright (c) 2024 Andrew Ng
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
6+
associated documentation files (the "Software"), to deal in the Software without restriction, including
7+
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
8+
copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the
9+
following conditions:
10+
11+
The above copyright notice and this permission notice shall be included in all copies or substantial
12+
portions of the Software.
13+
14+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
15+
LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
16+
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
17+
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
18+
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

‎README.md

+74-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,77 @@
11
# aimodels
2-
Simple, unified interface to multiple Generative AI providers
32

43
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
4+
5+
Simple, unified interface to multiple Generative AI providers.
6+
7+
## Installation
8+
9+
```shell
10+
pip install aimodels
11+
```
12+
13+
## Set up
14+
15+
This library provides a thin wrapper around python client libraries to interact with
16+
various Generative AI providers allowing creators to seamlessly swap out or test responses
17+
from a number of LLMs without changing their code.
18+
19+
To get started you will need the API Keys for the providers
20+
you intend to use and install the provider specific library to use.
21+
22+
The API Keys are expected to be in the host ENV and can be set manually or by using a tool such
23+
as [`python-dotenv`](https://pypi.org/project/python-dotenv/) or [`direnv`](https://direnv.net/).
24+
25+
For example if you wanted to use Antrophic's Claude 3.5 Sonnet in addition to OpenAI's ChatGPT 4o
26+
you would first need to set the API keys:
27+
28+
```shell
29+
export ANTHROPIC_API_KEY="your-anthropic-api-key"
30+
export OPENAI_API_KEY="your-openai-api-key"
31+
```
32+
33+
Install the respective client libraries:
34+
35+
```shell
36+
pip install openai anthropic
37+
```
38+
39+
In your python code:
40+
41+
```python
42+
from aimodels.client import MultiFMClient
43+
44+
models = ["openai:gpt-4o", "anthropic:claude-3-5-sonnet-20240620"]
45+
46+
client = MultiFMClient()
47+
messages = [
48+
{"role": "system", "content": "Respond in Pirate English."},
49+
{"role": "user", "content": "Tell me a joke."},
50+
]
51+
52+
for model in models:
53+
response = client.chat.completions.create(
54+
model=model,
55+
messages=messages,
56+
temperature=0.75
57+
)
58+
print(response.choices[0].message.content)
59+
60+
```
61+
62+
For more examples, check out the `examples` directory where you will find several
63+
notebooks that you can run to experiment with the interface.
64+
65+
The current list of supported providers can be found in the `aimodels.providers`
66+
package.
67+
68+
## License
69+
70+
aimodels is released under the MIT License. You are free to use, modify, and distribute
71+
the code for both commercial and non-commercial purposes.
72+
73+
## Contributing
74+
75+
If you would like to contribute, please read our [Contributing Guide](CONTRIBUTING.md)
76+
77+

0 commit comments

Comments
 (0)