Re: [Cython] planning for 0.17

2012-07-22 Thread Stefan Behnel
mark florisson, 21.07.2012 20:48: > On 26 June 2012 21:36, Stefan Behnel wrote: >> I'd like to get an idea of what's still open for 0.17. >> >> Mark mentioned some open memoryview issues on his list and I know that >> there are still issues with PyPy, some of which could get fixed in a >> reasonabl

Re: [Cython] planning for 0.17

2012-07-21 Thread mark florisson
On 26 June 2012 21:36, Stefan Behnel wrote: > Hi, > > I'd like to get an idea of what's still open for 0.17. > > Mark mentioned some open memoryview issues on his list and I know that > there are still issues with PyPy, some of which could get fixed in a > reasonable time frame. Also, Jenkins isn'

Re: [Cython] planning for 0.17

2012-06-27 Thread Stefan Behnel
mark florisson, 27.06.2012 15:03: > On 27 June 2012 13:48, Stefan Behnel wrote: >> mark florisson, 27.06.2012 14:17: >>> That works for me, as long and array is cimported from cpython (as >>> 'array' or some other name). It will patch __Pyx_GetBuffer with a >>> typecheck and a call to its __getbuff

Re: [Cython] planning for 0.17

2012-06-27 Thread mark florisson
On 27 June 2012 13:48, Stefan Behnel wrote: > mark florisson, 27.06.2012 14:17: >> On 27 June 2012 12:59, Stefan Behnel wrote: >>> mark florisson, 27.06.2012 11:54: I can't test it right now, but I don't understand the following in the release notes (regarding array.array): "Note that on

Re: [Cython] planning for 0.17

2012-06-27 Thread Stefan Behnel
mark florisson, 27.06.2012 14:17: > On 27 June 2012 12:59, Stefan Behnel wrote: >> mark florisson, 27.06.2012 11:54: >>> I can't test it right now, but I don't understand the following in the >>> release notes (regarding array.array): "Note that only the buffer >>> syntax is supported for these arr

Re: [Cython] planning for 0.17

2012-06-27 Thread mark florisson
On 27 June 2012 12:59, Stefan Behnel wrote: > mark florisson, 27.06.2012 11:54: >> if anyone would like to pick up the  release for 0.17, I'd be much >> obliged. > > I think I can handle it. :) > Great, thanks! >> I can't test it right now, but I don't understand the following in the >> release

Re: [Cython] planning for 0.17

2012-06-27 Thread Stefan Behnel
mark florisson, 27.06.2012 11:54: > if anyone would like to pick up the release for 0.17, I'd be much > obliged. I think I can handle it. :) > I can't test it right now, but I don't understand the following in the > release notes (regarding array.array): "Note that only the buffer > syntax is s

Re: [Cython] planning for 0.17

2012-06-27 Thread mark florisson
On 26 June 2012 21:36, Stefan Behnel wrote: > Hi, > > I'd like to get an idea of what's still open for 0.17. > > Mark mentioned some open memoryview issues on his list and I know that > there are still issues with PyPy, some of which could get fixed in a > reasonable time frame. Also, Jenkins isn'

Re: [Cython] planning for 0.17

2012-06-27 Thread Vitja Makarov
2012/6/27 Stefan Behnel : > Vitja Makarov, 27.06.2012 06:29: >> I've updated T766's milstone from 0.16 to 0.17 as it didn't get into >> 0.16 release. > > Could you add it to the release notes then? > I think it's too minor change to be listed in release notes. -- vitja. _

Re: [Cython] planning for 0.17

2012-06-27 Thread Stefan Behnel
Vitja Makarov, 27.06.2012 06:29: > I've updated T766's milstone from 0.16 to 0.17 as it didn't get into > 0.16 release. Could you add it to the release notes then? Stefan ___ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailm

Re: [Cython] planning for 0.17

2012-06-26 Thread Vitja Makarov
2012/6/27 Stefan Behnel : > Hi, > > I'd like to get an idea of what's still open for 0.17. > > Mark mentioned some open memoryview issues on his list and I know that > there are still issues with PyPy, some of which could get fixed in a > reasonable time frame. Also, Jenkins isn't all that happy ye