2011/7/20 Robert Bradshaw :
> We're long overdue for a release, and this week would be a good one
> for me to push one out. Hudson
> https://sage.math.washington.edu:8091/hudson is looking in pretty good
> shape, and though I know we've got a big pile of stuff currently in
> progress, we've also go
On 30 July 2011 06:21, David Cournapeau wrote:
> On Sat, Jul 30, 2011 at 6:07 PM, Stefan Behnel 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
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
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.)
--
Arfreve
On Sat, Jul 30, 2011 at 7:20 AM, Dag Sverre Seljebotn
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 into the release bran
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 we're
On 30 July 2011 11:55, Vitja Makarov wrote:
> 2011/7/30 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 fou
On Sat, Jul 30, 2011 at 6:07 PM, Stefan Behnel 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 it in one p
2011/7/30 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 bey
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
impa
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 it in one place, and specifically in Cython, instead of dropping it
on the us
On Sat, Jul 30, 2011 at 5:43 PM, Stefan Behnel 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
> featur
Robert Bradshaw, 29.07.2011 20:10:
On Wed, Jul 27, 2011 at 11:32 PM, Vitja Makarov wrote:
It's fun: with cython you can use decorators, generators and more with py2.3,
may be it's better to drop support after 0.15?
I think Vitja has a point here. Cython now supports major Python language
feat
13 matches
Mail list logo
