On Tue, Feb 9, 2010 at 9:54 AM, David Cournapeau wrote:
> On Mon, Feb 8, 2010 at 9:14 PM, Ralf Gommers
> > Final question is about Atlas and friends. Is 3.8.3 the best version to
> > install? Does it compile out of the box under Wine? Is this page
> > http://www.scipy.org/Installing_SciPy/Windows
On Sun, Feb 21, 2010 at 11:34 AM, Pauli Virtanen wrote:
> su, 2010-02-21 kello 20:17 +0200, Pauli Virtanen kirjoitti:
> [clip]
> > The Capsule API seems pretty much the same as the CObject API. (Why the
> > name change?) We can probably #define PyCapsule_* compatibility defines
> > in npy_3kcompa
su, 2010-02-21 kello 20:45 +0100, Dag Sverre Seljebotn kirjoitti:
> Pauli Virtanen wrote:
[clip]
> > Currently, Scipy has some known failures because of
> >
> > (i) removed new= keyword in numpy.histogram
> > (ii) Cython supports only native size/alignment PEP 3118 buffers, and
> > Numpy array
On Sun, Feb 21, 2010 at 4:06 PM, Robert Kern wrote:
> On Sun, Feb 21, 2010 at 16:00, Gökhan Sever wrote:
> > Hello,
> >
> > Since after Robert Kern showed http://advice.mechanicalkern.com/ on
> SciPy09
> > there are many similar initiatives that uses stackoverflow.com (SO)
> layout.
> > Some sma
On Mon, Feb 22, 2010 at 7:06 AM, Robert Kern wrote:
>
> I spent some time on Friday getting Plurk's Solace tweaked for our use
> (for various reasons, it's much better code to deal with than the
> CNPROG software currently running advice.mechanicalkern.com).
>
> http://opensource.plurk.com/Solace
On Sun, Feb 21, 2010 at 16:00, Gökhan Sever wrote:
> Hello,
>
> Since after Robert Kern showed http://advice.mechanicalkern.com/ on SciPy09
> there are many similar initiatives that uses stackoverflow.com (SO) layout.
> Some smart guys come up with this site http://stackexchange.com/ to those
> wh
Hello,
Since after Robert Kern showed http://advice.mechanicalkern.com/ on SciPy09
there are many similar initiatives that uses stackoverflow.com (SO) layout.
Some smart guys come up with this site http://stackexchange.com/ to those
who want to have a simple but a paid solution.
I don't have an i
No Warning for me:
└─(08:26 $)─> python isinf.py
True
└─(08:26 $)─> python2.5 isinf.py
True
Python 2.6.4 (r264:75706, Dec 7 2009, 18:43:55)
[GCC 4.4.1] on linux2
Python 2.5.4 (r254:67916, Jan 20 2010, 21:43:02)
[GCC 4.4.1] on linux2
numpy.version.version
'1.3.0'
└─(08:33 $)─> uname -a
Li
Pauli Virtanen wrote:
> Hi,
>
> The test suite passes now on Pythons 2.4 - 3.1. Further testing is very
> welcome -- also on Python 2.x. Please check that your favourite software
> still builds and works with SVN trunk Numpy.
>
> Currently, Scipy has some known failures because of
>
> (i) removed n
On Sun, Feb 21, 2010 at 11:34 AM, Pauli Virtanen wrote:
> su, 2010-02-21 kello 20:17 +0200, Pauli Virtanen kirjoitti:
> [clip]
> > The Capsule API seems pretty much the same as the CObject API. (Why the
> > name change?) We can probably #define PyCapsule_* compatibility defines
> > in npy_3kcompa
su, 2010-02-21 kello 20:17 +0200, Pauli Virtanen kirjoitti:
[clip]
> The Capsule API seems pretty much the same as the CObject API. (Why the
> name change?) We can probably #define PyCapsule_* compatibility defines
> in npy_3kcompat.h that use PyCObject on 2.x, and use the real thing on
> 3.x.
Btw
On Sun, Feb 21, 2010 at 4:30 AM, Charles R Harris wrote:
> Hi All,
>
> I would be much obliged if some folks would run the attached script and
> report the output, numpy version, and python version. It just runs
> np.isinf(np.inf), which raises an "invalid value" warning with current
> numpy. As
brucewa...@broo:~/Downloads$ python isinf.py
True
Kubuntu 9.10
NumPy 1.3.0
Python 2.6.4 (r264:75706, Dec 7 2009, 18:43:55)
[GCC 4.4.1] on linux2
On Sun, Feb 21, 2010 at 12:42 PM, Nadav Horesh wrote:
>
> $ python isinf.py
> Warning: invalid value encountered in isinf
> True
>
> machine: gentoo
su, 2010-02-21 kello 02:13 -0700, Charles R Harris kirjoitti:
> The warning is
>
> dep.py:6: PendingDeprecationWarning: The CObject API is deprecated as
> of Python 3.1. Please convert to using the Capsule API.
> np.dtype('M8[3M/40]')
>
> This doesn't happen with the old dtypes, so I assume it i
$ python isinf.py
Warning: invalid value encountered in isinf
True
machine: gentoo linux on amd64
python 2.6.4 (64 bit)
gcc 4.3.4
numpy.__version__ == '1.4.0'
glibc 2.10.1
Nadav
-Original Message-
From: numpy-discussion-boun...@scipy.org on behalf of Charles R Harris
Sent: Sun 21-F
Charles R Harris wrote:
> Hi All,
>
> I would be much obliged if some folks would run the attached script and
> report the output, numpy version, and python version. It just runs
> np.isinf(np.inf), which raises an "invalid value" warning with current
> numpy. As far as I can see the function i
On Sun, Feb 21, 2010 at 5:30 AM, Charles R Harris
wrote:
> Hi All,
>
> I would be much obliged if some folks would run the attached script and
> report the output, numpy version, and python version. It just runs
> np.isinf(np.inf), which raises an "invalid value" warning with current
> numpy. As f
Charles R Harris wrote:
> Hi All,
>
> I would be much obliged if some folks would run the attached script
> and report the output, numpy version, and python version. It just runs
> np.isinf(np.inf), which raises an "invalid value" warning with current
> numpy. As far as I can see the function it
On Sun, Feb 21, 2010 at 11:05 AM, Charles R Harris
wrote:
>
>
> On Sun, Feb 21, 2010 at 3:33 AM, David Cournapeau
> wrote:
>>
>> On Sun, Feb 21, 2010 at 7:30 PM, Charles R Harris
>> wrote:
>> > Hi All,
>> >
>> > I would be much obliged if some folks would run the attached script and
>> > report
On Sun, Feb 21, 2010 at 3:33 AM, David Cournapeau wrote:
> On Sun, Feb 21, 2010 at 7:30 PM, Charles R Harris
> wrote:
> > Hi All,
> >
> > I would be much obliged if some folks would run the attached script and
> > report the output, numpy version, and python version. It just runs
> > np.isinf(np.
On Sun, Feb 21, 2010 at 2:30 AM, Charles R Harris
wrote:
> I would be much obliged if some folks would run the attached script and
> report the output, numpy version, and python version.
>>> import isinf
Warning: invalid value encountered in isinf
True
Python 2.6.4 (r264:75706, Dec 7 2009, 18:4
AWESOME :)
On Sun, Feb 21, 2010 at 1:43 PM, Pauli Virtanen wrote:
> Hi,
>
> The test suite passes now on Pythons 2.4 - 3.1. Further testing is very
> welcome -- also on Python 2.x. Please check that your favourite software
> still builds and works with SVN trunk Numpy.
>
> Currently, Scipy has s
On Sun, Feb 21, 2010 at 6:30 PM, Charles R Harris wrote:
> Hi All,
>
> I would be much obliged if some folks would run the attached script and
> report the output, numpy version, and python version. It just runs
> np.isinf(np.inf), which raises an "invalid value" warning with current
> numpy. As
My machine is a PPC dual G5, running Mac OS X 10.5.8
~ $ python
Python 2.5.4 (r254:67917, Dec 23 2008, 14:57:27)
[GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy as np
>>> import warnings
>>>
>>> war
Hi,
The test suite passes now on Pythons 2.4 - 3.1. Further testing is very
welcome -- also on Python 2.x. Please check that your favourite software
still builds and works with SVN trunk Numpy.
Currently, Scipy has some known failures because of
(i) removed new= keyword in numpy.histogram
(ii) C
On 2/21/2010 5:30 AM, Charles R Harris wrote:
> I would be much obliged if some folks would run the attached script and
> report the output, numpy version, and python version.
No problem with NumPy 1.3.0 (from superpack) on Python 2.6.4 under Vista.
Alan Isaac
Python 2.6.4 (r264:75708, Oct 26 200
On Sun, 21 Feb 2010 13:22:41 +0200
Pauli Virtanen wrote:
> Hi,
>
> Please remind me what platform you are running on. Also,
>please update
> and re-run the tests, and check the output from
>
> import numpy as np
> from numpy.core.multiarray import memorysimpleview as
>memoryview
>
> dt = [(
Hi,
Please remind me what platform you are running on. Also, please update
and re-run the tests, and check the output from
import numpy as np
from numpy.core.multiarray import memorysimpleview as memoryview
dt = [('a', np.int8), ('b', np.int16),
('c', np.int32), ('d', np.int64),
('e'
On Sun, 21 Feb 2010 03:30:31 -0700
Charles R Harris wrote:
> Hi All,
>
> I would be much obliged if some folks would run the
>attached script and
> report the output, numpy version, and python version. It
>just runs
> np.isinf(np.inf), which raises an "invalid value"
>warning with current
>
On Sun, Feb 21, 2010 at 7:30 PM, Charles R Harris
wrote:
> Hi All,
>
> I would be much obliged if some folks would run the attached script and
> report the output, numpy version, and python version. It just runs
> np.isinf(np.inf), which raises an "invalid value" warning with current
> numpy. As f
Hi All,
I would be much obliged if some folks would run the attached script and
report the output, numpy version, and python version. It just runs
np.isinf(np.inf), which raises an "invalid value" warning with current
numpy. As far as I can see the function itself hasn't changed since
numpy1.3, ye
==
FAIL:
test_multiarray.TestNewBufferProtocol.test_export_endian
--
Traceback (most recent call last):
File
"/home/nwagner/local/lib64/python2.6/site-packag
Hi Travis,
The warning is
dep.py:6: PendingDeprecationWarning: The CObject API is deprecated as of
Python 3.1. Please convert to using the Capsule API.
np.dtype('M8[3M/40]')
This doesn't happen with the old dtypes, so I assume it is associated with
something introduced for datetime. Any ideas
33 matches
Mail list logo
