On Sun, Oct 7, 2012 at 6:36 PM, Dan Goodman wrote:
> On 06/10/2012 18:17, Ralf Gommers wrote:
>> Do you mean scalars or arrays? For me set_printoptions only affects
>> arrays and not scalars. Both float32 and float64 arrays work as advertised:
>
> Yep, I mean scalars (although as Warren noted, it
On 06/10/2012 18:17, Ralf Gommers wrote:
> Do you mean scalars or arrays? For me set_printoptions only affects
> arrays and not scalars. Both float32 and float64 arrays work as advertised:
Yep, I mean scalars (although as Warren noted, it also affects e.g.
array(1.23456789)).
Dan
__
On Sat, Oct 6, 2012 at 12:17 PM, Ralf Gommers wrote:
>
>
> On Fri, Oct 5, 2012 at 5:17 PM, Dan Goodman wrote:
>
>> Hi,
>>
>> numpy.set_printoptions(precision=...) doesn't affect single floats, even
>> if they are numpy floats rather than Python floats. Is this a bug or is
>> there some reason for
On Fri, Oct 5, 2012 at 5:17 PM, Dan Goodman wrote:
> Hi,
>
> numpy.set_printoptions(precision=...) doesn't affect single floats, even
> if they are numpy floats rather than Python floats. Is this a bug or is
> there some reason for this behaviour? I ask because I have a class that
> derives from
Hi,
numpy.set_printoptions(precision=...) doesn't affect single floats, even
if they are numpy floats rather than Python floats. Is this a bug or is
there some reason for this behaviour? I ask because I have a class that
derives from numpy.float64 and adds some extra information, and I'd like
