Move requirements to pyproject.toml

[kageurufu]

Set up enough of pyproject.toml to be valid as a project

We already effectively had a minimum python version of 3.9 (due to dependencies), this merely notes that.

regenerating scripts/klippy-requirements.txt and scripts/requirements_dev.txt
can be done with
uv export -o scripts/klippy-requirements.txt --no-hashes --no-dev and
uv export -o scripts/requirements_dev.txt --no-hashes --dev-only (personally, I think we remove requirements_dev.txt soon)

Checklist

• pr title makes sense
• squashed to 1 commit
• added a test case if possible
• if new feature, added to the readme
• ci is happy and green

[PhilippMolitor]

i'd also recommend setting up a .python-version file in the root so uv automatically installs the recommended python version by itself when using uv venv: https://docs.astral.sh/uv/concepts/python-versions/#python-version-files

[kageurufu]

.python-version what would we want? I'm happy to just bless 3.13 there.

The ruff checks, that's a discussion with @rogerlz about what's going to be useful enough to be worth making merging upstream harder

[PhilippMolitor]

I'd also say 3.13 for the sake of being progressive.

As we still want to merge upstream changes, linting is an issue for sure... no easy route there.

[kageurufu]

So I think we make a discord thread for linting, I'll add .python-version, and this is good to merge. Maybe update ci-install to use uv Sent with Shortwave <https://www.shortwave.com?utm_medium=email&utm_content=signature&utm_source=ZnJhbmtseW5AdGFja2l0dC5uZXQ=> On Mon Dec 23, 2024, 04:52 PM GMT, Philipp Molitor ***@***.***> wrote: I'd also say 3.13 for the sake of being progressive. As we still want to merge upstream changes, linting is an issue for sure... no easy route there. — Reply to this email directly, view it on GitHub <#502 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB7NJ2W5SZRUMXSNZJTIZT2HA5VDAVCNFSM6AAAAABUB62STOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGAZDCNZQGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[PhilippMolitor]

also, do we want to move pyproject.toml and uv.lock to the klippy folder maybe? this way they are semantically not responsible for all of the codebase, but just klippy. this would also simplify my effort (not yet committed) to add a seperate pyproject for the docs.