Fresh setup

[antoinejeannot]

Hi 👋
This PR attempts to clean things a bit concerning the dev, CI and releases workflows.

It tries to stay ISO-functional while adding some niceties:

• use pre-commit hooks
• add a Makefile with some recipes
• get rid of the ./scripts/ sub-folder and re-use the Makefile
• get rid of the setup.* and most requirements files, migrating to a pyproject.toml and one requirements-dev.txt (some background on why: http://blog.chrisgorgolewski.org/2017/12/to-pin-or-not-to-pin-dependencies.html)
• adapt github workflows with these new utilities

While working on this PR, several issues have been encountered but not yet solved:

• some FIXME & TODO have been added at appropriate places (mostly for cool pre-commit hooks that fix too many things for one PR)
• tensorflow's dependencies policy (with strict higher-bounds) prevents us from having one [dev] optional (hence the need to properly install tensorflow via a side-step in the nox session)
• the docs issue has not been handled yet, fortunately a next PR will
• tests depending on optionals (assets-X, tensorflow etc) are only carried out on Ubuntu. While it does not seem right at first glance (except to gain some CI time ofc), it has already led to some issues such as the just merged Add get_keras_model to TensorflowModel #187 which did not build on ubuntu but passed everywhere else, which left a peer in disarray.

Looking forward to your feedback on this one,
Feel free to review it commit by commit, as I tried to split the work as much as possible 🙏

[tbascoul]

I would argue against keeping the requirements-dev.txt
I understand the reproducibility aspect of it, but what is most likely to happen is that we will forget about it and end up running the CI on deprecated packages.
As you are already familiar with filelock project 😄 , here is an example of a setup with only a pyproject file: https://github.com/tox-dev/filelock/blob/c1163ae57128cb398a70c3dce3bfd816fc3599f0/pyproject.toml#L46
I find it better to have a minimum version requirement in pyproject optional dependencies.
It might break sometimes but at least you are keeping up to date with other packages.

Edit: after digging a bit more, the method used in httpx project might be the one I prefer: https://github.com/encode/httpx/blob/master/requirements.txt#L1-L5
Pinned requirements for the testing/doc/packaging part, non-pinned for all other packages.

[antoinejeannot]

I would argue against keeping the requirements-dev.txt I understand the reproducibility aspect of it, but what is most likely to happen is that we will forget about it and end up running the CI on deprecated packages. As you are already familiar with filelock project 😄 , here is an example of a setup with only a pyproject file: https://github.com/tox-dev/filelock/blob/c1163ae57128cb398a70c3dce3bfd816fc3599f0/pyproject.toml#L46 I find it better to have a minimum version requirement in pyproject optional dependencies. It might break sometimes but at least you are keeping up to date with other packages.

Edit: after digging a bit more, the method used in httpx project might be the one I prefer: https://github.com/encode/httpx/blob/master/requirements.txt#L1-L5 Pinned requirements for the testing/doc/packaging part, non-pinned for all other packages.

Totally fair point. As discussed on the side, I was tempted to drop the requirements-dev.txt file as well before reconsidering it to avoid too much change in the CI / dev workflow.

That said, I 💯 agree with the deprecation of the requirements-dev.txt, in favor of a test-requirements.txt with tests,docs,packaging dependencies hard-pinned.

[antoinejeannot]

PTAL @tbascoul