Hi *,
For this being the official tox mailing list, the responses have been
a bit sparse. We would be ok with using another tool for the job if
tox just isn't suited for this, but it would be nice if some person
involved in tox development could give us a more definite answer.
Regards,
Jonas Thiem
On Thu, Aug 28, 2014 at 12:09 PM, Jonas Thiem <jonasthiem at googlemail.com> wrote:
> Hi,
>> 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**:
>http://stackoverflow.com/questions/24411276/how-to-specify-another-tox-project-folder-as-a-dependency-for-a-tox-project>> 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)
>> Regards,
> Jonas Thiem