I personally am up for nearly whatever in dev environments, as long as it's clearly documented and preferably there's some short cut for getting everything that we can hook into our primitive build system. I like to avoid things that are hard to use cross platform, but I doubt minimock falls into that category.
ASF policy allows us to have whatever we want as development dependencies; I don't think the Yetus community has taken a more restrictive stand. I think most things will come down to individual judgement. If there were two options that were otherwise equal, I'd favor those with ALv2 or compatible licenses, but that's just me. On Thu, Jan 26, 2017 at 8:46 AM, Adam Faris <[email protected]> wrote: > Greetings, > I understand one goal of Yetus is to minimize external dependencies. While > working on YETUS-460, I asked the question about referencing a non-standard > python module for unit tests (minimock). It was suggested that dependencies > for development are not restricted, but I should email the dev list so others > could chime in. > 1) What are peoples thoughts on having to 'pip install x' into their > virutalenv before starting dev work? > 2) Secondly would this create licensing issues if the module itself is being > referenced but not distributed? For example minimock is MIT licensed, which I > believe is compatible with apache v2, but what about non-compatible licensed > modules? > -- Thank you, Adam
