Split package and development dependencies

[chpolste]

Hello @tommyod,

It would be nice to split the dependencies of this package into the ones needed to use the package (numpy, numba, pandas, as far as I can tell) and the ones used only during development (linter, docs, etc.). At the moment, pip install paretoset in a fresh environment installs almost 100 packages total, while depending only on numpy, numba and pandas would reduce the number to about 10.

I'd be happy to open a PR, but not sure how you'd prefer to implement (and then maintain) it:

1. Split the requirements.txt and link them with "-r"
2. Separate(/duplicate) list of dependencies in pyproject.toml and requirements.txt
3. ?

Thanks,
Christopher

[tommyod]

Hi @chpolste . First of all, thanks for reaching out!

I think updating requirements.txt to the more modern approach with pyproject.toml containing dependencies is a good idea. Then, in pyproject.toml we can split out optional development dependencies. See e.g. this link: https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#dependencies-and-requirements

A PR would be very welcome :)