[Cython] any more changes for 0.21?
Hi, I think the master branch is good enough for at least a 0.21 alpha. Are there any pending changes that should go in before it can be released? Any pull requests that should be considered? We should get this in, I think: https://github.com/cython/cython/pull/284 And the gdb tests are still broken. Robert, could you take a look through the Sage test failures? Most of them might be issues in Sage rather than Cython, but it's better to make sure we can either fix or safely ignore them. Stefan ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
[Cython] JyNI - C-API emulation for Jython
Hi, it looks like there is a C-API emulation for Jython on the way: http://jyni.org/ https://github.com/Stewori/JyNI I haven't tried it yet, and I'm sure Cython modules won't work with its current state, but the effort I put into making them run in PyPy's cpyext should pay off here, so we might at some point have a third backend to target. This also reminded me of IronClad, the C-API layer for IronPython. I looked it up, but it seems to have died some years ago, with no current effort to improve it or even just make it work with the latest IronPython releases. https://groups.google.com/d/msg/c-extensions-for-ironpython/SrIesUIh1Gw/cBQG1FMt0AUJ https://code.google.com/p/ironclad/ Not sure if it's still worth trying to make that run in Cython. Stefan ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] JyNI - C-API emulation for Jython
Cool. I find their motivation "Since Java is rather present in industry, while Python is more present in science, JyNI will be an important step to lower the cost of using scientific code in industrial environments" interesting. On the other hand, I think IronClad is pretty dead. On Mon, Jun 16, 2014 at 6:58 AM, Stefan Behnel wrote: > Hi, > > it looks like there is a C-API emulation for Jython on the way: > > http://jyni.org/ > > https://github.com/Stewori/JyNI > > I haven't tried it yet, and I'm sure Cython modules won't work with its > current state, but the effort I put into making them run in PyPy's cpyext > should pay off here, so we might at some point have a third backend to target. > > This also reminded me of IronClad, the C-API layer for IronPython. I looked > it up, but it seems to have died some years ago, with no current effort to > improve it or even just make it work with the latest IronPython releases. > > https://groups.google.com/d/msg/c-extensions-for-ironpython/SrIesUIh1Gw/cBQG1FMt0AUJ > > https://code.google.com/p/ironclad/ > > Not sure if it's still worth trying to make that run in Cython. > > Stefan > ___ > cython-devel mailing list > cython-devel@python.org > https://mail.python.org/mailman/listinfo/cython-devel ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] any more changes for 0.21?
On Mon, Jun 16, 2014 at 1:07 AM, Stefan Behnel wrote: > Hi, > > I think the master branch is good enough for at least a 0.21 alpha. Are > there any pending changes that should go in before it can be released? Any > pull requests that should be considered? I started some work on support for static methods (for c++ and cdef classes). I'll see if I can wrap this up and create a pull request. > We should get this in, I think: > > https://github.com/cython/cython/pull/284 > > And the gdb tests are still broken. > > Robert, could you take a look through the Sage test failures? Most of them > might be issues in Sage rather than Cython, but it's better to make sure we > can either fix or safely ignore them. Yeah, I'll take a look at those. - Robert ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
[Cython] Cython bugfix release
I just pushed another bugfix release for the 0.20.x line, available on github, cython.org, or and pypi. == Features added == * Some optimisations for set/frozenset instantiation. * Support for C++ unordered_set and unordered_map. == Bugs fixed == * Access to attributes of optimised builtin methods (e.g. [].append.__name__) could fail to compile. * Memory leak when extension subtypes add a memory view as attribute to those of the parent type without having Python object attributes or a user provided dealloc method. * Compiler crash on readonly properties in "binding" mode. * Auto-encoding with c_string_encoding=ascii failed in Py3.3. * Crash when subtyping freelist enabled Cython extension types with Python classes that use __slots__. * Freelist usage is restricted to CPython to avoid problems with other Python implementations. * Memory leak in memory views when copying overlapping, contiguous slices. * Format checking when requesting non-contiguous buffers from cython.array objects was disabled in Py3. * C++ destructor calls in extension types could fail to compile in clang. * Buffer format validation failed for sequences of strings in structs. * Docstrings on extension type attributes in .pxd files were rejected. == Contributors == Andreas van Cranenburgh Ian Bell Lars Buitinck Martin Quarda Mikhail Korobov Robert Bradshaw Stefan Behnel ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
Re: [Cython] any more changes for 0.21?
On Mon, Jun 16, 2014 at 5:07 PM, Robert Bradshaw wrote: > On Mon, Jun 16, 2014 at 1:07 AM, Stefan Behnel wrote: >> Hi, >> >> I think the master branch is good enough for at least a 0.21 alpha. Are >> there any pending changes that should go in before it can be released? Any >> pull requests that should be considered? > > I started some work on support for static methods (for c++ and cdef > classes). I'll see if I can wrap this up and create a pull request. > >> We should get this in, I think: >> >> https://github.com/cython/cython/pull/284 >> >> And the gdb tests are still broken. >> >> Robert, could you take a look through the Sage test failures? Most of them >> might be issues in Sage rather than Cython, but it's better to make sure we >> can either fix or safely ignore them. > > Yeah, I'll take a look at those. Not all of them look benign. I'm updating Sage to the latest release and will see what's goin on. ___ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
