On Sun, 2013-06-09 at 12:23 +0100, David Cournapeau wrote:
> On Sun, Jun 9, 2013 at 8:35 AM, Henry Gomersall
> wrote:
> > On Sat, 2013-06-08 at 14:35 +0200, Anne Archibald wrote:
> >> Looking at the rational module, I think you're right: it really
> >> shouldn't be too hard to get quads working as
On 09.06.2013 12:10, josef.p...@gmail.com wrote:
> On Wed, May 29, 2013 at 3:19 PM, wrote:
>> On Wed, May 29, 2013 at 12:25 PM, Julian Taylor
>> wrote:
>>> On 05/29/2013 06:12 AM, josef.p...@gmail.com wrote:
On Tue, May 28, 2013 at 6:31 PM, Charles R Harris
wrote:
>
> Hi
On Sun, Jun 9, 2013 at 8:35 AM, Henry Gomersall wrote:
> On Sat, 2013-06-08 at 14:35 +0200, Anne Archibald wrote:
>> Looking at the rational module, I think you're right: it really
>> shouldn't be too hard to get quads working as a user type using gcc's
>> __float128 type, which will provide hardw
On Wed, May 29, 2013 at 3:19 PM, wrote:
> On Wed, May 29, 2013 at 12:25 PM, Julian Taylor
> wrote:
>> On 05/29/2013 06:12 AM, josef.p...@gmail.com wrote:
>>>
>>> On Tue, May 28, 2013 at 6:31 PM, Charles R Harris
>>> wrote:
Hi All,
There is a PR adding quickselect to numpy as
Thanks Tom,
before we ship it, I'd love to have some feedback on the new ARGOUT_VIEWM
type.
I used to create my managed arrays using
PyObject* cap = PyCObject_FromVoidPtr((void*)(*$1), free);
but since this function is deprecated, and because of Bill's background
work to bring numpy.i up to
On Sat, 2013-06-08 at 14:35 +0200, Anne Archibald wrote:
> Looking at the rational module, I think you're right: it really
> shouldn't be too hard to get quads working as a user type using gcc's
> __float128 type, which will provide hardware arithmetic in the
> unlikely case that the user has hardw
