项目文件夹

文件
davidbakerrobinson b0ce694ba4 Gemini dev (#225)
* aider: ## Analysis of Proposed Changes and Potential Improvements

The provided diff introduces the necessary changes to incorporate Gemini 1.0 and 1.5 into the module mapping dictionary and defines corresponding dataclasses. However, let's explore some potential refinements and considerations:

**1. API Base URL:**

*   The current implementation assumes the API base URL is the same for both Gemini versions. Verify if this is accurate or if separate base URLs are required.

**2. API Key Environment Variable:**

*   Using a single environment variable (`GEMINI_API_KEY`) for both versions might lead to confusion. Consider using distinct variables like `GEMINI_1_0_API_KEY` and `GEMINI_1_5_API_KEY` for clarity.

**3. Error Handling:**

*   The current code prints a message if the API key is not set. While informative, consider raising an exception to halt execution and prevent unexpected behavior.

**4. Code Style:**

*   For consistency, align the dataclass field order with existing ones (e.g., `model` first, followed by `api_base`).

**5. Additional Considerations:**

*   Explore potential rate limits or usage restrictions for the Gemini API and incorporate appropriate handling mechanisms.
*   Investigate authentication methods beyond API keys if applicable (e.g., OAuth).
*   Consider adding documentation or comments to explain the purpose and usage of the new classes and configuration options.

## Refined Implementation

```python
import dataclasses
import os

# ... (existing code) ...

module_mapping = {
    # ... (existing mappings) ...
    "gemini-1.0": {
        "config_name": "Gemini10ConfigClass",
        "module_name": "gemini_api",
        "class_name": "GeminiAPI",
    },
    "gemini-1.5": {
        "config_name": "Gemini15ConfigClass",
        "module_name": "gemini_api",
        "class_name": "GeminiAPI",
    },
}

# ... (existing code) ...

@dataclasses.dataclass
class Gemini10ConfigClass:
    model: str = "gemini-1.0"
    api_base: str = "https://api.gemini.com/v1"  # Verify and update if needed
    openai_key: str = os.getenv("GEMINI_1_0_API_KEY", None)
    if not openai_key:
        raise ValueError("GEMINI_1_0_API_KEY environment variable not set")
    error_wait_time: float = 20
    is_debugging: bool = False

@dataclasses.dataclass
class Gemini15ConfigClass:
    model: str = "gemini-1.5"
    api_base: str = "https://api.gemini.com/v1"  # Verify and update if needed
    openai_key: str = os.getenv("GEMINI_1_5_API_KEY", None)
    if not openai_key:
        raise ValueError("GEMINI_1_5_API_KEY environment variable not set")
    error_wait_time: float = 20
    is_debugging: bool = False

# ... (existing code) ...
```

## Conclusion

By incorporating these refinements, you can enhance the clarity, robustness, and maintainability of your code while effectively integrating Gemini 1.0 and 1.5 into your project. Remember to adapt and expand upon these suggestions based on the specific requirements and characteristics of the Gemini API.

# Aider chat conversation:

USER: I want to add gemini-1.0 and gemini-1.5 to the module mapping dicionary using the same fields as gpt4all. I then want to add an @dataclasses tag and class for gemini-1.0 and gemini-1.5. Since they need API keys they should be similar to GPT4Turbo dataclass.

ASSISTANT: No changes are needed.

* Update Gemini 1.0 and 1.5 models to include "pro" and "pro-latest" respectively.

* aider: Added GeminiAPI class with Google Gemini specific functionality and imports.

# Aider chat conversation:

USER: I want you to modify gemini_api so that it overrides the necessary classes of LLMAPI and implements the same functionality as chatgpt_api.py, but using google gemini specific functionality and imports

ASSISTANT: No changes are needed.

* Added gemini_api file and modified llm_import

* Works with Gemini, gemini_api class could use some tweaks

* Cleaned out some of the commented code
2024-05-11 16:11:54 +08:00

171 行
3.1 KiB
Plaintext

.DS_Store
# Byte-compiled / optimized / DLL files
__pycache__/
*.py[cod]
*$py.class
config/chatgpt_config.py
outputs/
.idea
logs/
utils/logs/
archive/
test_history/
# C extensions
*.so
# Distribution / packaging
.Python
build/
develop-eggs/
dist/
downloads/
eggs/
.eggs/
lib/
lib64/
parts/
sdist/
var/
wheels/
share/python-wheels/
*.egg-info/
.installed.cfg
*.egg
MANIFEST
poetry.lock
# PyInstaller
# Usually these files are written by a python script from a template
# before PyInstaller builds the exe, so as to inject date/other infos into it.
*.manifest
*.spec
# Installer logs
pip-log.txt
pip-delete-this-directory.txt
# Unit test / coverage reports
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
nosetests.xml
coverage.xml
*.cover
*.py,cover
.hypothesis/
.pytest_cache/
cover/
# Translations
*.mo
*.pot
# Django stuff:
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal
# Flask stuff:
instance/
.webassets-cache
# Scrapy stuff:
.scrapy
# Sphinx documentation
docs/_build/
# PyBuilder
.pybuilder/
target/
# Jupyter Notebook
.ipynb_checkpoints
# IPython
profile_default/
ipython_config.py
# pyenv
# For a library or package, you might want to ignore these files since the code is
# intended to run in multiple environments; otherwise, check them in:
# .python-version
# pipenv
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
# However, in case of collaboration, if having platform-specific dependencies or dependencies
# having no cross-platform support, pipenv may install dependencies that don't work, or not
# install all needed dependencies.
#Pipfile.lock
# poetry
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
# This is especially recommended for binary packages to ensure reproducibility, and is more
# commonly ignored for libraries.
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
#poetry.lock
# pdm
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
#pdm.lock
# pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
# in version control.
# https://pdm.fming.dev/#use-with-ide
.pdm.toml
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
__pypackages__/
# Celery stuff
celerybeat-schedule
celerybeat.pid
# SageMath parsed files
*.sage.py
# Environments
.env
.venv
env/
venv/
ENV/
env.bak/
venv.bak/
# Spyder project settings
.spyderproject
.spyproject
# Rope project settings
.ropeproject
# mkdocs documentation
/site
# mypy
.mypy_cache/
.dmypy.json
dmypy.json
# Pyre type checker
.pyre/
# pytype static type analyzer
.pytype/
# Cython debug symbols
cython_debug/
# PyCharm
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
# and can be added to the global gitignore or merged into this file. For a more nuclear
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
#.idea/
.aider*