This PR fixes two minor problems that were introduced in #32 when switching from setup.py to pyproject.toml:
The runtime dependencies of the module had also become build dependencies. This behavior was not intended, and was caused by the dynamic lookup of the module version in pyproject.toml, that was requiring to install the module at build-time. It was fixed by making the project version a static field of pyproject.toml (25f8430e).
The editable install (python -m pip install -e .) was broken on Windows (still working on Linux, curiously). It was due to an incorrect combination of settings in the section of pyproject.toml managing setuptools options. It was fixed by editing the broken fields to a correct syntax (5dfec3e3).
This PR fixes two minor problems that were introduced in #32 when switching from
setup.pytopyproject.toml:pyproject.toml, that was requiring to install the module at build-time. It was fixed by making the project version a static field ofpyproject.toml(25f8430e).python -m pip install -e .) was broken on Windows (still working on Linux, curiously). It was due to an incorrect combination of settings in the section ofpyproject.tomlmanaging setuptools options. It was fixed by editing the broken fields to a correct syntax (5dfec3e3).