Separate user and dev requirements

[dagpunk]

Background

The current dependencies in requirements.txt are all development-related. They are not essential for using the package. Perform the following actions to improve the dependency management aspects of this template:

Plan

• Move the current contents of requirements.in and requirements.txt to dev-requirements.in and dev-requirements.txt.
• Modify some logic in the package to use a third-party package, simulating a common circumstance. Consider using pandas and/or a visualization package.
• Replace the current version of requirements.in and requirements.txt with the references to the third-party dependency used during the execution of the package.
• Modify the build/test GitHub Actions workflow to account for these changes.

References

• Example handling of separate requirements.txt and requirements.in files https://github.com/viperior/aequus/blob/056c53bdf94599a1f386529a6b66f35537358067/.github/workflows/test.yml

[dagpunk]

The -r flag can be used within requirements files.

So there can be two files:

• requirements.in
  • list of dependencies needed to run the package
• dev-requirements.in
  • -r requirements.txt
  • list of dev/test dependencies

where dev-requirements.in has an instruction to install everything in requirements.in.

Then, developers don't have to worry about installing two sets of dependencies. A developer simply uses dev-requirements.in to get both the normal dependencies but also those needed to develop and test.

[dagpunk]

This requires #90