Closed leehuwuj closed 5 days ago
Latest commit: 3f96642e67383f1d306291c8138aef80dfcb6424
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
This pull request introduces support for Python 3.13 across the project, ensuring compatibility with the latest version. Key changes include enhancements to the Dependency
interface in helpers/python.ts
, allowing for version constraints on dependencies, and updates to the supportedTools
array in helpers/tools.ts
, specifically for the DuckDuckGo search tool. Additionally, the pyproject.toml
file is modified to allow compatibility with Python 3.14 while excluding version 3.13.
File Path | Change Summary |
---|---|
.changeset/tricky-beers-bow.md | Introduced support for Python 3.13 as a patch for compatibility. |
helpers/python.ts | Updated Dependency interface to include an optional constraints property; modified getAdditionalDependencies and mergePoetryDependencies functions to handle version constraints. |
helpers/tools.ts | Updated DuckDuckGo search tool dependency version from "6.1.7" to "^6.3.5" . |
templates/types/streaming/fastapi/pyproject.toml | Changed Python version constraint from ">=3.11,<3.13" to ">=3.11,<3.14" in Poetry dependencies. |
Objective | Addressed | Explanation |
---|---|---|
Support Python 3.13 for Python template (#307) | ✅ | |
Update Python version in pyproject.toml (#307) | ✅ |
helpers/python.ts
file, which is relevant as it pertains to managing Python dependencies, aligning with the main PR's goal of supporting Python 3.13.🐇 In the garden where code does bloom,
A rabbit hops, dispelling gloom.
With Python 3.13 now in sight,
Dependencies dance, all feel right.
Version constraints, they play their part,
In the world of code, a rabbit's heart! 🐇
[!WARNING]
Rate limit exceeded
@leehuwuj has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 10 minutes and 21 seconds before requesting another review.
⌛ How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.🚦 How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://docs.coderabbit.ai/faq) for further information.📥 Commits
Reviewing files that changed from the base of the PR and between 8c3823d96c9e711ffc35a0c9fca424d1afae65b7 and 3f96642e67383f1d306291c8138aef80dfcb6424.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Fix: https://github.com/run-llama/create-llama/issues/307
Summary by CodeRabbit
New Features
Bug Fixes
Chores