On Tue, Aug 5, 2014 at 1:48 AM, Robert Bradshaw wrote:
> On Mon, Aug 4, 2014 at 4:14 PM, Ian Bell wrote:
> >
> > On Sat, Aug 2, 2014 at 7:08 PM, Robert Bradshaw
> wrote:
> >>
> >> On Sat, Aug 2, 2014 at 3:56 AM, Ian Bell wrote:
> >> > Are there any tests/docs/examples showing how to use the cp
On Mon, Aug 4, 2014 at 4:14 PM, Ian Bell wrote:
>
> On Sat, Aug 2, 2014 at 7:08 PM, Robert Bradshaw wrote:
>>
>> On Sat, Aug 2, 2014 at 3:56 AM, Ian Bell wrote:
>> > Are there any tests/docs/examples showing how to use the cpdef enum?
>> > This
>> > is a feature I have been looking for for a lon
t Bradshaw <
> rober...@gmail.com>
> >> >> wrote:
> >> >>
> >> >> > from: Robert Bradshaw
> >> >> > date: Sat, Aug 02 10:08 AM -07:00 2014
> >> >> > to: Core developer mailing list of the Cython compiler
> &
42 PM, Matthew Brett
>> > wrote:
>> >>
>> >> On Sat, Aug 02, 2014 at 10:08 AM, Robert Bradshaw
>> >> wrote:
>> >>
>> >> > from: Robert Bradshaw
>> >> > date: Sat, Aug 02 10:08 AM -07:00 2014
>> >>
t Bradshaw
> >> wrote:
> >>
> >> > from: Robert Bradshaw
> >> > date: Sat, Aug 02 10:08 AM -07:00 2014
> >> > to: Core developer mailing list of the Cython compiler
> >> >
> >> > reply-to: Core developer mailing list of
10:08 AM -07:00 2014
>> > to: Core developer mailing list of the Cython compiler
>> >
>> > reply-to: Core developer mailing list of the Cython compiler
>> >
>> > subject: Re: [Cython] Test/example for cpdef enum
>> >
>> > On Sat, Aug 2,
On Sat, Aug 2, 2014 at 7:08 PM, Robert Bradshaw wrote:
> On Sat, Aug 2, 2014 at 3:56 AM, Ian Bell wrote:
> > Are there any tests/docs/examples showing how to use the cpdef enum?
> This
> > is a feature I have been looking for for a long time and I am hoping to
> use
> > it very soon in my own p
el@python.org>
> > reply-to: Core developer mailing list of the Cython compiler <
> cython-devel@python.org>
> > subject: Re: [Cython] Test/example for cpdef enum
> >
> > On Sat, Aug 2, 2014 at 3:56 AM, Ian Bell wrote:
> >> Are there any tests/docs/exa
On Sat, Aug 02, 2014 at 10:08 AM, Robert Bradshaw wrote:
> from: Robert Bradshaw
> date: Sat, Aug 02 10:08 AM -07:00 2014
> to: Core developer mailing list of the Cython compiler
>
> reply-to: Core developer mailing list of the Cython compiler
>
> subject: Re: [Cyt
On Sat, Aug 2, 2014 at 3:56 AM, Ian Bell wrote:
> Are there any tests/docs/examples showing how to use the cpdef enum? This
> is a feature I have been looking for for a long time and I am hoping to use
> it very soon in my own project.
https://github.com/cython/cython/blob/master/tests/run/cpdef
Are there any tests/docs/examples showing how to use the cpdef enum? This
is a feature I have been looking for for a long time and I am hoping to use
it very soon in my own project.
I have a windows box that I can run the alpha test suite on with the full
complement of python versions. Let me kn
Hi,
Jenkins found a couple of test failures. I haven't looked through them yet,
but if anything looks familiar or obvious to someone, please go ahead and
fix it.
https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests/430/
Stefan
___
cython
On 23 April 2012 09:23, Stefan Behnel wrote:
> mark florisson, 22.04.2012 16:41:
>> On 22 April 2012 15:31, mark florisson wrote:
>>> I think the problem here
>>> is that a single memoryview object is traversed multiple times through
>>> different traverse functions, and that the refcount doesn't
mark florisson, 22.04.2012 16:41:
> On 22 April 2012 15:31, mark florisson wrote:
>> I think the problem here
>> is that a single memoryview object is traversed multiple times through
>> different traverse functions, and that the refcount doesn't match the
>> number of traverses. Indeed, the refcou
On 22 April 2012 15:31, mark florisson wrote:
> On 22 April 2012 13:34, Stefan Behnel wrote:
>> mark florisson, 22.04.2012 13:54:
>>> On 22 April 2012 11:57, Stefan Behnel wrote:
I keep seeing test crashes in Py3.2 debug builds on Jenkins with the latest
master, referring to ref-countin
On 22 April 2012 13:34, Stefan Behnel wrote:
> mark florisson, 22.04.2012 13:54:
>> On 22 April 2012 11:57, Stefan Behnel wrote:
>>> I keep seeing test crashes in Py3.2 debug builds on Jenkins with the latest
>>> master, referring to ref-counting problems. Here, for example:
>>>
>>> https://sage.m
mark florisson, 22.04.2012 13:54:
> On 22 April 2012 11:57, Stefan Behnel wrote:
>> I keep seeing test crashes in Py3.2 debug builds on Jenkins with the latest
>> master, referring to ref-counting problems. Here, for example:
>>
>> https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests
On 22 April 2012 11:57, Stefan Behnel wrote:
> Hi,
>
> I keep seeing test crashes in Py3.2 debug builds on Jenkins with the latest
> master, referring to ref-counting problems. Here, for example:
>
> https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests/BACKEND=c,PYVERSION=py32-ext/3
Hi,
I keep seeing test crashes in Py3.2 debug builds on Jenkins with the latest
master, referring to ref-counting problems. Here, for example:
https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests/BACKEND=c,PYVERSION=py32-ext/328/console
and likewise in the series of builds startin
___
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
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
On 13 October 2011 20:22, Stefan Behnel wrote:
> 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
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 implementation is still being
worked on. Th
2011/10/13 mark florisson :
> On 13 October 2011 12:52, mark florisson wrote:
>> On 13 October 2011 12:44, Stefan Behnel wrote:
>>> mark florisson, 13.10.2011 12:18:
On 13 October 2011 10:56, mark florisson wrote:
>
> On 13 October 2011 10:53, Vitja Makarov wrote:
>>
>>
mark florisson, 13.10.2011 13:52:
On 13 October 2011 12:44, Stefan Behnel wrote:
mark florisson, 13.10.2011 12:18:
On 13 October 2011 10:56, mark florisson wrote:
On 13 October 2011 10:53, Vitja Makarov wrote:
2011/10/13 Stefan Behnel:
Vitja Makarov, 13.10.2011 08:03:
I found that tempita b
On 13 October 2011 12:52, mark florisson wrote:
> On 13 October 2011 12:44, Stefan Behnel wrote:
>> mark florisson, 13.10.2011 12:18:
>>>
>>> On 13 October 2011 10:56, mark florisson wrote:
On 13 October 2011 10:53, Vitja Makarov wrote:
>
> 2011/10/13 Stefan Behnel:
>>
>
On 13 October 2011 12:44, Stefan Behnel wrote:
> mark florisson, 13.10.2011 12:18:
>>
>> On 13 October 2011 10:56, mark florisson wrote:
>>>
>>> On 13 October 2011 10:53, Vitja Makarov wrote:
2011/10/13 Stefan Behnel:
>
> Vitja Makarov, 13.10.2011 08:03:
>>
>> I found tha
mark florisson, 13.10.2011 12:18:
On 13 October 2011 10:56, mark florisson wrote:
On 13 October 2011 10:53, Vitja Makarov wrote:
2011/10/13 Stefan Behnel:
Vitja Makarov, 13.10.2011 08:03:
I found that tempita bug goes away if you change language_level to 2.
There's no language level config
On 13 October 2011 10:56, mark florisson wrote:
> On 13 October 2011 10:53, Vitja Makarov wrote:
>> 2011/10/13 Stefan Behnel :
>>> Vitja Makarov, 13.10.2011 08:03:
I found that tempita bug goes away if you change language_level to 2.
>>>
>>> There's no language level configured in Py2.4
On 13 October 2011 10:53, Vitja Makarov wrote:
> 2011/10/13 Stefan Behnel :
>> Vitja Makarov, 13.10.2011 08:03:
>>>
>>> I found that tempita bug goes away if you change language_level to 2.
>>
>> There's no language level configured in Py2.4, which fails.
>>
>> https://sage.math.washington.edu:809
2011/10/13 Stefan Behnel :
> Vitja Makarov, 13.10.2011 08:03:
>>
>> I found that tempita bug goes away if you change language_level to 2.
>
> There's no language level configured in Py2.4, which fails.
>
> https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests/48/BACKEND=c,PYVERSION=py
mark florisson, 13.10.2011 11:10:
On 13 October 2011 09:53, Stefan Behnel wrote:
Stefan Behnel, 13.10.2011 07:10:
mark florisson, 12.10.2011 23:46:
Is it me or are other builds broken as well?
I pushed a fix for the tempita thing, but it seems the entire py3k build
is broken:
https://sage.m
On 13 October 2011 09:53, Stefan Behnel wrote:
> Stefan Behnel, 13.10.2011 07:10:
>>
>> mark florisson, 12.10.2011 23:46:
Is it me or are other builds broken as well?
I pushed a fix for the tempita thing, but it seems the entire py3k build
is
broken:
ht
On 13 October 2011 06:10, Stefan Behnel wrote:
>
> mark florisson, 12.10.2011 23:46:
>
> On 10 October 2011 16:17, Stefan Behnel wrote:
>>
>> Jenkins currently reports several failures, and this one seems to be
>> due to your tempita changes:
>>
> https://sage.math.wash
Vitja Makarov, 13.10.2011 08:03:
I found that tempita bug goes away if you change language_level to 2.
There's no language level configured in Py2.4, which fails.
https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests/48/BACKEND=c,PYVERSION=py24/console
Stefan
___
Stefan Behnel, 13.10.2011 07:10:
mark florisson, 12.10.2011 23:46:
Is it me or are other builds broken as well?
I pushed a fix for the tempita thing, but it seems the entire py3k build is
broken:
https://sage.math.washington.edu:8091/hudson/view/All/job/cython-devel-build/54/PYVERSION=py3k/con
Robert Bradshaw, 13.10.2011 09:26:
On Wed, Oct 12, 2011 at 10:10 PM, Stefan Behnel wrote:
mark florisson, 12.10.2011 23:46:
Is it me or are other builds broken as well?
I pushed a fix for the tempita thing, but it seems the entire py3k build
is broken:
https://sage.math.washington.edu:8091/hu
On Wed, Oct 12, 2011 at 10:10 PM, Stefan Behnel wrote:
> mark florisson, 12.10.2011 23:46:
>
> On 10 October 2011 16:17, Stefan Behnel wrote:
>>
>> Jenkins currently reports several failures, and this one seems to be
>> due to your tempita changes:
>>
>
> https://sa
2011/10/13 Stefan Behnel :
> mark florisson, 12.10.2011 23:46:
>
> On 10 October 2011 16:17, Stefan Behnel wrote:
>>
>> Jenkins currently reports several failures, and this one seems to be
>> due to your tempita changes:
>>
>
> https://sage.math.washington.edu:8091/h
Stefan Behnel, 13.10.2011 07:10:
mark florisson, 12.10.2011 23:46:
Is it me or are other builds broken as well?
I pushed a fix for the tempita thing, but it seems the entire py3k build is
broken:
https://sage.math.washington.edu:8091/hudson/view/All/job/cython-devel-build/54/PYVERSION=py3k/con
mark florisson, 12.10.2011 23:46:
On 10 October 2011 16:17, Stefan Behnel wrote:
Jenkins currently reports several failures, and this one seems to be
due to your tempita changes:
https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/cython-devel-lxml-trunk/PYVERSION=py24/31/consol
On Thu, Jun 16, 2011 at 11:07 PM, Stefan Behnel wrote:
> Hi,
>
> Romain wants to start writing tests for his Python/ctypes backend branch, so
> we need to extend the test runner.
>
> We'll eventually want to merge his branch back into normal mainline, so I
> suggest actually just running the compl
Hi,
Romain wants to start writing tests for his Python/ctypes backend branch,
so we need to extend the test runner.
We'll eventually want to merge his branch back into normal mainline, so I
suggest actually just running the complete test suite in a new, separate
configuration, just like we d
On Wed, Apr 13, 2011 at 4:07 AM, mark florisson
wrote:
> Another, different but related issue: how can we get useful output
> from the test runner? e.g. I'm running my test with a
> '@cython.test_assert_path_exists("...")' and I get this error output:
>
> ==
Another, different but related issue: how can we get useful output
from the test runner? e.g. I'm running my test with a
'@cython.test_assert_path_exists("...")' and I get this error output:
==
ERROR: runTest (__main__.CythonRunTe
On Mon, Apr 11, 2011 at 3:56 AM, mark florisson
wrote:
> On 11 April 2011 12:53, mark florisson wrote:
>> On 11 April 2011 12:45, Stefan Behnel wrote:
>>> mark florisson, 11.04.2011 12:26:
Can we select tests in the tests directory selectively? I see the -T
or --ticket option, but
On 11 April 2011 12:53, mark florisson wrote:
> On 11 April 2011 12:45, Stefan Behnel wrote:
>> mark florisson, 11.04.2011 12:26:
>>>
>>> Can we select tests in the tests directory selectively? I see the -T
>>> or --ticket option, but it doens't seem to find the test tagged with #
>>> ticket:.
>>
On 11 April 2011 12:45, Stefan Behnel wrote:
> mark florisson, 11.04.2011 12:26:
>>
>> Can we select tests in the tests directory selectively? I see the -T
>> or --ticket option, but it doens't seem to find the test tagged with #
>> ticket:.
>>
>> I can select unit tests using python runtests.py
>
mark florisson, 11.04.2011 12:26:
Can we select tests in the tests directory selectively? I see the -T
or --ticket option, but it doens't seem to find the test tagged with #
ticket:.
I can select unit tests using python runtests.py
Cython.SubPackage.Tests.SomeTest, but I can't seem to do the sam
Can we select tests in the tests directory selectively? I see the -T
or --ticket option, but it doens't seem to find the test tagged with #
ticket: .
I can select unit tests using python runtests.py
Cython.SubPackage.Tests.SomeTest, but I can't seem to do the same
thing for tests in the tests dire
53 matches
Mail list logo