Skip to content

Conversation

@ibolmo
Copy link
Collaborator

@ibolmo ibolmo commented Dec 27, 2025

No description provided.

@ibolmo ibolmo self-assigned this Dec 27, 2025
@vercel
Copy link

vercel bot commented Dec 27, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
ai-proxy Ready Ready Preview, Comment Dec 29, 2025 11:27pm

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

description = "Provides Python types, Pydantic models, and helpers to extend the OpenAI client for the Braintrust proxy, improving developer experience, typechecking, and editor integration."
readme = "README.md"
requires-python = ">=3.9"
requires-python = ">=3.10"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Align uv.lock Python requirement with 3.10 change

The pyproject now requires Python ≥3.10 and the code uses PEP 604 unions, which will raise a syntax error on 3.9, but py/uv.lock still declares requires-python = " >=3.9" and even pins the project as 0.1.0. Anyone following the README and running uv sync with Python 3.9 will get a fully resolved environment that can’t import the package. Regenerate uv.lock to reflect the 3.10 floor (and the new version) so uv refuses 3.9 environments instead of letting them fail at runtime.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants