container-pool 0.1.0__tar.gz

container_pool-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,22 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Install dependencies
+        run: pip install -e ".[openai,dev]"
+
+      - name: Run tests
+        run: pytest tests/ -v

container_pool-0.1.0/.github/workflows/claude.yml

@@ -0,0 +1,45 @@
+name: Claude Code
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  pull_request:
+    types: [opened, synchronize]
+
+permissions:
+  contents: write
+  pull-requests: write
+  issues: write
+  id-token: write
+
+jobs:
+  # Auto-review every PR when opened or updated
+  review:
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: anthropics/claude-code-action@v1
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          prompt: |
+            Review this pull request. Check for:
+            - Correctness and edge cases
+            - Consistency with the existing codebase patterns (provider-agnostic backend interface, asyncio pool mechanics)
+            - Missing or inadequate test coverage
+            - Any issues with the public API surface in __init__.py
+            Be concise. Summarize findings as inline comments and a short summary.
+          claude_args: "--max-turns 5"
+
+  # Respond to @claude mentions in issue/PR comments
+  assist:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude'))
+    runs-on: ubuntu-latest
+    steps:
+      - uses: anthropics/claude-code-action@v1
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          claude_args: "--max-turns 10"

container_pool-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,42 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Install dependencies
+        run: pip install -e ".[openai,dev]"
+
+      - name: Run tests
+        run: pytest tests/ -v
+
+  publish:
+    needs: test
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # for trusted publishing (no token needed if configured on PyPI)
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+
+      - name: Build package
+        run: |
+          pip install build
+          python -m build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

container_pool-0.1.0/.gitignore

@@ -0,0 +1,207 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# 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
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.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
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# 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
+.envrc
+.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/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/

container_pool-0.1.0/LICENSE

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

container_pool-0.1.0/PKG-INFO

@@ -0,0 +1,212 @@
+Metadata-Version: 2.4
+Name: container-pool
+Version: 0.1.0
+Summary: Provider-agnostic async container pool with expiry recovery and per-request file tracking
+Project-URL: Repository, https://github.com/aayushgzip/container-pool
+Project-URL: Issues, https://github.com/aayushgzip/container-pool/issues
+License: MIT License
+        
+        Copyright (c) 2026 aayushdwids
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+License-File: LICENSE
+Keywords: async,asyncio,code-interpreter,container,openai,pool
+Classifier: Development Status :: 4 - Beta
+Classifier: Framework :: AsyncIO
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.11
+Provides-Extra: dev
+Requires-Dist: build; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest-mock>=3.12; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: twine; extra == 'dev'
+Provides-Extra: openai
+Requires-Dist: openai>=1.0.0; extra == 'openai'
+Description-Content-Type: text/markdown
+
+# container-pool
+
+Production-grade async container pool for Python. Handles container lifecycle, reuse, concurrency, and automatic recovery from expiry — so you don't have to.
+
+Built for OpenAI's Code Interpreter, but designed to work with **any sandboxed container runtime** via a pluggable backend interface.
+
+## The Problem
+
+When running sandboxed containers behind a multi-user backend, you hit problems no provider solves for you:
+
+- **Containers expire silently** after 20 minutes of inactivity. Your next request fails with a 404.
+- **No built-in pooling.** Every request creates a new container (~2-3s overhead).
+- **No concurrency management.** Two users hitting your API simultaneously? You're on your own.
+- **File cleanup is your problem.** Leaked files accumulate and you eat the storage cost.
+
+`container-pool` is the infrastructure layer that handles all of this.
+
+## What This Does
+
+```
+Request A ──→ acquire() ──→ [Container 1] ──→ release() ──→ back to pool
+Request B ──→ acquire() ──→ [Container 2] ──→ release() ──→ back to pool
+Request C ──→ acquire() ──→ (pool full, blocks until release) ──→ ...
+```
+
+- **FIFO pool** with configurable size, blocking acquisition with timeout when exhausted
+- **Automatic expiry recovery** — detects expired containers (404, status=expired) and transparently recreates them
+- **Per-request file tracking** with cleanup, so containers stay clean between users
+- **Retry with exponential backoff** on container creation failures
+- **Graceful shutdown** that destroys all containers on exit
+- **Provider-agnostic** — implement `BaseContainerBackend` to support any runtime
+
+## Installation
+
+```bash
+pip install container-pool            # core only
+pip install "container-pool[openai]"  # with OpenAI backend
+```
+
+## Usage
+
+```python
+from openai import AsyncOpenAI
+from container_pool import ContainerPool, RequestFileTracker
+from container_pool.backends.openai import OpenAIContainerBackend
+
+client = AsyncOpenAI()
+backend = OpenAIContainerBackend(client)
+
+pool = ContainerPool(
+    backend,
+    max_pool_size=5,
+    acquire_timeout=30.0,
+    container_name="my-pool",
+)
+
+# Acquire, use, release
+container = await pool.acquire()
+try:
+    tracker = RequestFileTracker(container)
+    uploaded = await tracker.upload_file("/tmp/data.csv")
+    # ... run code interpreter with container.container_id ...
+    files = await container.list_output_files("/mnt/data/")
+    results = await container.download_files(files, "/tmp/output")
+finally:
+    await tracker.cleanup()        # delete uploaded files
+    await pool.release(container)  # return to pool
+
+# On app shutdown
+await pool.shutdown()
+```
+
+## Custom Backends
+
+Implement `BaseContainerBackend` to plug in any container runtime:
+
+```python
+from container_pool import BaseContainerBackend, ContainerInfo, UploadedFile
+
+class MyBackend(BaseContainerBackend):
+    async def create_container(self, name: str) -> ContainerInfo: ...
+    async def get_container(self, container_id: str) -> ContainerInfo: ...
+    async def destroy_container(self, container_id: str) -> None: ...
+    async def upload_file(self, container_id: str, local_path: str) -> UploadedFile: ...
+    async def download_file_content(self, container_id: str, file_id: str) -> bytes: ...
+    async def download_file_to_disk(self, container_id: str, file_id: str, local_path: str) -> int: ...
+    async def delete_file(self, container_id: str, file_id: str) -> None: ...
+    async def list_files(self, container_id: str, path_prefix: str = "") -> dict[str, str]: ...
+```
+
+## How It Works
+
+### Acquire Flow
+
+```
+acquire()
+  ├─ Queue has available container? → validate it's alive → return
+  ├─ Pool below max size? → create new container → return
+  └─ Pool exhausted? → block until someone calls release() (with timeout)
+```
+
+### Expiry Recovery
+
+`container-pool` handles silent expiry transparently — callers always get a live container:
+
+```
+validate_or_recreate(container)
+  ├─ active status → use it
+  ├─ expired status → recreate
+  ├─ 404 → recreate
+  └─ connection error → recreate
+```
+
+### Performance
+
+| Operation | Latency |
+|---|---|
+| Warm acquire | <100ms |
+| Cold acquire | ~2-3s (container creation) |
+| Pool exhausted | Blocks up to `acquire_timeout` |
+| Expiry recovery | ~2-3s (transparent recreation) |
+
+## Configuration
+
+| Parameter | Description |
+|---|---|
+| `max_pool_size` | Max containers in pool (1–50) |
+| `acquire_timeout` | Seconds to wait when pool is exhausted |
+| `container_name` | Name prefix for created containers |
+| `creation_max_attempts` | Retry attempts on creation failure (default: 3) |
+| `creation_base_delay` | Base delay for exponential backoff in seconds (default: 1.0) |
+
+## Roadmap
+
+### v1 (current)
+- [x] FIFO pool with `asyncio.Queue`
+- [x] Automatic expiry detection and recovery
+- [x] Per-request file tracking and cleanup
+- [x] Retry with exponential backoff
+- [x] Graceful shutdown
+- [x] Pluggable backend interface
+- [x] OpenAI Code Interpreter backend
+
+### v2
+- [ ] **Pool pre-warming** — create containers at startup to eliminate cold-start latency
+- [ ] **Background keep-alive** — periodic pings to prevent idle expiry
+- [ ] **Distributed state** — Redis/PostgreSQL backend for multi-node deployments
+- [ ] **Observability** — metrics for pool utilization, acquire wait times, expiry rate
+- [ ] **Pool strategies** — LRU, priority-based in addition to FIFO
+
+## Contributing
+
+Contributions welcome. Please open an issue first to discuss what you'd like to change.
+
+## Why This Exists
+
+Built after hitting every one of these problems while running Code Interpreter in a multi-user production backend. OpenAI's docs hand you a container ID and say good luck — this is the "good luck" part.
+
+— [@aayushgzip](https://github.com/aayushgzip)
+
+## License
+
+[MIT](LICENSE)