lionagi 0.3.8__tar.gz → 0.5.0__tar.gz

lionagi-0.5.0/.env.example

@@ -0,0 +1,7 @@
+
+# model providers
+# OPENAI_API_KEY=
+# ANTHROPIC_API_KEY=
+
+# scrape youtube
+# RAPIDAPI_KEY=

lionagi-0.5.0/.github/FUNDING.yml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: [lion-agi]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

lionagi-0.5.0/.github/dependabot.yml

@@ -0,0 +1,22 @@
+version: 2
+updates:
+  # Poetry
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    allow:
+      - dependency-type: "all"
+    versioning-strategy: "lockfile-only"
+    ignore:
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
+    # As we use Poetry, we need to specify this as the package manager
+
+  # GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+# filepath: .github/dependabot.yml

lionagi-0.5.0/.github/workflows/ci.yml

@@ -0,0 +1,68 @@
+name: Continuous Integration
+
+on:
+  push:
+    branches: [ main, develop ]
+  pull_request:
+    branches: [ main, develop ]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ['3.11', '3.12', '3.13']
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v5
+      with:
+        python-version: ${{ matrix.python-version }}
+    
+    - name: Install uv
+      run: |
+        curl -LsSf https://astral.sh/uv/install.sh | sh
+        echo "$HOME/.cargo/bin" >> $GITHUB_PATH
+    
+    - name: Load cached dependencies
+      id: cached-uv-dependencies
+      uses: actions/cache@v4
+      with:
+        path: .venv
+        key: venv-${{ runner.os }}-${{ matrix.python-version }}-${{ hashFiles('pyproject.toml') }}
+    
+    - name: Install dependencies
+      if: steps.cached-uv-dependencies.outputs.cache-hit != 'true'
+      run: |
+        uv venv
+        uv build
+    
+    - name: Run tests
+      run: |
+        source .venv/bin/activate
+        uv run pytest --asyncio-mode=auto --maxfail=1 --disable-warnings tests/
+    
+    - name: Check code style and compatibility
+      run: |
+        source .venv/bin/activate
+        uv run black --check .
+        uv run isort --check-only .
+
+  publish:
+    needs: test
+    runs-on: ubuntu-latest
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+    
+    - name: Install uv
+      run: |
+        curl -LsSf https://astral.sh/uv/install.sh | sh
+        echo "$HOME/.cargo/bin" >> $GITHUB_PATH
+    
+    - name: Build package
+      run: uv build

lionagi-0.5.0/.github/workflows/codeql.yml

@@ -0,0 +1,40 @@
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ main, develop ]
+  pull_request:
+    branches: [ main, develop ]
+  schedule:
+    - cron: '0 0 * * 0'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'python' ]
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v3
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3
+
+# filepath: .github/workflows/codeql-analysis.yml

lionagi-0.5.0/.github/workflows/release.yml

@@ -0,0 +1,65 @@
+name: Release
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ['3.11', '3.12', '3.13']
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v5
+      with:
+        python-version: ${{ matrix.python-version }}
+    
+    - name: Install uv
+      run: |
+        curl -LsSf https://astral.sh/uv/install.sh | sh
+        echo "$HOME/.cargo/bin" >> $GITHUB_PATH
+    
+    - name: Install dependencies
+      run: |
+        uv venv
+        uv build
+    
+    - name: Run tests
+      run: |
+        source .venv/bin/activate
+        uv run pytest --asyncio-mode=auto --maxfail=1 --disable-warnings tests/
+
+  deploy:
+    needs: test
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+    
+    - name: Install uv
+      run: |
+        curl -LsSf https://astral.sh/uv/install.sh | sh
+        echo "$HOME/.cargo/bin" >> $GITHUB_PATH
+    
+    - name: Install dependencies
+      run: |
+        uv venv
+        uv pip install twine
+    
+    - name: Build package
+      run: uv build
+    
+    - name: Publish package to PyPI
+      env:
+        TWINE_USERNAME: __token__
+        TWINE_PASSWORD: ${{ secrets.PYPI_API_KEY }}
+      run: uv run twine upload dist/*

lionagi-0.5.0/.gitignore

@@ -0,0 +1,174 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+*.DS_Store
+dev/
+# 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
+
+# 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/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# 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/
+
+# Exclude setup.py and pyproject.toml from version control
+setup.py
+pyproject.toml
+.idea/
+.data/
+notebooks/.lock
+notebooks/meta.json
+logs/
+temp_logs/

lionagi-0.5.0/.pre-commit-config.yaml

@@ -0,0 +1,28 @@
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.5.0
+    hooks:
+    -   id: end-of-file-fixer
+    -   id: check-yaml
+    -   id: debug-statements
+    -   id: check-added-large-files
+    -   id: check-ast
+    -   id: check-json
+
+-   repo: https://github.com/psf/black
+    rev: 24.3.0
+    hooks:
+    -   id: black
+        language_version: python3
+
+-   repo: https://github.com/pycqa/isort
+    rev: 5.13.2
+    hooks:
+    -   id: isort
+        args: ["--profile", "black"]
+
+-   repo: https://github.com/asottile/pyupgrade
+    rev: v3.15.2
+    hooks:
+    -   id: pyupgrade
+        args: [--py310-plus]

lionagi-0.5.0/.python-version

@@ -0,0 +1 @@
+3.12

lionagi-0.5.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+# LionAGI Code of Conduct
+
+## A. Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as members, contributors, and leaders of the LionAGI community pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of background, identity, and personal characteristics.
+
+We commit to act and interact in ways that contribute to an inclusive, diverse, and friendly community.
+
+## B. Our Standards
+
+Examples of behavior that contribute to a positive environment include:
+
+* Demonstrating empathy and kindness toward other people.
+* Being respectful of differing opinions, viewpoints, and experiences.
+* Giving and gracefully accepting constructive feedback.
+* Accepting responsibility for our actions, apologizing to those affected by our mistakes, and learning from the experience.
+* Focusing on what is best for the community as a whole.
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind.
+* Trolling, insulting or derogatory comments, and personal or political attacks.
+* Public or private harassment.
+* Publishing others' private information, such as a physical or email address, without explicit permission.
+* Other conduct which could reasonably be considered inappropriate in a professional setting.
+
+## C. Enforcement Responsibilities
+
+Our community leaders are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct.
+
+## D. Scope
+
+This Code of Conduct applies within all community spaces, including GitHub, Discord, and various social media platforms, and also applies when an individual is officially representing the community.
+
+## E. Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team via our Discord server. All complaints will be reviewed and investigated in a manner that ensures fairness and respect for all parties.
+
+Community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## F. Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action deemed in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or behavior deemed unprofessional.
+
+**Consequence**: A private written warning from community leaders, with an explanation of why the behavior was inappropriate.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. This includes a temporary ban from community interaction if the behavior persists.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards.
+
+**Consequence**: A temporary ban from any sort of interaction within the community.
+
+### 4. Permanent Ban
+
+**Community Impact**: Sustained inappropriate behavior, harassment, or aggression toward individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## G. Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at [Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
+
+For answers to common questions about this code of conduct, see the [FAQ](https://www.contributor-covenant.org/faq).

lionagi-0.5.0/CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing to LionAGI
+
+Thank you for considering contributing to LionAGI! This document provides guidelines and instructions for contributing to this project.
+
+## Getting Started
+
+1. **Fork the Repository**: Begin by forking the repository to your GitHub account. This creates your own copy of the project where you can make changes.
+
+2. **Clone the Forked Repository**: Clone the repository to your local machine to start working on the changes.
+
+3. **Set Up Your Development Environment**: Ensure you have a suitable Python development environment. Any IDE that supports Python and package installation should be sufficient.
+
+## Making Changes
+
+1. **Creating Branches**: For new features or bug fixes, create a new branch off the main branch. Branch names should be descriptive and reflect the feature or fix you are working on.
+
+2. **Commit Messages**: Write clear and descriptive commit messages. While there’s no strict format, ensure your messages convey the purpose of the commit.
+
+## Submitting Contributions
+
+1. **Pull Requests**: Once you are ready with your changes, push your branch to your fork and open a pull request against the main repository.
+
+2. **Pull Request Description**: Provide a detailed description of the changes in your pull request. Link it to any relevant issues.
+
+3. **Code Review Process**: Your pull request will be reviewed by the project maintainers. Feedback may be provided for improvements.
+
+4. **Merging**: After approval, one of the maintainers will merge your pull request. No direct merges into the main branch are allowed without approval.
+
+## Testing
+
+1. **Writing Tests**: Include unit and integration tests for your code. Ensure your tests cover new features as well as any changes to existing functionality.
+
+2. **Running Tests Locally**: Before submitting your pull request, run all tests locally to ensure they pass.
+
+## Coding Standards
+
+1. **PEP 8**: Follow [PEP 8](https://www.python.org/dev/peps/pep-0008/) style guidelines for writing Python code.
+
+2. **PEP 257**: Adhere to [PEP 257](https://www.python.org/dev/peps/pep-0257/) for docstring conventions.
+
+3. **Linting**: Use linters to check your code against these standards.
+
+## Dependencies
+
+1. **Managing Dependencies**: Do not add or update dependencies without prior approval from the maintainers.
+
+## Documentation
+
+1. **Update Documentation**: Accompany your code changes with corresponding updates in the documentation.
+
+2. **Versioning Documentation**: Documentation should be versioned alongside the code.
+
+## Community Interaction
+
+1. **Using Discord**: Use the project’s Discord for discussions, questions, and collaboration.
+
+## Acknowledging Contributions
+
+1. **Recognition**: We value your contributions and will acknowledge significant contributions in our social media and release notes.
+
+2. **GitHub Sponsors**: We are considering setting up a GitHub Sponsor button to enable sponsorship for our contributors.
+
+## Questions?
+
+If you have any questions or need further clarification about contributing, feel free to reach out on our Discord server.
+
+Thank you for contributing to LionAGI, and we look forward to your contributions!