> On Apr 4, 2016, at 1:39 AM, John Aherne wrote:
>
> I have to specify a really long path to pick up the copy of trial.py for the
> virtualenv I am working in.
>
> I specify the virtualenv python I want to run with and then the path to
> trial.py then the test I want to run.
>
> It would app
I have to specify a really long path to pick up the copy of trial.py for
the virtualenv I am working in.
I specify the virtualenv python I want to run with and then the path to
trial.py then the test I want to run.
It would appear to be only the wincertstore module that is missed.
Perhaps I'll s
> On Apr 3, 2016, at 6:45 AM, John Aherne wrote:
>
> When I run trial in a virtualenv it seems to miss some imports and skips some
> tests.
>
> It would seem to be mainly wincertstore that it can't import.
>
> To make it work I have to include wincertstore in my main python setup and
> then
When I run trial in a virtualenv it seems to miss some imports and skips
some tests.
It would seem to be mainly wincertstore that it can't import.
To make it work I have to include wincertstore in my main python setup and
then it starts to test the wincertstore tests.
Anyone else seen this happe
