- PROs:
- it’s been a lot of work, so we could keep it
- nice for testing, where we can run parallel py:cpp tests to confirm new PRs
- easier for the users to have all-in-one tuned install
- CONs
- a LOT of work for PRs, can be detering innovation, esp if you work in one language and don’t care about the other.
- very hard more complex refactoring
- less KISS
What features/structure we want to keep in the repos? Ie. how to split them into modules?
Similar arguments go for the monolitic / modular repo organization. The monolitic is more “stable”, slower to develop, ensured to work. The modular is more rapid, easier for new people to jump-in, or work only on features that one is interested.
We will see these problems in what people are currently working on: Proposal to introduce pybind for move toward Python 3 compatibility - #4 by chhenning , optimization, porting, etc…
I’ll post my proposed approach