Setup install requirements include libraries only used in utils folder

Related discussion: #195

Should we move the utils folder to its own “side” package? Not everyone will be using the parsers that we have provided, and this might result in them installing packages they don’t need along with Dash Bio.

[byronz]

just imagine the future PRs and listen to your heart

[alexcjohnson]

@mkcor asked about this on slack, in the context of the dash/dash-renderer monorepo that seems like it’s going in the opposite direction. Responding here to be more visible:

The pieces of the dash monorepo will still be separate packages on PyPI - well, mostly - @byronz and I are discussing making pytest-dash into submodule dash.testing, but dash-renderer and dash-component-system will stay separate on PyPI. We’re just moving them into a single GH repo to make development easier. The reason for this is that a large fraction of dash and dash-renderer work is coupled, meaning two cross-referenced PRs (which are hard both to develop and to review), complicated and error-prone merge strategies, and their versions are locked anyway.

Compare that to dash-core-components, dash-html-components, and dash-table, which are staying in their own repos: we do lock versions so you only get the latest versions of these only when you upgrade dash, but development tends to be mostly decoupled from dash and dash-renderer development.

If you expect there will be a lot of cross-package development between dash-bio and dash-bio-utils, the monorepo pattern can make sense but you can still split them into two PyPI packages. If you think the development will be more or less independent in the two, the separate-repo approach that you’ve built is simpler and will be easier to maintain.