Vitja Makarov, 05.05.2011 16:29:
2011/5/5 Stefan Behnel:
Vitja Makarov, 05.05.2011 08:41:
Recently I've found that pyregr.test_dict (test_mutatingiteration)
test makes it slow:
def test_mutatingiteration():
d = {}
d[1] = 1
for i in d:
print i
d[i+1] = 1
test_
2011/5/5 Stefan Behnel :
> Vitja Makarov, 05.05.2011 08:41:
>>
>> Recently I've found that pyregr.test_dict (test_mutatingiteration)
>> test makes it slow:
>>
>> def test_mutatingiteration():
>> d = {}
>> d[1] = 1
>> for i in d:
>> print i
>> d[i+1] = 1
>>
>> test_mutati
Vitja Makarov, 05.05.2011 08:41:
Recently I've found that pyregr.test_dict (test_mutatingiteration)
test makes it slow:
def test_mutatingiteration():
d = {}
d[1] = 1
for i in d:
print i
d[i+1] = 1
test_mutatingiteration()
In CPython this code raises: RuntimeEr
2011/4/25 Vitja Makarov :
> 2011/4/25 Stefan Behnel :
>> Vitja Makarov, 25.04.2011 11:04:
>>>
>>> 2011/4/25 Stefan Behnel:
Vitja Makarov, 25.04.2011 08:19:
>
> 2011/4/25 Stefan Behnel:
>>
>> Stefan Behnel, 07.04.2011 13:52:
>>>
>>> Stefan Behnel, 07.04.2011 13:46:
2011/4/25 Stefan Behnel :
> Vitja Makarov, 25.04.2011 11:04:
>>
>> 2011/4/25 Stefan Behnel:
>>>
>>> Vitja Makarov, 25.04.2011 08:19:
2011/4/25 Stefan Behnel:
>
> Stefan Behnel, 07.04.2011 13:52:
>>
>> Stefan Behnel, 07.04.2011 13:46:
>>>
>>> I just noticed that the
Vitja Makarov, 25.04.2011 11:04:
2011/4/25 Stefan Behnel:
Vitja Makarov, 25.04.2011 08:19:
2011/4/25 Stefan Behnel:
Stefan Behnel, 07.04.2011 13:52:
Stefan Behnel, 07.04.2011 13:46:
I just noticed that the CPython pyregr tests have jumped up from ~14
minutes for a run to ~4 hours when we
2011/4/25 Stefan Behnel :
> Vitja Makarov, 25.04.2011 08:19:
>>
>> 2011/4/25 Stefan Behnel:
>>>
>>> Stefan Behnel, 07.04.2011 13:52:
Stefan Behnel, 07.04.2011 13:46:
>
> I just noticed that the CPython pyregr tests have jumped up from ~14
> minutes for a run to ~4 hours when w
Vitja Makarov, 25.04.2011 08:19:
2011/4/25 Stefan Behnel:
Stefan Behnel, 07.04.2011 13:52:
Stefan Behnel, 07.04.2011 13:46:
I just noticed that the CPython pyregr tests have jumped up from ~14
minutes for a run to ~4 hours when we added generator support.
https://sage.math.washington.edu:8
Vitja Makarov, 25.04.2011 08:19:
2011/4/25 Stefan Behnel:
Stefan Behnel, 07.04.2011 13:52:
Stefan Behnel, 07.04.2011 13:46:
I just noticed that the CPython pyregr tests have jumped up from ~14
minutes for a run to ~4 hours when we added generator support.
https://sage.math.washington.edu:8
2011/4/25 Stefan Behnel :
> Stefan Behnel, 07.04.2011 13:52:
>>
>> Stefan Behnel, 07.04.2011 13:46:
>>>
>>> I just noticed that the CPython pyregr tests have jumped up from ~14
>>> minutes for a run to ~4 hours when we added generator support.
>>>
>>>
>>> https://sage.math.washington.edu:8091/hudso
Stefan Behnel, 07.04.2011 13:52:
Stefan Behnel, 07.04.2011 13:46:
I just noticed that the CPython pyregr tests have jumped up from ~14
minutes for a run to ~4 hours when we added generator support.
https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests-pyregr-py26-c/buildTimeTrend
Stefan Behnel, 07.04.2011 13:46:
I just noticed that the CPython pyregr tests have jumped up from ~14
minutes for a run to ~4 hours when we added generator support.
https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/cython-devel-tests-pyregr-py26-c/buildTimeTrend
I currently ha
Hi,
I just noticed that the CPython pyregr tests have jumped up from ~14
minutes for a run to ~4 hours when we added generator support.
https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/cython-devel-tests-pyregr-py26-c/buildTimeTrend
I currently have no idea why that is (well
13 matches
Mail list logo