Thanks.
I was using a virtualenv.
Just loaded everything again and all is now cleaner.
Now the not ported modules don't appear.
Just have the sslChainLoads test to look at.
Regards
John Aherne
On Sun, Mar 18, 2018 at 7:17 PM, Craig Rodrigues
wrote:
> Do not run the tests directly from t
Do not run the tests directly from the source tree.
Instead, you should install Twisted into a virtualenv
and run "trial twisted" from inside the virtualenv and outside the source
tree.
The installer has some logic to omit the installation of certain modules
and tests
which do not work on Python 3.
This is useful info for anyone else running into these issues. At least
they might save a bit of time not having to run down what is happening.
Seems that the mail,email, test_hook and StringIO errors all come from not
ported modules as seen in twisted\src\python\_setup.py.
The _getEllipticCurve
Some clarification on running the tests.
For the tests on test_sslverify
If I apply the patches from 6371 on python2.7.13 32bit windows2012R2, the
test_sslverify runs without error or failure.
TrustRootTests
test_caCertsPlatformDefaults ...
[OK]
test_caCertsWindows ...
[OK]
test_
When I run the test suite on windows I end up with the following errors and
failures - see below.
So my basic question is. Can anyone tell me what the latest state is for
running tests on windows and in particular the state of running SSL on
windows.
When I look at the buildbots status by and lar
