Re: [Cython] Should we drop support for CPython 2.3? (and maybe even 2.4?)

2011-07-30 Thread David Cournapeau
On Sat, Jul 30, 2011 at 5:43 PM, Stefan Behnel stefan...@behnel.de wrote: This version also was the first one to use an AST for parsing (not sure if that's interesting for us), and it was the first to ship with ctypes/libffi, which keeps being considered as a future basis for certain advanced

[Cython] Vitja's CyFunction branch

2011-07-30 Thread Stefan Behnel
Hi, I wonder what we should do with Vitja's CyFunction branch. He mentioned issues with it in the past (I remember that there was one specific changeset that he considered questionable), and it seems that we found several ways to extend the function support beyond that, which may have an

Re: [Cython] Vitja's CyFunction branch

2011-07-30 Thread Vitja Makarov
2011/7/30 Stefan Behnel stefan...@behnel.de: Hi, I wonder what we should do with Vitja's CyFunction branch. He mentioned issues with it in the past (I remember that there was one specific changeset that he considered questionable), and it seems that we found several ways to extend the

Re: [Cython] Should we drop support for CPython 2.3? (and maybe even 2.4?)

2011-07-30 Thread David Cournapeau
On Sat, Jul 30, 2011 at 6:07 PM, Stefan Behnel stefan...@behnel.de wrote: David Cournapeau, 30.07.2011 10:52: Python 2.4 is still surprisingly common. Working around it for C extensions can be pretty daunting. The same applies to Cython, obviously, although I do see the advantage of doing

Re: [Cython] Vitja's CyFunction branch

2011-07-30 Thread Dag Sverre Seljebotn
My opinion is that we create a (short-lived) branch for the release, and continue development (ignoring the release) on master. If CyFunction solves no problems that blocks a release, I am -1 on merging it into the release branch. But we shouldn't keep things in pull requests just because

Re: [Cython] Vitja's CyFunction branch

2011-07-30 Thread Robert Bradshaw
On Sat, Jul 30, 2011 at 7:20 AM, Dag Sverre Seljebotn d.s.seljeb...@astro.uio.no wrote: My opinion is that we create a (short-lived) branch for the release, and continue development (ignoring the release) on master. If CyFunction solves no problems that blocks a release, I am -1 on merging it

Re: [Cython] Cython 0.15 release candidate

2011-07-30 Thread Arfrever Frehtes Taifersar Arahesis
2011-07-29 23:23:46 Dag Sverre Seljebotn napisaƂ(a): Looks very much like a numpy-on-py3 bug to me. I have reported: http://projects.scipy.org/numpy/ticket/1919 (NumPy-related tests in Cython pass with Python 3.*, when NumPy has been built with the patch from this ticket applied.) --

Re: [Cython] Vitja's CyFunction branch

2011-07-30 Thread Stefan Behnel
Robert Bradshaw, 30.07.2011 18:49: The only reason I haven't pushed a release branch is that last time I did that it kept getting the mainline development pulled into it That was just an accident on my side when I wasn't aware of the new branch you had created. Won't happen again. Just open a

Re: [Cython] Should we drop support for CPython 2.3? (and maybe even 2.4?)

2011-07-30 Thread Lisandro Dalcin
On 30 July 2011 06:21, David Cournapeau courn...@gmail.com wrote: On Sat, Jul 30, 2011 at 6:07 PM, Stefan Behnel stefan...@behnel.de wrote: David Cournapeau, 30.07.2011 10:52: Python 2.4 is still surprisingly common. Working around it for C extensions can be pretty daunting. The same