[Numpy-discussion] numpyx.pyx (recent svn) works?
Wed Apr 9 02:47:25 CDT 2008
On Wed, Apr 9, 2008 at 12:25 AM, Francesc Altet <firstname.lastname@example.org> wrote:
> I don't expect you having problems in that regard either. However, I've
> been having problems compiling perfectly valid Pyrex code with the
> Cython compiler. I just haven't had time to locate where the problem
> is and report it, but people using Pyrex and planning to migrate to
> Cython must be aware that these sort of things happen.
It would be great to have some examples of this, so we can better
understand whether they are bugs in cython or deliberate changes in
behavior. There are some of the latter, described here:
and in fact one of those already bit us in the tiny numpy/pyrex
example, as reported originally in this thread. If something more
serious arises we certainly need to know about it, but I know the
cython devs are a pretty responsive bunch, so I hope we'll have a good
chance of clean resolutions for those. Considering how pyrex has
essentially no public development process to speak of, I find it a
worrying tool to commit to for the long run, while cython is very
actively developed, which is always a bonus.
But I'm not trying to ram anything down people's throats, which is why
I didn't even want to put in the mtrand.c changes before there was
more feedback (even as a self-contained single commit). Here's the
patch that commit would contain, against current SVN, so others can
test it without putting anything into SVN itself:
I'll be happy to leave it as a new trac ticket with an attachment for
it if it will make the testing/review process easier in the long run.
More information about the Numpy-discussion