Separate dependecies and dev-dependencies (like pytest), pyproject.toml could be an option
Make it easier to build and deploy
Several links which may be helpful
Thanks for the suggestion! Unpacking the links provided above, I think this issue proposed discussions around 2 points:
poetryWhile I strongly agree with 1. and I believe it's something feasible to do in very short term, 2. requires more changes to the whole packaging, CI and releasing process, since poetry specifically does not yet provide a native support (it seems dephell supports it) for generating setup.py which might still be useful for some of the CI/dev tools at the moment.
If I'm getting it right, is it true that currently we only support MacOS build on Travis CI? Could be a bit more helpful to add Linux/Windows builds for more sanity checks, and maybe older version builds to address confusions like #1099.
Additionally, are we considering something related to code coverage?
We do have Linux build and Windows build, but we don't have any tests cases for the CLI which is a tech debt.
FYI currently we use GitHub Actions for Linux build (#1023), AppVeyor for Windows build. We're considering to merge Windows & Mac OS X build into GitHub Actions, and purchase a self-hosted GitHub Actions runner at some point.
Additionally, are we considering something related to code coverage?
Yes, see #677, codecov.