On Sun, Jun 21, 2009 at 3:08 AM, Charles R
Harris wrote:
>
> Since we are extending the API and bumping up the API number, I wonder
> if we should change the python dependency to 2.6?
I think we should keep compatibility with python 2.4, it is still used
by many people, and the default python on
On Sat, Jun 20, 2009 at 19:31, Gael Varoquaux
wrote:
>
> On Sat, Jun 20, 2009 at 12:08:29PM -0600, Charles R Harris wrote:
> > Since we are extending the API and bumping up the API number, I wonder
> > if we should change the python dependency to 2.6? If there are
> > otherwise no major improvemen
On Sat, Jun 20, 2009 at 12:08:29PM -0600, Charles R Harris wrote:
> Since we are extending the API and bumping up the API number, I wonder
> if we should change the python dependency to 2.6? If there are
> otherwise no major improvements in the pipe besides bug fixes now
> might be the time to star
On Sat, Jun 20, 2009 at 6:24 PM, Skipper Seabold wrote:
> On Sat, Jun 20, 2009 at 5:33 PM, Ralf
> Gommers wrote:
> > Hi,
> >
> > I'm working on the I/O documentation, and have a bunch of questions.
> >
> > 1. The npy/npz formats are documented in lib.format and in the NEP
> > (http://svn.scipy.org
On Sat, Jun 20, 2009 at 6:08 PM, Robert Kern wrote:
> On Sat, Jun 20, 2009 at 16:33, Ralf Gommers
> wrote:
> >
> > Hi,
> >
> > I'm working on the I/O documentation, and have a bunch of questions.
> >
> > 1. The npy/npz formats are documented in lib.format and in the NEP (
> http://svn.scipy.org/
On Sat, Jun 20, 2009 at 5:33 PM, Ralf
Gommers wrote:
> Hi,
>
> I'm working on the I/O documentation, and have a bunch of questions.
>
> 1. The npy/npz formats are documented in lib.format and in the NEP
> (http://svn.scipy.org/svn/numpy/trunk/doc/neps/npy-format.txt). Is
> lib.format the right plac
On Sat, Jun 20, 2009 at 16:33, Ralf Gommers wrote:
>
> Hi,
>
> I'm working on the I/O documentation, and have a bunch of questions.
>
> 1. The npy/npz formats are documented in lib.format and in the NEP
> (http://svn.scipy.org/svn/numpy/trunk/doc/neps/npy-format.txt). Is lib.format
> the right p
Hi,
I'm working on the I/O documentation, and have a bunch of questions.
1. The npy/npz formats are documented in lib.format and in the NEP (
http://svn.scipy.org/svn/numpy/trunk/doc/neps/npy-format.txt). Is lib.format
the right place to add relevant parts of the NEP, or would doc.io be better?
O
A Saturday 20 June 2009 19:04:03 Erik Tollerud escrigué:
> I've encountered an odd error I don't understand (see the case below):
> the first structured array ("A" in the example) initializes from a
> list of length-2 arrays with no problem, but if I give it a 2-by-2
> array ("B"), it raises a Type
On Sat, Jun 20, 2009 at 8:15 AM, David Cournapeau wrote:
> On Thu, Jun 18, 2009 at 2:05 PM, Charles R
> Harris wrote:
>
>>
>> I don't know. I think it is cleaner to depend on 1.4.0
>
> Oh, definitely - I certainly prefer this solution as well.
>
>> but there
>> might be other considerations such as
Hi Erik
2009/6/20 Erik Tollerud :
> I've encountered an odd error I don't understand (see the case below):
> the first structured array ("A" in the example) initializes from a
> list of length-2 arrays with no problem, but if I give it a 2-by-2
> array ("B"), it raises a TypeError... Why would it
I've encountered an odd error I don't understand (see the case below):
the first structured array ("A" in the example) initializes from a
list of length-2 arrays with no problem, but if I give it a 2-by-2
array ("B"), it raises a TypeError... Why would it be any different to
convert the first index
2009/6/20 Stéfan van der Walt
> 2009/6/20 Stéfan van der Walt :
> > I just updated my machine, and everything broke in the way you
> > described. This must be a regression in one of the python26-*
> > packages?
>
> The problem can be reproduced from the command prompt:
>
> $ nosetests
> Tracebac
2009/6/20 Stéfan van der Walt :
> I just updated my machine, and everything broke in the way you
> described. This must be a regression in one of the python26-*
> packages?
The problem can be reproduced from the command prompt:
$ nosetests
Traceback (most recent call last):
File "/usr/bin/nose
2009/6/20 Darren Dale :
> 2009/6/20 Stéfan van der Walt
>> I am running NumPy from SVN with nose 0.10.4 on Karmic and everything
>> seems ok. Could be that one of the packages in Karmic itself is
>> broken?
>
> That's interesting. Have you been keeping up to date with the package
> manager? Maybe
2009/6/20 Stéfan van der Walt
> Hi,
>
> I am running NumPy from SVN with nose 0.10.4 on Karmic and everything
> seems ok. Could be that one of the packages in Karmic itself is
> broken?
>
That's interesting. Have you been keeping up to date with the package
manager? Maybe I need to do a fresh i
On Sat, Jun 20, 2009 at 10:03 AM, David Cournapeau <
da...@ar.media.kyoto-u.ac.jp> wrote:
> Stéfan van der Walt wrote:
> > Hi,
> >
> > I am running NumPy from SVN with nose 0.10.4 on Karmic and everything
> > seems ok. Could be that one of the packages in Karmic itself is
> > broken?
> >
>
> Or m
Stéfan van der Walt wrote:
> Hi,
>
> I am running NumPy from SVN with nose 0.10.4 on Karmic and everything
> seems ok. Could be that one of the packages in Karmic itself is
> broken?
>
Or maybe something with nose 0.11 (I don't see any change related to new
nose in numpy/testing since 1.3.0, t
Hi,
I am running NumPy from SVN with nose 0.10.4 on Karmic and everything
seems ok. Could be that one of the packages in Karmic itself is
broken?
Regards
Stéfan
2009/6/20 Darren Dale :
> I know karmic is in early development, but I wanted to give the numpy devs a
> heads up that the test suite
On Thu, Jun 18, 2009 at 2:05 PM, Charles R
Harris wrote:
>
> I don't know. I think it is cleaner to depend on 1.4.0
Oh, definitely - I certainly prefer this solution as well.
> but there
> might be other considerations such as release schedules, both for
> numpy/scipy and perhaps some of the maj
I know karmic is in early development, but I wanted to give the numpy devs a
heads up that the test suite will not run on this platform. I've tested
numpy-1.2.1 installed with the package manager, the 1.3.0 release, and the
trunk. I'm not familiar enough with the internals of numpy's testing
framew
21 matches
Mail list logo
