[TIP] Issue with larger project with subprojects; how to deal with dependencies?
yasumoto7 at gmail.com
Thu Aug 28 15:14:11 PDT 2014
Not entirely helpful (as it sidesteps your question), but if you use the
pants build tool <http://pantsbuild.github.io/>, it's very well-suited
toward a large monorepo of code. You can specify a suite of python_tests
will run all the targets that are included as dependencies.
An example is Apache Aurora <http://github.com/apache/incubator-aurora>,
the cluster scheduler used at Twitter. At the top of the repo, you can run
all the tests via:
You probably don't want to move away from tox, but I figured I'd point out
an alternative if that sounds interesting
On Thu, Aug 28, 2014 at 3:09 AM, Jonas Thiem <jonasthiem at googlemail.com>
> we got an issue with our project which is made of various subprojects,
> all of them in theory usable on their own with their own tox.ini and
> "tox" command, but in practise combined in one large repo and with
> some dependencies between them.
> The problem is, many of these subprojects simply won't work with a
> simple "tox" command unless a custom package index is in place, or
> sitepackages=True is set (which we don't want to do) with the
> dependencies installed into the system.
> That is unfortunate, since the entire point of just being able to type
> "tox" is that it just works for everyone for simple testing.
> **More details**:
> I would be happy for some responses and discussions and possibly some
> final advise on what to do, or maybe even an update to tox to allow
> relative path dependency fetches from other tox.ini-equipped folders.
> (see Stackoverflow link for details on why we think this would be a
> useful solution)
> Jonas Thiem
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python