Repository navigation
chore: add uv project metadata (issue #42, PR-A) - #418
Draft
OktavianusKokoh wants to merge 2 commits into
Draft
OktavianusKokoh wants to merge 2 commits into
OktavianusKokoh wants to merge 2 commits into
Conversation
Introduce pyproject.toml and uv.lock while keeping a pip-friendly requirements.txt. Document uv sync / uv sync --extra dev alongside pip in the README installation section. Stacked on batch base 918f5c1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part of #42 (PR-A only): add uv project metadata (
pyproject.toml+uv.lock) while keeping a pip-friendlyrequirements.txt, and documentuv sync/uv sync --extra devnext topip install -r requirements.txtin the README.Problem solved: the repo had no lockable project metadata for reproducible installs; this focused PR introduces uv without replacing the documented pip path.
Final changes
pyproject.toml— project metadata, runtime deps, optional extras (dev/webui/finetune), hatchlingpackages = ["model"]uv.lock— locked resolutionrequirements.txt— synced to pyproject pins (duplicate unpinnedpandasremoved;pandas==2.2.2kept)README.md— Installation section: pip + uvPublic API unchanged (
Kronos,KronosTokenizer,KronosPredictor).model/andtests/untouched.Acceptance criteria (PR-A) & verification
uv sync --extra devexit 0; README documents bothhuggingface_hub==0.33.1,safetensors==0.6.2unchangedCode review: PASS on candidate SHA below.
Verified commit SHA
2b08409a4432b5a96844ba18dbafac1e15ae0b86Test commands & evidence
Known limitations / human review notes
pip; useuv sync(documented) or ensure pip exists for the README pip line.ai-team/issue-42-pra-uv: chore: add uv project metadata (issue #42, PR-A) #417 — this PR supersedes that tip for the batch based on918f5c1.Test plan
uv sync --extra devpython -m pytest tests/ -q→ 4 passeduv sync --extra dev && python -m pytest tests/ -q