Re: Testing build

2015-05-13 Thread Cecil Westerhof
Op Wednesday 13 May 2015 17:45 CEST schreef Chris Angelico: > On Thu, May 14, 2015 at 1:18 AM, Cecil Westerhof wrote: >> With: python3 -m test -j3 I now get: Traceback (most recent call >> last): File "/usr/lib64/python3.4/runpy.py", line 170, in >> _run_module_as_main "__main__", mod_spec) File

Re: Testing build

2015-05-13 Thread Chris Angelico
On Thu, May 14, 2015 at 1:18 AM, Cecil Westerhof wrote: > With: > python3 -m test -j3 > I now get: > Traceback (most recent call last): > File "/usr/lib64/python3.4/runpy.py", line 170, in _run_module_as_main > "__main__", mod_spec) > File "/usr/lib64/python3.4/runpy.py

Re: Testing build

2015-05-13 Thread Cecil Westerhof
Op Wednesday 13 May 2015 16:12 CEST schreef Chris Angelico: > On Wed, May 13, 2015 at 11:53 PM, Cecil Westerhof wrote: >> To be clear I did not built Python yet, I used the versions >> installed on my system. (3.4.1 and 2.78) >> >> After looking at: >> https://docs.python.org/devguide/ >> >> I ex

Re: Testing build

2015-05-13 Thread Chris Angelico
On Wed, May 13, 2015 at 11:53 PM, Cecil Westerhof wrote: > To be clear I did not built Python yet, I used the versions installed > on my system. (3.4.1 and 2.78) > > After looking at: > https://docs.python.org/devguide/ > > I executed first: > python3 -m test -j3 > which gave: > a1: [6

Testing build

2015-05-13 Thread Cecil Westerhof
To be clear I did not built Python yet, I used the versions installed on my system. (3.4.1 and 2.78) After looking at: https://docs.python.org/devguide/ I executed first: python3 -m test -j3 which gave: a1: [6.435562750993995, 6.446765303000575, 6.405053696988034] a2: [4.437405036