TokenStack_top_p(self.pEngine.OStack)
-Brad
On Thu, Feb 28, 2013 at 10:38 AM, Yury V. Zaytsev wrote:
> Hi Brad,
>
> On Thu, 2013-02-28 at 08:01 -0800, Bradley M. Froehle wrote:
> >
> > cdef extern from "test.h":
> > int* foo2ptr "&foo" (
On Thu, Feb 28, 2013 at 4:58 AM, Yury V. Zaytsev wrote:
> Hi,
>
> I'm sorry if my question would appear to be trivial, but what am I
> supposed to do, if I want to wrap class methods, that return a reference
> to another class?
As a workaround you could use:
cdef extern from "test.h":
int*
.
-Brad
On Wed, Dec 19, 2012 at 10:24 PM, Stefan Behnel wrote:
> Hi Bradley,
>
> Bradley M. Froehle, 19.12.2012 21:31:
> > I was recently trying to use mpi4py in a hand-written Python 3 extension
> > module with `#define Py_LIMITED_API`.
>
> Work on getting Cython play
I've been noticing some unused function warnings of the following variety:
test.cpp:1189:12: warning: unused function
> '__pyx_pw_5numpy_7ndarray_1__getbuffer__' [-Wunused-function]
> static int __pyx_pw_5numpy_7ndarray_1__getbuffer__(PyObject *__pyx_v_self,
> Py_buffer *__pyx_v_info, int __pyx_v_
I ran `git bisect`:
d96dfdbb290d23bf3b4a186dc5b1b5d9ee7fcaa5 is the first bad commit
commit d96dfdbb290d23bf3b4a186dc5b1b5d9ee7fcaa5
Author: Mark Florisson
Date: Tue Apr 10 15:01:00 2012 +0100
Decref memoryview slice class attributes
https://github.com/cython/cython/commit/d96dfdbb290d23b
Any chance we can tag the official 0.17 release in Github as well?
-Brad
On Sun, Sep 2, 2012 at 12:40 AM, Stefan Behnel wrote:
> Robert Bradshaw, 02.09.2012 09:17:
>> On Sat, Sep 1, 2012 at 11:49 PM, Stefan Behnel wrote:
>>> Robert Bradshaw, 02.09.2012 06:05:
I know this was brought up a co
I think again this is an instance of the tests being incorrect, rather than the
code. The failing numpy_tests are all cases where we instantiate a buffer of
type 'b' (== 'signed char') but then try to use it as if it was a 'char'.
The fix, of course is to just replace most instances of 'char' w
Yes, this versioning has also impacted mpi4py which had to add some pretty ugly
code in setup.py to work around it:
https://code.google.com/p/mpi4py/source/detail?r=841e9df
-Brad
> NB I am not sure what is the status on PEP 386 [1] (not yet adopted
> afaik) but it might be worthwhile following i
