[TIP] tox environment separation docs

anatoly techtonik techtonik at gmail.com
Sat Sep 3 01:37:23 PDT 2016


Thanks. Figured out this too by experiment.

On Thu, Sep 1, 2016 at 9:07 PM, David Stanek <dstanek at dstanek.com> wrote:
> I don't know of any official docs, but I think that tox just doesn't
> change the working directory. That way commands that tox runs will run
> correctly. You should be able to find out what virtualenv you are in and
> change the file that you are trying to open.
>
> On Mon, Aug 15 at 10:21 +0300, anatoly techtonik wrote:
>> Hi,
>>
>> Where are the docs or spec that describe how tox
>> separates working directory and its virtualenv?
>>
>> https://testrun.org/tox/latest/#what-is-tox
>>
>> When I redirect output to file in this PR [1], the file
>> is created in my project root and not in virtualenv
>> working directory. So I'd like to read some spec to
>> understand what this working directory should be.
>>
>> 1. https://bitbucket.org/hpk42/tox/pull-requests/206/support-piping-command-output-to-file/diff
>>
>> --
>> anatoly t.
>>
>> _______________________________________________
>> testing-in-python mailing list
>> testing-in-python at lists.idyll.org
>> http://lists.idyll.org/listinfo/testing-in-python
>
> --
> David Stanek
> web: http://dstanek.com
> blog: http://traceback.org



-- 
anatoly t.



More information about the testing-in-python mailing list