Le lundi 30 juillet 2012 à 11:07 -0700, Ondřej Čertík a écrit :
> On Mon, Jul 30, 2012 at 10:04 AM, Ronan Lamy wrote:
> > Le lundi 30 juillet 2012 à 17:10 +0100, Ronan Lamy a écrit :
> >> Le lundi 30 juillet 2012 à 04:57 +0100, Ronan Lamy a écrit :
> >> > Le lundi 30 juillet 2012 à 02:00 +0100, Ro
Hi,
I have wrapped a c++ code with SWIG.
Now that code used to read input from ASCII files. I'm trying to replace that
part with an input coming from numpy.
I would rather not use setup.py if I have to (but if I can't avoid fine)
I'm looking at SWIG/numpy tutorials
looks like you need to do s
Hi,
A partial answer to your questions:
On Mon, Jul 30, 2012 at 10:33 PM, Vlastimil Brom
wrote:
> Hi all,
> I'd like to ask for some hints or advice regarding the usage of
> numpy.array and especially slicing.
>
> I only recently tried numpy and was impressed by the speedup in some
> parts of t
Hi all,
I'd like to ask for some hints or advice regarding the usage of
numpy.array and especially slicing.
I only recently tried numpy and was impressed by the speedup in some
parts of the code, hence I suspect, that I might miss some other
oportunities in this area.
I currently use the followi
On Mon, Jul 30, 2012 at 10:04 AM, Ronan Lamy wrote:
> Le lundi 30 juillet 2012 à 17:10 +0100, Ronan Lamy a écrit :
>> Le lundi 30 juillet 2012 à 04:57 +0100, Ronan Lamy a écrit :
>> > Le lundi 30 juillet 2012 à 02:00 +0100, Ronan Lamy a écrit :
>> >
>> > >
>> > > Anyway, I managed to compile (by b
On Wed, Jul 25, 2012 at 7:36 PM, Ralf Gommers
wrote:
> [...]
> It looks like you want to discard the Milestones, except for the 1.7.0,
> 1.8.0 and 2.0.0 ones. Why not keep all of them?
These were the only ones defined in the current numpy repository.
I'll add code to create any missing ones.
> I
Le lundi 30 juillet 2012 à 17:10 +0100, Ronan Lamy a écrit :
> Le lundi 30 juillet 2012 à 04:57 +0100, Ronan Lamy a écrit :
> > Le lundi 30 juillet 2012 à 02:00 +0100, Ronan Lamy a écrit :
> >
> > >
> > > Anyway, I managed to compile (by blanking
> > > numpy/distutils/command/__init__.py) and to
Hi,
first my apologies for crossposting this to two maillists, but as both
projects are affected I think this is in order.
Like the subject says I encountered some undesired behavior in the
interaction of SciPy with NumPy.
Using the "old" SciPy version 0.9.0 everything works fine and smooth.
But
Le lundi 30 juillet 2012 à 04:57 +0100, Ronan Lamy a écrit :
> Le lundi 30 juillet 2012 à 02:00 +0100, Ronan Lamy a écrit :
>
> >
> > Anyway, I managed to compile (by blanking
> > numpy/distutils/command/__init__.py) and to run the tests. I only see
> > the 2 pickle errors from your latest gist.
On 07/30/2012 10:53 AM, Travis Oliphant wrote:
> Can you file a bug report on Github's issue tracker?
It's https://github.com/numpy/numpy/issues/369
Phil
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo
Can you file a bug report on Github's issue tracker?
Thanks,
-Travis
On Jul 26, 2012, at 1:33 PM, Phil Hodge wrote:
> On a Linux machine:
>
>> uname -srvop
> Linux 2.6.18-308.8.2.el5 #1 SMP Tue May 29 11:54:17 EDT 2012 x86_64
> GNU/Linux
>
> this example shows an apparent problem with the w
On Mon, Jul 30, 2012 at 2:30 PM, Phil Hodge wrote:
> On 07/27/2012 03:58 PM, Andreas Mueller wrote:
>> Hi Everybody.
>> The bug is that no error is raised, right?
>> The docs say
>>
>> where(condition, [x, y])
>>
>> x, y : array_like, optional
>> Values from which to choose. `x` and `y` need
On 07/27/2012 03:58 PM, Andreas Mueller wrote:
> Hi Everybody.
> The bug is that no error is raised, right?
> The docs say
>
> where(condition, [x, y])
>
> x, y : array_like, optional
> Values from which to choose. `x` and `y` need to have the same
> shape as `condition`
>
> In the exam
13 matches
Mail list logo
