lionagi 0.10.6__tar.gz → 0.10.7__tar.gz

lionagi-0.10.7/.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.10", "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.10.7/.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.10.6 → lionagi-0.10.7}/.github/workflows/docs.yml

@@ -2,7 +2,7 @@ name: Build and Deploy Docs
 
 on:
   push:
-    branches: [ "main" ]
+    branches: ["main"]
 
 jobs:
   build-deploy:

lionagi-0.10.7/.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.10", "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.10.6 → lionagi-0.10.7}/.gitignore

@@ -172,3 +172,5 @@ notebooks/.lock
 notebooks/meta.json
 logs/
 temp_logs/
+
+scripts/

lionagi-0.10.7/.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.10.7/CODE_OF_CONDUCT.md

@@ -0,0 +1,104 @@
+# 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.10.6 → lionagi-0.10.7}/CONTRIBUTING.md

@@ -1,67 +1,94 @@
 # Contributing to LionAGI
 
-Thank you for considering contributing to LionAGI! This document provides guidelines and instructions for contributing to this project.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+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.
+1. **Update Documentation**: Accompany your code changes with corresponding
+   updates in the documentation.
 
-2. **Versioning Documentation**: Documentation should be versioned alongside the code.
+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.
+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.
+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.
+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.
+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!
+Thank you for contributing to LionAGI, and we look forward to your
+contributions!

{lionagi-0.10.6 → lionagi-0.10.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lionagi
-Version: 0.10.6
+Version: 0.10.7
 Summary: An Intelligence Operating System.
 Author-email: HaiyangLi <quantocean.li@gmail.com>
 License:            Apache License
@@ -241,21 +241,28 @@ Description-Content-Type: text/markdown
 ![PyPI - Downloads](https://img.shields.io/pypi/dm/lionagi?color=blue)
 ![Python Version](https://img.shields.io/badge/python-3.10%2B-blue)
 
-[Documentation](https://lion-agi.github.io/lionagi/) | [Discord](https://discord.gg/aqSJ2v46vu) | [PyPI](https://pypi.org/project/lionagi/) | [Roadmap](https://trello.com/b/3seomsrI/lionagi)
+[Documentation](https://lion-agi.github.io/lionagi/) |
+[Discord](https://discord.gg/aqSJ2v46vu) |
+[PyPI](https://pypi.org/project/lionagi/) |
+[Roadmap](https://trello.com/b/3seomsrI/lionagi)
 
 # LION - Language InterOperable Network
 
 ## An Intelligence Operating System
 
-LionAGI is a robust framework for orchestrating multi-step AI operations with precise control. Bring together multiple models, advanced ReAct reasoning, tool integrations, and custom validations in a single coherent pipeline.
+LionAGI is a robust framework for orchestrating multi-step AI operations with
+precise control. Bring together multiple models, advanced ReAct reasoning, tool
+integrations, and custom validations in a single coherent pipeline.
 
 ## Why LionAGI?
 
 - **Structured**: LLM interactions are validated and typed (via Pydantic).
-- **Expandable**: Integrate multiple providers (OpenAI, Anthropic, Perplexity, custom) with minimal friction.
-- **Controlled**: Built-in safety checks, concurrency strategies, and advanced multi-step flows—like ReAct with verbose outputs.
-- **Transparent**: Real-time logging, message introspection, and easy debugging of tool usage.
-
+- **Expandable**: Integrate multiple providers (OpenAI, Anthropic, Perplexity,
+  custom) with minimal friction.
+- **Controlled**: Built-in safety checks, concurrency strategies, and advanced
+  multi-step flows—like ReAct with verbose outputs.
+- **Transparent**: Real-time logging, message introspection, and easy debugging
+  of tool usage.
 
 ## Installation
 
@@ -263,17 +270,11 @@ LionAGI is a robust framework for orchestrating multi-step AI operations with pr
 pip install lionagi
 ```
 
-Dependencies:
-	•	aiocahce
-  •	aiohttp
-	•	jinja2
-	•	pandas
-	•	pillow
-  •	pydantic
-	•	python-dotenv
-  •	tiktoken
+Dependencies: •	aiocahce •	aiohttp •	jinja2 •	pandas •	pillow •	pydantic
+•	python-dotenv •	tiktoken
 
 ## Quick Start
+
 ```python
 from lionagi import Branch, iModel
 
@@ -294,6 +295,7 @@ print(response)
 ```
 You claim to be a dragon, oh what a braggin'!
 ```
+
 ### Structured Responses
 
 Use Pydantic to keep outputs structured:
@@ -311,6 +313,7 @@ res = await hunter.communicate(
 print(type(response))
 print(response.joke)
 ```
+
 ```
 <class '__main__.Joke'>
 With fiery claws, dragons hide their laughter flaws!
@@ -318,7 +321,8 @@ With fiery claws, dragons hide their laughter flaws!
 
 ### ReAct and Tools
 
-LionAGI supports advanced multi-step reasoning with ReAct. Tools let the LLM invoke external actions:
+LionAGI supports advanced multi-step reasoning with ReAct. Tools let the LLM
+invoke external actions:
 
 ```python
 from lionagi.tools.types import ReaderTool
@@ -336,16 +340,21 @@ result = await branch.ReAct(
 print(result)
 ```
 
-The LLM can now open the PDF, read in slices, fetch references, and produce a final structured summary.
+The LLM can now open the PDF, read in slices, fetch references, and produce a
+final structured summary.
 
 ### Observability & Debugging
+
 - Inspect messages:
+
 ```python
 df = branch.to_df()
 print(df.tail())
 ```
+
 - Action logs show each tool call, arguments, and outcomes.
-- Verbose ReAct provides chain-of-thought analysis (helpful for debugging multi-step flows).
+- Verbose ReAct provides chain-of-thought analysis (helpful for debugging
+  multi-step flows).
 
 ### Example: Multi-Model Orchestration
 
@@ -377,10 +386,12 @@ pip install "lionagi[ollama]"
 ## Community & Contributing
 
 We welcome issues, ideas, and pull requests:
+
 - Discord: Join to chat or get help
 - Issues / PRs: GitHub
 
 ### Citation
+
 ```
 @software{Li_LionAGI_2023,
   author = {Haiyang Li},
@@ -392,4 +403,6 @@ We welcome issues, ideas, and pull requests:
 ```
 
 **🦁 LionAGI**
-> Because real AI orchestration demands more than a single prompt. Try it out and discover the next evolution in structured, multi-model, safe AI.
+
+> Because real AI orchestration demands more than a single prompt. Try it out
+> and discover the next evolution in structured, multi-model, safe AI.