Better pyproject.toml structure

[wmalgadey]

can't you put all dependencies in your pyproject.toml? You can provide production and optional dependencies (like for testings) and use "tags" to decide what to install. Here is an example.

In your case, requests is a dependency, while responses is a dev dependency, so you'll list it below project.optional-dependencies.

If you do it, we can remove the pip install -r requirements.txt step and just pip install -e '.[all]'.

Originally posted by @palazzem in #109 (comment)

• removed requirements.txt
• added all dependencies to pyproject.toml
• make dependencies per task/job visible/installable

[inverse]

What else would you change here? The dependencies aspect seems reasonable and dev group functional.

The pylint configuration seems quite verbose but not that familiar with that toolchain.