On Tue, Apr 23, 2013 at 12:10 PM, Frédéric Bastien wrote:
> Hi,
>
> A big thanks for that release.
>
> I also think it would be useful to do a release candidate about this. This
> release changed the behavior releated to python long and broke a test in
> Theano. Nothing important, but we could hav
Hi Jon,
I have personally never used f2py to link to library code, but according to
the documentation:
http://cens.ioc.ee/projects/f2py2e/usersguide/index.html#command-f2py
if you are building a module (that is, invoking f2py -c), then you can
either include the path to the .a file directly at t
Hi Andrew,
Am 12.04.13 11:50, schrieb Andrew Nelson:
> I have written a differential evolution optimiser that i use for
> curvefitting. As a genetic optimisation technique it is stochastic and
> relies heavily on random number generators to do the minimisation. As
> part
out of
On Thu, 2013-04-25 at 14:04 -0600, Charles R Harris wrote:
>
>
> On Thu, Apr 25, 2013 at 1:51 PM, wrote:
> On Thu, Apr 25, 2013 at 3:40 PM, Robert Kern
> wrote:
> > On Thu, Apr 25, 2013 at 8:21 PM, Andrew Giessel
> > wrote:
> >> I respect this opinion.
On Thu, Apr 25, 2013 at 1:51 PM, wrote:
> On Thu, Apr 25, 2013 at 3:40 PM, Robert Kern
> wrote:
> > On Thu, Apr 25, 2013 at 8:21 PM, Andrew Giessel
> > wrote:
> >> I respect this opinion. However (and maybe this is legacy), while
> reading
> >> through the numeric.py source file, I was surpris
On Thu, Apr 25, 2013 at 3:40 PM, Robert Kern wrote:
> On Thu, Apr 25, 2013 at 8:21 PM, Andrew Giessel
> wrote:
>> I respect this opinion. However (and maybe this is legacy), while reading
>> through the numeric.py source file, I was surprised at how short many of the
>> functions are, generally.
On Thu, Apr 25, 2013 at 8:21 PM, Andrew Giessel
wrote:
> I respect this opinion. However (and maybe this is legacy), while reading
> through the numeric.py source file, I was surprised at how short many of the
> functions are, generally. Functions like ones() and zeros() are pretty
> simple wrap
I respect this opinion. However (and maybe this is legacy), while reading
through the numeric.py source file, I was surprised at how short many of
the functions are, generally. Functions like ones() and zeros() are pretty
simple wrappers which call empty() and then copy over values.
FWIW, I had
On Thu, Apr 25, 2013 at 6:54 PM, Matthew Brett wrote:
> Hi,
>
> On Thu, Apr 25, 2013 at 10:42 AM, Robert Kern wrote:
>> On Thu, Apr 25, 2013 at 6:30 PM, Matthew Brett
>> wrote:
>>> So the decision has to be based on some estimate of:
>>>
>>> 1) Cost for adding a new function to the namespace
>
I would love to get the following pull requests of mine merged in:
https://github.com/numpy/numpy/pull/2822
https://github.com/numpy/numpy/pull/462
https://github.com/numpy/numpy/pull/359
https://github.com/numpy/numpy/pull/2821
The last one probably requires a bit more work, but I'm still waitin
Hi,
On Thu, Apr 25, 2013 at 10:42 AM, Robert Kern wrote:
> On Thu, Apr 25, 2013 at 6:30 PM, Matthew Brett
> wrote:
>> Hi,
>>
>> On Thu, Apr 25, 2013 at 10:14 AM, Robert Kern wrote:
>>> On Wed, Apr 24, 2013 at 10:37 PM, andrew giessel
>>> wrote:
Hello all-
A while back I emailed
On Thu, Apr 25, 2013 at 6:30 PM, Matthew Brett wrote:
> Hi,
>
> On Thu, Apr 25, 2013 at 10:14 AM, Robert Kern wrote:
>> On Wed, Apr 24, 2013 at 10:37 PM, andrew giessel
>> wrote:
>>> Hello all-
>>>
>>> A while back I emailed the list about function for the numpy namespace,
>>> iteraxis(), which
Hi,
On Thu, Apr 25, 2013 at 10:14 AM, Robert Kern wrote:
> On Wed, Apr 24, 2013 at 10:37 PM, andrew giessel
> wrote:
>> Hello all-
>>
>> A while back I emailed the list about function for the numpy namespace,
>> iteraxis(), which allows you to generalize the default iteration behavior of
>> nump
Hi all,
I have recently started using f2py to access some legacy fortran code
and it's mostly worked better than I expected. It handles common
blocks, block data, etc. with no problems. I did need to define the
type of all the arguments in subroutine and function calls, but not in
the body of th
On Wed, Apr 24, 2013 at 10:37 PM, andrew giessel
wrote:
> Hello all-
>
> A while back I emailed the list about function for the numpy namespace,
> iteraxis(), which allows you to generalize the default iteration behavior of
> numpy arrays over any axis.
>
> I've implemented this function more clea
On Thu, 2013-04-25 at 09:16 -0600, Charles R Harris wrote:
> Hi All,
>
> I think it is time to start the runup to the 1.8 release. I don't know
> of any outstanding blockers but if anyone has a PR/issue that they
> feel needs to be in the next Numpy release now is the time to make it
> known.
Sou
Charles R Harris gmail.com> writes:
>
> Hi All,I think it is time to start the runup to the 1.8 release. I don't
know of any outstanding blockers but if anyone has a PR/issue that they feel
needs to be in the next Numpy release now is the time to make it known.Chuck
>
It would be good to get
Hi All,
I think it is time to start the runup to the 1.8 release. I don't know of
any outstanding blockers but if anyone has a PR/issue that they feel needs
to be in the next Numpy release now is the time to make it known.
Chuck
___
NumPy-Discussion mai
18 matches
Mail list logo
