Martin Spacek wrote:
> I just tried building the 1.0.2 release, and I still get the type
> conversion problem. Building from 1.0.3dev3736 makes the problem
> disappear. Was this an issue that was fixed recently?
>
>
Yes.
-Travis
___
Numpy-discussio
On Tue, May 08, 2007 at 11:51:23AM -0400, Anne Archibald wrote:
> Unfortunately this seems to make it impossible for me to use ctrl-c or
> any other method to interrupt an interminable computation (on MPL
> 0.90.0). Very frustrating.
AFAIK this is fixed in the latest release of ipython (Kudos to t
On 08/05/07, Gael Varoquaux <[EMAIL PROTECTED]> wrote:
> On Tue, May 08, 2007 at 12:18:56PM +0200, Giorgio Luciano wrote:
> > A good workspace (with an interactive button) just to not get figures
> > freezed
>
> I am not sure what you mean by "figures freezed" but I would like to
> check that you a
All,
On a 2D array, numpy.core.umath.maximum.reduce returns a 1D array (the
default axis is 0). An axis=None is not recognized as a valid argument for
numpy.core.umath.maximum, unfortunately... Is this the wanted behavior ?
Thanks a lot in advance
P.
_
Thanks Gael,
I dont' use Ipython, but Ide in interactive mode and everything is fine
(changed matplotlibrc and then se switch on in configuration). I just
meant hat if you dont' know it or dont' pay attention to start with the
correct shortcut etc. etc. you dont' have an "immediate" interactive
On 02.05.2007, at 23:36, James Boyle wrote:
> So far I have not had success.
> Enclosed is the dump of my most recent failure - the complaint comes
> from the linker since the linker has both a powerPC (ppc) and an
> intel (i386) flag. I guess that what is being attempted is a
> universal build (
On Tue, May 08, 2007 at 12:18:56PM +0200, Giorgio Luciano wrote:
> A good workspace (with an interactive button) just to not get figures
> freezed
I am not sure what you mean by "figures freezed" but I would like to
check that you are aware of ipython, and its "-pylab" switch that allows
a nice i
All good points stated here.
Unfortunatly I'm not able to contribute, and as stated also in other
thread, scipy/python was not born for being a clone of matlab (uhmm well
probably matplotlib at first was). What would be the "killer" distro for
matlab ?
An updated distro with numpy/scipy/matplotl
I just tried building the 1.0.2 release, and I still get the type
conversion problem. Building from 1.0.3dev3736 makes the problem
disappear. Was this an issue that was fixed recently?
Martin
Martin Spacek wrote:
> In linux and win32 (numpy 1.0.1 release compiled from source, and
> 1.0.3dev3726
