To save us having to change packages in multiple places, I've made requirements.txt the main source which is then read in setup.py. This is also done for test requirements (requirements-test.txt) and dev requirements (requirements-dev.txt - currently this is doc generation related but if we add specific dev tools later e.g. profiling then it will be added here). I've also dropped unsupported Python versions from setup.py.
I've removed environment.yml. If conda is desired the packages can be installed via conda install --file requirements.txt. This seems to be the simplest solution. The alternative is to manually maintain an environment.yml file, or have a script that parses requirements.txt and creates it.
To save us having to change packages in multiple places, I've made requirements.txt the main source which is then read in setup.py. This is also done for test requirements (requirements-test.txt) and dev requirements (requirements-dev.txt - currently this is doc generation related but if we add specific dev tools later e.g. profiling then it will be added here). I've also dropped unsupported Python versions from setup.py.
I've removed environment.yml. If conda is desired the packages can be installed via
conda install --file requirements.txt. This seems to be the simplest solution. The alternative is to manually maintain an environment.yml file, or have a script that parses requirements.txt and creates it.