2009/6/22 David Cournapeau :
> My main motivation for an early numpy 1.4 is scipy 0.8.0. But if other
> people think numpy 1.4.0 as it is now is too 'weak', making scipy
> 0.8.0 compatible with numpy 1.3.0 is technically possible. Then we can
> talk about adding those features for numpy 1.4.0, and
On Mon, Jun 22, 2009 at 10:15 AM, Bruce Southey wrote:
>
>
> On Sun, Jun 21, 2009 at 4:01 AM, David Cournapeau
> wrote:
>>
>> (Continuing the discussion initiated in the neighborhood iterator thread)
>>
>> Hi,
>>
>> I would like to gather people's opinion on what to target for numpy
>> 1.4.0.
>
On Mon, Jun 22, 2009 at 3:18 PM, Pierre GM wrote:
>
> On Jun 21, 2009, at 5:01 AM, David Cournapeau wrote:
>
>> (Continuing the discussion initiated in the neighborhood iterator
>> thread)
>>
>> Hi,
>>
>> I would like to gather people's opinion on what to target for numpy
>> 1.4.0.
>
> Is this a
On Jun 21, 2009, at 5:01 AM, David Cournapeau wrote:
> (Continuing the discussion initiated in the neighborhood iterator
> thread)
>
> Hi,
>
>I would like to gather people's opinion on what to target for numpy
> 1.4.0.
Is this a wish list ?
* As Darren mentioned, some __array_prepare__ me
On 21-Jun-09, at 11:59 AM, David Cournapeau wrote:
>> Can't really say at this point, but it is the suggested path to
>> python-3.
>
> OTOH, I don't find the python 3 "official" transition story very
> convincing. I have tried to gather all the information I could find,
> both on the python wiki a
On Sun, Jun 21, 2009 at 05:48, Ian Mallett wrote:
>
> This works perfectly! Is there likewise a similar call for Numeric?
If Numeric.roll() exists, then yes. Otherwise, you may have to look at
the numpy.roll() sources to replicate what it does.
--
Robert Kern
"I have come to believe that the w
On Mon, Jun 22, 2009 at 2:17 AM, Robert wrote:
>
> I'd like even support for Python 2.3. Many basic libraries still
> support 2.3
and many don't :) In my experience, the limit is often python 2.4
(which we still support).
> And numpy is a very basic library. And what is in numpy (scipy)
> that r
hello,
is it possible to resize in place a memmap array?
thanks in advice
Luigi
--
~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*
Io sono
lo sbaglio, il momento di confusione, l'inopportuno
Non sono niente.
Non sarò mai niente.
Non posso vol
On Mon, Jun 22, 2009 at 7:04 AM, Travis Oliphant wrote:
> I don't remember dropping support for 2.4. When did that happen?
It does work on 2.4, I regularly test numpy and scipy on RHEL 5 with
64 bits python 2.4. We dropped 2.3 support since 1.2 IIRC.
David
__
On Sun, Jun 21, 2009 at 4:01 AM, David Cournapeau <
da...@ar.media.kyoto-u.ac.jp> wrote:
> (Continuing the discussion initiated in the neighborhood iterator thread)
>
> Hi,
>
>I would like to gather people's opinion on what to target for numpy
> 1.4.0.
>- Chuck suggested to drop python < 2
On Sun, Jun 21, 2009 at 4:04 PM, Travis Oliphant wrote:
> I don't remember dropping support for 2.4. When did that happen?
>
>
It didn't, numpy should still run with 2.4. If there is a problem I
haven't heard about it.
Chuck
___
Numpy-discussion maili
I don't remember dropping support for 2.4. When did that happen?
Sent from my iPhone
On Jun 21, 2009, at 12:17 PM, Robert wrote:
> Lou Pecora wrote:
>> I'm still using 2.4, but I plan to go to 2.5 when the project we're
>> doing now reaches a stable point later this year. Not sure after
>
Lou Pecora wrote:
> I'm still using 2.4, but I plan to go to 2.5 when the project we're
> doing now reaches a stable point later this year. Not sure after that.
> I know it's real work to keep several versions going, but I sense there
> are a lot of people in the 2.4 - 2.5 window. I guess 2.6
I'm still using 2.4, but I plan to go to 2.5 when the project we're doing now
reaches a stable point later this year. Not sure after that. I know it's real
work to keep several versions going, but I sense there are a lot of people in
the 2.4 - 2.5 window. I guess 2.6 is a mini step toward 3.0
On Mon, Jun 22, 2009 at 12:59 AM, David Cournapeau wrote:
> Another suggestion is to avoid breaking the API when transitioning for
> python 3. But that seems quite unrealistic. How do we deal with the
> removing of string/long APIs ?
^ This should be int, of cours
On Mon, Jun 22, 2009 at 12:42 AM, Charles R
Harris wrote:
> On Sun, Jun 21, 2009 at 8:55 AM, Darren Dale wrote:
>> On Sun, Jun 21, 2009 at 10:38 AM, John Reid
>> wrote:
>>>
>>> David Cournapeau wrote:
>>> > (Continuing the discussion initiated in the neighborhood iterator
>>> > thread)
>>> > -
On Sun, Jun 21, 2009 at 9:42 AM, Charles R
Harris wrote:
> On Sun, Jun 21, 2009 at 8:55 AM, Darren Dale wrote:
>> On Sun, Jun 21, 2009 at 10:38 AM, John Reid
>> wrote:
>>>
>>> David Cournapeau wrote:
>>> > (Continuing the discussion initiated in the neighborhood iterator
>>> > thread)
>>> > -
On Sun, Jun 21, 2009 at 8:55 AM, Darren Dale wrote:
> On Sun, Jun 21, 2009 at 10:38 AM, John Reid
> wrote:
>>
>> David Cournapeau wrote:
>> > (Continuing the discussion initiated in the neighborhood iterator
>> > thread)
>> > - Chuck suggested to drop python < 2.6 support from now on. I am
>>
On Sun, Jun 21, 2009 at 11:55 PM, Darren Dale wrote:
> On Sun, Jun 21, 2009 at 10:38 AM, John Reid
> wrote:
>>
>> David Cournapeau wrote:
>> > (Continuing the discussion initiated in the neighborhood iterator
>> > thread)
>> > - Chuck suggested to drop python < 2.6 support from now on. I am
>>
On Sun, Jun 21, 2009 at 10:38 AM, John Reid wrote:
> David Cournapeau wrote:
> > (Continuing the discussion initiated in the neighborhood iterator thread)
> > - Chuck suggested to drop python < 2.6 support from now on. I am
> > against it without a very strong and detailed rationale, because m
David Cournapeau wrote:
> (Continuing the discussion initiated in the neighborhood iterator thread)
> - Chuck suggested to drop python < 2.6 support from now on. I am
> against it without a very strong and detailed rationale, because many OS
> still don't have python 2.6 (RHEL, Ubuntu LTS).
I
On Sun, Jun 21, 2009 at 5:01 AM, David Cournapeau <
da...@ar.media.kyoto-u.ac.jp> wrote:
> (Continuing the discussion initiated in the neighborhood iterator thread)
>
> Hi,
>
>I would like to gather people's opinion on what to target for numpy
> 1.4.0.
>- Chuck suggested to drop python < 2
This works perfectly! Is there likewise a similar call for Numeric?
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
(Continuing the discussion initiated in the neighborhood iterator thread)
Hi,
I would like to gather people's opinion on what to target for numpy
1.4.0.
- Chuck suggested to drop python < 2.6 support from now on. I am
against it without a very strong and detailed rationale, because many O
On Sun, Jun 21, 2009 at 03:31, Ian Mallett wrote:
>
> Sounds like it would work, but unfortunately numpy was one of my dependency
> constraints. I should have mentioned that.
In that case, use numpy.roll() instead of slicing to get wraparound.
--
Robert Kern
"I have come to believe that the w
Sounds like it would work, but unfortunately numpy was one of my dependency
constraints. I should have mentioned that.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Sun, Jun 21, 2009 at 02:04, Ian Mallett wrote:
>
> Hello,
>
> I'm working on a program that will draw me a metallic 3D texture. I
> successfully made a Perlin noise implementation and found that when the
> result is blurred in one direction, the result actually looks somewhat like
> brushed
Hello,
I'm working on a program that will draw me a metallic 3D texture. I
successfully made a Perlin noise implementation and found that when the
result is blurred in one direction, the result actually looks somewhat like
brushed aluminum. The plan is to do this for every n*m*3 layer (2D textur
28 matches
Mail list logo
