Avoid duplicating dependencies in requirements.in AND pyproject.toml; Pyproject.toml is the future

[lord-haffi]

It is possible for pip-tools to compile the requirements.txt out of the pyproject.toml if the packaging tool is supported by the tool. Lucky us, that hatch is indeed supported by pip-tools.
Therefore, we don't need the "duplicate" requirements.in file anymore! Have fun, doing it in every repository ^^

@hf-kklein a great starter quest if you ask me :P

[hf-kklein]

good starter if pip-tools was working with python3.12 yet: jazzband/pip-tools#2021

[lord-haffi]

good starter if pip-tools was working with python3.12 yet: jazzband/pip-tools#2021

😧 Well, I'm still using Python 3.11

[hf-kklein]

just because our newbies came with 3.12 installed and i want to save them the hazzle of re-configuring their toxbase to 3.11 when 3.12 is the better option in the long run.

[hf-kklein]

@lord-haffi here's a draft: #155

can we do something similar with the dev_requirements, too? or is there no need, because we have no duplication there as we had in requirements.in vs. pyproject.toml?

[lord-haffi]

Don't know, what you want to do. I just wanted to get rid of the duplication. The dev_requirements are not listed in the pyproject.toml

[hf-kklein]

the we're done :)