On Sat, Oct 4, 2014 at 12:40 AM, Robert Kern wrote:
> On Sat, Oct 4, 2014 at 12:21 AM, Nathaniel Smith wrote:
>> On Fri, Oct 3, 2014 at 8:12 AM, Robert Kern wrote:
>>> On Fri, Oct 3, 2014 at 4:29 AM, Nathaniel Smith wrote:
On Fri, Oct 3, 2014 at 3:20 AM, Charles R Harris
wrote:
>
On Sat, Oct 4, 2014 at 12:21 AM, Nathaniel Smith wrote:
> On Fri, Oct 3, 2014 at 8:12 AM, Robert Kern wrote:
>> On Fri, Oct 3, 2014 at 4:29 AM, Nathaniel Smith wrote:
>>> On Fri, Oct 3, 2014 at 3:20 AM, Charles R Harris
>>> wrote:
On Thu, Oct 2, 2014 at 7:06 PM, Benjamin Root wrote:
On Fri, Oct 3, 2014 at 8:12 AM, Robert Kern wrote:
> On Fri, Oct 3, 2014 at 4:29 AM, Nathaniel Smith wrote:
>> On Fri, Oct 3, 2014 at 3:20 AM, Charles R Harris
>> wrote:
>>>
>>> On Thu, Oct 2, 2014 at 7:06 PM, Benjamin Root wrote:
Out[1] has an integer divided by an integer, and you c
On Fri, Oct 3, 2014 at 3:40 PM, Nathaniel Smith wrote:
> On Fri, Oct 3, 2014 at 10:00 PM, Nathaniel Smith wrote:
> > On Fri, Oct 3, 2014 at 5:13 AM, Charles R Harris
> > wrote:
> >>
> >> On Thu, Oct 2, 2014 at 10:12 PM, Charles R Harris
> >> wrote:
> >> Plus the g*dawful warning default to onl
On Fri, Oct 3, 2014 at 10:00 PM, Nathaniel Smith wrote:
> On Fri, Oct 3, 2014 at 5:13 AM, Charles R Harris
> wrote:
>>
>> On Thu, Oct 2, 2014 at 10:12 PM, Charles R Harris
>> wrote:
>> Plus the g*dawful warning default to only warn once. That has always
>> bothered me, it just seems useless.
>
>
On Fri, Oct 3, 2014 at 3:00 PM, Nathaniel Smith wrote:
> On Fri, Oct 3, 2014 at 5:13 AM, Charles R Harris
> wrote:
> >
> > On Thu, Oct 2, 2014 at 10:12 PM, Charles R Harris
> > wrote:
> > Plus the g*dawful warning default to only warn once. That has always
> > bothered me, it just seems useless
On Fri, Oct 3, 2014 at 5:13 AM, Charles R Harris
wrote:
>
> On Thu, Oct 2, 2014 at 10:12 PM, Charles R Harris
> wrote:
> Plus the g*dawful warning default to only warn once. That has always
> bothered me, it just seems useless.
I believe the idea is to only warn once per source location, i.e. if
On 10/03/2014 06:13 AM, Charles R Harris wrote:
> Plus the g*dawful warning default to only warn once. That has always bothered
> me, it just seems useless.
If you use a custom warning, there's no reason why you couldn't set a filter
that shows it every time by default.
Georg
__
Hi,
When you run f2py without -c option, the wrapper source files are generated
without compiling them.
With these source files and fortranobject.c, you can build the extension
module with your specific compiler options using the compiler framework of
your choice.
I am not familiar with Visual Stu
It does, but it is not portable. That's why I was hoping NumPy might think
about supporting more rounding algorithms.
On Thu, Oct 2, 2014 at 10:00 PM, John Zwinck wrote:
> On 3 Oct 2014 07:09, "T J" wrote:
> >
> > Any bites on this?
> >
> > On Wed, Sep 24, 2014 at 12:23 PM, T J wrote:
> >> Pyt
On Fri, Oct 3, 2014 at 1:33 AM, Stephan Hoyer wrote:
> On Thu, Oct 2, 2014 at 11:29 PM, Nathaniel Smith wrote:
>
>> The seterr warning system makes a lot of sense for IEEE754 floats,
>> which are specifically designed so that 0/0 has a unique well-defined
>> answer. For ints though this seems re
On Thu, Oct 2, 2014 at 11:29 PM, Nathaniel Smith wrote:
> The seterr warning system makes a lot of sense for IEEE754 floats,
> which are specifically designed so that 0/0 has a unique well-defined
> answer. For ints though this seems really broken to me. 0 / 0 = 0 is
> just the wrong answer. It w
On Fri, Oct 3, 2014 at 4:29 AM, Nathaniel Smith wrote:
> On Fri, Oct 3, 2014 at 3:20 AM, Charles R Harris
> wrote:
>>
>> On Thu, Oct 2, 2014 at 7:06 PM, Benjamin Root wrote:
>>>
>>> Out[1] has an integer divided by an integer, and you can't represent nan
>>> as an integer. Perhaps something weir
13 matches
Mail list logo
