On Fri, Jun 20, 2008 at 01:29, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> Hi,
>
>I was thinking about adding a versioning into the deprecation
> related functions. E.g., you could say that one function is deprecated
> in version 1.2, but adding a in_version in deprecate. Does anyone have
> s
Hi,
I was thinking about adding a versioning into the deprecation
related functions. E.g., you could say that one function is deprecated
in version 1.2, but adding a in_version in deprecate. Does anyone have
strong feeling against it ? It should be a transparant change. I would
also like t
On Thu, Jun 19, 2008 at 5:29 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>> I just tested the changes and there seem to be no ill effects. Should
>> I go ahead and commit it? I'll do it in a single commit with no other
>> changes so it's easy to revert should it prove to be a bad idea.
>
> Sure.
2008/6/16 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> I have a speed problem with the approach I'm using to detect phase wrappings
> in a 3D data set. In my application, phaseField is a 3D array containing the
> phase values of a field. In order to detect the vortices/phase windings at
> each point
Charles R Harris wrote:
> The compile flags are missing -fno-strict-aliasing. I don't know if
> this is a problem with the python distutils or what, but it would be
> nice if it didn't occur.
Yes. That's one of the reasons why I started numscons. The current
behavior in numpy.distutils is for t
2008/6/18 bevan <[EMAIL PROTECTED]>:
> Hello,
>
> I am looking for some pointers that will hopefully get me a round an issue I
> have hit.
>
> I have a timeseries of river flow and would like to carry out some analysis on
> the recession periods. That is anytime the values are decreasing. I would
Hi,
>> As long as it doesn't cause problems, then I'd vote for doing it.
>> This only happens at module import time, so even if several modules
>> using cython call it, it's only when they get imported. I think the
>> API simplification is worth it (minor, but still nice).
>>
>> I just tested the
On Thu, Jun 19, 2008 at 19:38, Pierre GM <[EMAIL PROTECTED]> wrote:
> On Thursday 19 June 2008 20:28:46 Robert Kern wrote:
>> On Thu, Jun 19, 2008 at 19:15, Pierre GM <[EMAIL PROTECTED]> wrote:
>> > Your question raises a good point: is there any consensus on using
>> > __all__ instead of the modul
On Thursday 19 June 2008 20:28:46 Robert Kern wrote:
> On Thu, Jun 19, 2008 at 19:15, Pierre GM <[EMAIL PROTECTED]> wrote:
> > Your question raises a good point: is there any consensus on using
> > __all__ instead of the module namespace ?
>
> I'm not sure what you mean. Can you clarify?
__all__
On Thu, Jun 19, 2008 at 19:18, Fernando Perez <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 19, 2008 at 5:06 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>> On Thu, Jun 19, 2008 at 19:02, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
>>> 2008/6/19 Fernando Perez <[EMAIL PROTECTED]>:
> - import_array(
On Thu, Jun 19, 2008 at 19:15, Pierre GM <[EMAIL PROTECTED]> wrote:
> Your question raises a good point: is there any consensus on using __all__
> instead of the module namespace ?
I'm not sure what you mean. Can you clarify?
--
Robert Kern
"I have come to believe that the whole world is an en
Hi all,
as we transition over to nose in full (which I'm very happy to see),
we'll want to have a good solution to finding doctests in extension
modules. My initial efforts haven't been very fruitful on this front,
and if any of you has any insights, I'd appreciate to hear them. I
started the co
On Thu, Jun 19, 2008 at 5:06 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 19, 2008 at 19:02, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
>> 2008/6/19 Fernando Perez <[EMAIL PROTECTED]>:
- import_array(). Can we put it at the bottom of c_numpy.pxd, so that
users don't have
Reggie,
Good to hear from you.
There are no particular reason why maximum/minimum/default_fill_value
functions should stay in limbo, I'll put them in __all__. I'll also try to
implement the accumulate/reduceat functions for maximum/minimum, using the
work you've done on _extrema_functions.
You
On Thu, Jun 19, 2008 at 19:02, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> 2008/6/19 Fernando Perez <[EMAIL PROTECTED]>:
>>> - import_array(). Can we put it at the bottom of c_numpy.pxd, so that
>>> users don't have to import it every time?
>>
>> Sounds fine to me, but I don't know if there c
2008/6/19 Fernando Perez <[EMAIL PROTECTED]>:
>> - import_array(). Can we put it at the bottom of c_numpy.pxd, so that
>> users don't have to import it every time?
>
> Sounds fine to me, but I don't know if there could be a subtle problem
> with pxds used by multiple pyx files. I'm not comfortabl
On Thu, Jun 19, 2008 at 18:18, Vineet Jain (gmail) <[EMAIL PROTECTED]> wrote:
> Thanks.
>
> With your changes, I'm getting a beta of 0.23 which I think is still wrong.
> I would have expected a value closer to 2.
To get the beta of AAPL versus the index , you need to swap
aapl_ret and _ret
Thanks.
With your changes, I'm getting a beta of 0.23 which I think is still wrong.
I would have expected a value closer to 2.
Vineet
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robert Kern
Sent: Thursday, June 19, 2008 7:08 PM
To: Discussion of N
Hi,
> Cython looks in the include_dirs for .pxd files, right? Then yes, I
> would support putting them alongside arrayobject.h.
Yes, right - Fernando just pointed me to the reference - quoting him:
"As indicated here:
http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/version/Doc/Manual/s
On Thu, Jun 19, 2008 at 18:02, Matthew Brett <[EMAIL PROTECTED]> wrote:
>>> Following on from Fernando's post about his Cython example, I would
>>> like to suggest adding his .pxd files to the standard numpy include
>>> directory, fetched with np.get_include()
>>
>> I am a bit hesitant to add them
On Thu, Jun 19, 2008 at 17:48, Vineet Jain (gmail) <[EMAIL PROTECTED]> wrote:
> I took the following code and applied it to aapl and time series (see
> attached file):
>
> import numpy as np
> lstsq = np.linalg.lstsq
> from numpy import float64, extract
>
> aapl_array = np.array([row[0] for ro
>> Following on from Fernando's post about his Cython example, I would
>> like to suggest adding his .pxd files to the standard numpy include
>> directory, fetched with np.get_include()
>
> I am a bit hesitant to add them to a standard "public" path until they
> are close to complete.
As usual, fa
On Thu, Jun 19, 2008 at 17:46, Matthew Brett <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Following on from Fernando's post about his Cython example, I would
> like to suggest adding his .pxd files to the standard numpy include
> directory, fetched with np.get_include()
I am a bit hesitant to add them to
This is just a minor question/problem with the new numpy.ma in version
1.1.0.
Because maximum and minimum in ma lack an accumulate attribute, I've
duplicated the functionality using the
maximum_fill_value/minimum_fill_value functions and doing something
like:
np.ma.masked_array(np.maximum.accumul
I took the following code and applied it to aapl and time series (see
attached file):
import numpy as np
lstsq = np.linalg.lstsq
from numpy import float64, extract
aapl_array = np.array([row[0] for row in stock_and_market_values])
_array = np.array([row[1] for row in stock_and_market_val
Hi,
Following on from Fernando's post about his Cython example, I would
like to suggest adding his .pxd files to the standard numpy include
directory, fetched with np.get_include()
Why:
Because anyone writing a Cython extension for numpy will need these
files. At the moment, this means that ever
Hi,
I am still tracking down the memory bug in my C module and I have found a odd
inconsistency.
I call import_array in the init function of the module and I want to check in
the later code if numpy has been initialised before by checking the
PyArray_API
value if it is NULL.
I have found out
2008/6/19 Matthew Brett <[EMAIL PROTECTED]>:
>>> - There's a bug in the latest Cython annotation, preventing the
>>> example from compiling. Workaround: replace "cython -a" with
>>> "cython".
>>
>> Mmh, I have 0.9.8 (their last release) and it works for me...
>
> I've got the same version, works f
Hi,
>> - There's a bug in the latest Cython annotation, preventing the
>> example from compiling. Workaround: replace "cython -a" with
>> "cython".
>
> Mmh, I have 0.9.8 (their last release) and it works for me...
I've got the same version, works for me too...
Matthew
__
On Thu, Jun 19, 2008 at 2:31 AM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> You weren't the only one confused. In fact, reading the FAQ didn't help me:
>
> http://wiki.cython.org/FAQ#head-a3d09805a03c014080feff45fe8e22024d473d62
>
> The NumPy definitions are all external, so why shouldn't t
On Thu, Jun 19, 2008 at 11:59, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 5:24 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>>> - The signature of numpy.test in 1.2 will be backward compatible with
>>> 1.1, and it will at least return some indication of failure (if not
>>> the
Hi all,
Is this supposed to be like that, i.e. is the fancy __setitem__ supposed to
not complain about unused assignees?
>>> v = zeros((10,))
>>> z = [1,2,5]
>>> v[z] = [1,2,4,5]
>>> v
array([ 0., 1., 2., 0., 0., 4., 0., 0., 0., 0.])
Contrast with:
>>> v[1:3] = [1,2,3,4]
Traceback (mo
Having an empty CFLAGS environment variable and running
$ python setup.py build
emits tons of these messages:
numpy/core/src/scalartypes.inc.src: In function 'scalar_value':
numpy/core/src/scalartypes.inc.src:77: warning: dereferencing type-punned
pointer will break strict-aliasing rules
The co
On Wed, Jun 18, 2008 at 5:24 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>> - The signature of numpy.test in 1.2 will be backward compatible with
>> 1.1, and it will at least return some indication of failure (if not
>> the same object as in 1.1). This will, by the way, make it different
>> from th
2008/6/18 Charles R Harris <[EMAIL PROTECTED]>:
>
>
> On Wed, Jun 18, 2008 at 11:48 AM, Anne Archibald <[EMAIL PROTECTED]>
> wrote:
>>
>> 2008/6/18 Stéfan van der Walt <[EMAIL PROTECTED]>:
>> > 2008/6/18 Anne Archibald <[EMAIL PROTECTED]>:
>> >> In [7]: x.take(x.argsort())
>> >> Out[7]: array([ 0.
2008/6/19 Fernando Perez <[EMAIL PROTECTED]>:
> after I updated the pyrex code to use cython, a bit of confusion led
> me to using .pxi includes instead of .pxd files and cimport. That
> turned out to be mistaken, as later clarified by the Cython team:
>
> http://codespeak.net/pipermail/cython-dev
36 matches
Mail list logo
