2011/10/15 Stefan Behnel :
> Vitja Makarov, 15.10.2011 11:26:
>>
>> Recent commits to the master introduced pyregr regressions. You can
>> see it here, just sort by age:
>>
>>
>> https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests-pyregr/BACKEND=c,PYVERSION=py27/33/testReport/
>
> I
Vitja Makarov, 15.10.2011 11:26:
Recent commits to the master introduced pyregr regressions. You can
see it here, just sort by age:
https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests-pyregr/BACKEND=c,PYVERSION=py27/33/testReport/
I fixed the ones I had introduced, thanks for n
Hi!
Recent commits to the master introduced pyregr regressions. You can
see it here, just sort by age:
https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests-pyregr/BACKEND=c,PYVERSION=py27/33/testReport/
Here is one example:
=
Vitja Makarov, 15.10.2011 11:07:
It's something wrong with py2.7 pyregr build "'exec' currently
requires a target mapping (globals/locals)"
is still there after you merged my exec/eval branch. I can't reproduce
it on localhost, actually it works just fine, I tried test_binop
The tests simply ha
2011/10/15 Vitja Makarov :
> 2011/10/15 Stefan Behnel :
>> Stefan Behnel, 13.10.2011 21:22:
>>>
>>> Vitja Makarov, 13.10.2011 20:33:
But py3k pyregr is no red due to SIGSEGV, is that python problem:
https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests-pyregr/
2011/10/15 Stefan Behnel :
> Stefan Behnel, 13.10.2011 21:22:
>>
>> Vitja Makarov, 13.10.2011 20:33:
>>>
>>> But py3k pyregr is no red due to SIGSEGV, is that python problem:
>>>
>>>
>>> https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests-pyregr/BACKEND=c,PYVERSION=py3k/26/console
>
Stefan Behnel, 13.10.2011 21:22:
Vitja Makarov, 13.10.2011 20:33:
But py3k pyregr is no red due to SIGSEGV, is that python problem:
https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests-pyregr/BACKEND=c,PYVERSION=py3k/26/console
Not sure, but rather likely. The PEP393 implementa
