running the project with uv

[wasserrutschentester]

uv is a package manager and runner from the same team as ruff

this pr adds the dependencies from requirements.txt to the pyproject.toml, so one can just start using it with uv run upload.py without needing to manually set up the virtual environment or install the dependencies (everything is automatically done on the first run with uv)

additionally the uv.lock file is used to pin to even more explicit versions.

Summary by CodeRabbit

• Chores
  • Updated project configuration with build metadata, linting tool settings, and type checking configuration.
  • Established explicit version pinning for all project dependencies.

[coderabbitai]

📝 Walkthrough

Walkthrough

Added Python project metadata, dependencies, and tooling configurations to pyproject.toml. Includes project name/version specifications, 59 new dependency pinnings, ruff linter rules with isort import sorting configuration, and pyright type checker settings with strict mode enabled.

Changes

Cohort / File(s)	Summary
Project Configuration pyproject.toml	Added [project] section with metadata (name, version, description, readme, requires-python). Added [tool.ruff], [tool.ruff.lint], [tool.ruff.lint.isort] for linter and import sorting configuration. Added [tool.pyright] with strict type checking, Python version targeting, and diagnostic report settings. Pinned 59+ package dependencies.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Configuration commits with care,
Dependencies listed fair,
Ruff rules aligned just right,
Pyright watching strict and tight!
Tools and settings, all in place—
Our project hops with style and grace! 🎯

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'running the project with uv' is directly related to the main objective of the PR, which is to add support for running the project with uv by configuring pyproject.toml with dependencies and tool settings.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

pyproject.toml (1)

1-6: Missing [build-system] table.

For a fully compliant pyproject.toml (PEP 517/518), a [build-system] section is expected. While uv run may work without it, adding one ensures compatibility with pip install . and other standard tooling.

Suggested addition at the top of the file

+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
 [project]
 name = "upload-assistant"

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}