Since the beta last month several issues have been fixed, including
the NumPy array attribute access deprecation, which are now rewritten
to use the NumPy macros. Another serious bug in the reversed(range())
optimization was disabled, a C compiler bug on OS X Lion in OpenMP
code was circumvented, the documentation for fused types has been
improved, some bugs related to fused C++ and buffers types have been
fixed, and nogil was added to the included STL declarations.
I encourage everyone to give it a try, see if your project still
compiles and works, and if it doesn't to take up those torches and
pitchforks from your desks, you know where to find us.
Enjoy!
Here is a pitchfork:
https://gist.github.com/2268824
This is a crash report when trying to cython-ify scikit-learn master
with both master and the 0.16rc0 tag of the cython repo.
Best,
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
This may be related to this issue:
https://github.com/cython/cython/commit/3dc1d68b6ccf437df0bce0bd18bf1862ff49a440
It's better to cherry-pick this commit.
--
vitja.
I'm wrong. Mark already fixed this: 1eabb1c63c72ce6b4b0abc6082468b9c1ab37c41
--
vitja.
We are happy to announce the first release candidate for Cython 0.16,
you can grab it from here: http://wiki.cython.org/ReleaseNotes-0.16
...
I encourage everyone to give it a try, see if your project still
compiles and works, and if it doesn't to take up those torches and
pitchforks from your desks, you know where to find us.
Thanks for the report. I'm getting a 404 on the URL above when I open it in
my browser - didn't try the checkout yet. In any case, could you paste the
exact error message that Cython gives you, including the name and line
number of the source file that you are compiling?
Stefan
Thanks for the report. I'm getting a 404 on the URL above when I open it in> Hello. I have code that builds with 0.15.1, but fails with "Cannot convert
> 'PyObject *' to Python object" using 0.16rc0. My system is x86_64 Fedora
> 14 if that matters. To reproduce the problem:
>
> svn checkout http://pynastran.googlecode.com/svn/trunk/pyNastran/op4pynastran-read-only
my browser - didn't try the checkout yet. In any case, could you paste the
exact error message that Cython gives you, including the name and line
number of the source file that you are compiling?
So with new memoryview support, is it true that I can write algorithms in
cython, that accept non-contiguous numpy array slices (from python), and can
operate on them with (reasonable) efficiency? IIRC, that was not true with
previous cython numpy support.
Here is small example to trigger the issue:
cimport numpy as np
cdef np.ndarray[np.uint32_t, ndim=1] bar():
pass
def foo(shape):
return bar().size
This bug was introduced by 95b6e693327650607c6f5b1fffc5c9867dce0645,
"Stopgap support for numpy 1.7"
I'm sure we must fix it before the release.
--
vitja.
Sorry to say that, but seeing how many bugs they introduced, those changes
have seriously degraded the stability of the release branch.
Stefan
Yeah.
Little note: after merging release branch back to master my and Mark's
fixes are now both there:
https://github.com/cython/cython/blob/master/Cython/Compiler/ParseTreeTransforms.py#L1791
I think we must remove one of the self.visitchilden(node) lines.
--
vitja.
Fortunately the fixes are also rather trivial.
Yeah, I hadn't noticed the fix in your branch when fixing that commit.
I finally got some free time, so I'll be fixing some remaining issue
and try to push out a new release candidate somewhere tomorrow or the
day after.
> --
> vitja.