based on our situation
On 10/01/2013 9:02 AM, Christopher Hanley wrote:
I'm all for a big scary warning on import. Fair
warning is good for everyone, not just our developers.
agree
As
I'm all for a big scary warning on import. Fair warning is good for
everyone, not just our developers.
As for testing, our software that uses the API is tested nightly. So if
our software stops working, and the compatibility layer is the cause, we
would definitely be looking into what happened.
Hi,
Just to note, as they plan to remove there dependency on it this year,
is it bad that they can't use 1.8 for a few mounts until they finish
the conversion? They already have a working version. They can continue
to use it for as long they want. The only advantage for them if the
compat layers a
On Wed, Jan 9, 2013 at 4:21 PM, Christopher Hanley wrote:
> After poking around our code base and talking to a few folks I predict
> that we at STScI can remove our dependence on the numpy-numarray
> compatibility layer by the end of this calendar year. I'm unsure of what
> the timeline for numpy
On Wed, Jan 9, 2013 at 11:21 PM, Christopher Hanley wrote:
> After poking around our code base and talking to a few folks I predict that
> we at STScI can remove our dependence on the numpy-numarray compatibility
> layer by the end of this calendar year. I'm unsure of what the timeline for
> nump
After poking around our code base and talking to a few folks I predict that
we at STScI can remove our dependence on the numpy-numarray compatibility
layer by the end of this calendar year. I'm unsure of what the timeline
for numpy 1.8 is so I don't know if this schedule supports removal of the
co
We can keep testing it in coming
versions while we catch up.
Raul Cota (P.Eng., Ph.D. Chemical Engineering)
Research & Development Manager
Virtual Materials Group - Canada
www.virtualmaterials.com
===
On Mon, Jan 7, 2013 at 4:08 PM, Raul Cota wrote:
> Ran a fair bit of our test suite using numpy 1.7 compiling against the
> corresponding 'numpy/oldnumeric.h' and everything worked well .
>
> All I saw was the warning below which is obviously expected:
> """
> Warning23warning Msg: Using
Ran a fair bit of our test suite using
numpy 1.7 compiling against the corresponding 'numpy/oldnumeric.h'
and everything worked well .
All I saw was the warning below which is obviously expected:
"""
Warning 23 warning Msg: Using deprecated NumP
On 07/01/2013 9:22 AM, Charles R Harris
wrote:
On Sun, Jan 6, 2013 at 9:15 PM, Raul Cota
wrote:
I realize we may be a minority but it would be very
nice if support for n
On Sun, Jan 6, 2013 at 9:15 PM, Raul Cota wrote:
> I realize we may be a minority but it would be very nice if support for
> numeric could be kept for a few more versions. We don't have any particular
> needs for numarray.
>
> We just under went through an extremely long and painful process to
>
I realize we may be a minority but it
would be very nice if support for numeric could be kept for a few
more versions. We don't have any particular needs for numarray.
We just under went through an extremely long and painful process
to upgrade our software
On Sun, Jan 6, 2013 at 5:07 PM, Nathaniel Smith wrote:
> On Sun, Jan 6, 2013 at 10:36 PM, Charles R Harris
> wrote:
> >
> >
> > On Sun, Jan 6, 2013 at 8:09 AM, Charles R Harris <
> charlesr.har...@gmail.com>
> > wrote:
> >>
> >>
> >>
> >> On Sun, Jan 6, 2013 at 7:42 AM, Nathaniel Smith wrote:
>
On Sun, Jan 6, 2013 at 10:36 PM, Charles R Harris
wrote:
>
>
> On Sun, Jan 6, 2013 at 8:09 AM, Charles R Harris
> wrote:
>>
>>
>>
>> On Sun, Jan 6, 2013 at 7:42 AM, Nathaniel Smith wrote:
>>>
>>> On Sun, Jan 6, 2013 at 2:38 AM, Charles R Harris
>>> wrote:
>>> > Thoughts?
>>>
>>> To be clear, wh
On Sun, Jan 6, 2013 at 8:09 AM, Charles R Harris
wrote:
>
>
> On Sun, Jan 6, 2013 at 7:42 AM, Nathaniel Smith wrote:
>
>> On Sun, Jan 6, 2013 at 2:38 AM, Charles R Harris
>> wrote:
>> > Thoughts?
>>
>> To be clear, what you're talking about is basically deleting these two
>> packages:
>> numpy
On Sun, Jan 6, 2013 at 7:42 AM, Nathaniel Smith wrote:
> On Sun, Jan 6, 2013 at 2:38 AM, Charles R Harris
> wrote:
> > Thoughts?
>
> To be clear, what you're talking about is basically deleting these two
> packages:
> numpy.oldnumeric
> numpy.numarray
> plus the compatibility C API in
> nu
On Sun, Jan 6, 2013 at 2:38 AM, Charles R Harris
wrote:
> Thoughts?
To be clear, what you're talking about is basically deleting these two packages:
numpy.oldnumeric
numpy.numarray
plus the compatibility C API in
numpy/numarray/include
?
So this would only affect Python code which explicit
17 matches
Mail list logo