Use compatible-release specifier for dependency versions

[paulf81]

Use compatible release specifiers for dependency versions

This pull request adds version specifications for the dependencies with the compatible release specifier. The change uses the latest release of each dependent version of the requirement without incrementing a major version which in semantic versioning could include breaking changes.

From the docs:

For a given release identifier V.N, the compatible release clause is approximately equivalent to the pair of comparison clauses:
>= V.N, == V.*

Some examples from the docs:

~= 2.2                     # <- this line is approximately equivalent
>= 2.2, == 2.*         # <- to this line

~= 1.4.5                   # <- this line is approximately equivalent
>= 1.4.5, == 1.4.*.    # <- to this line

More concretely, if we say numpy~=1.20, it means that FLORIS requires Numpy to be at least v1.20 and any other larger v1 is valid but not v2.

Related issue

Closes #745

Impacted areas of the software

setup.py and the dependencies chosen during installation

@kflemin

[paulf81]

ok @rafmudaf all tests passing now and I got rid of the overly picky versions, good to go?

[rafmudaf]

Can you show that you tested the "docs" extra dependencies? These are not covered by the tests unless the documentation is built, and in this case it isn't

[paulf81]

@rafmudaf , I just cloned the latest version into a clean conda environment and ran:

pip install -e ".[docs, develop]"

without conflicts

[paulf81]

And all tests pass

[rafmudaf]

Thanks for checking that. Well done fixing this!