Hi Patrick,
On Sun, Feb 28, 2010 at 1:35 PM, Patrick Marsh patrickmars...@gmail.com wrote:
Greetings,
I have been trying to build the numpy superpack on windows using the
binaries posted by David.
Could you post *exactly* the sequence of commands you executed ?
Especially at the beginning,
Patrick Marsh wrote:
Hi David,
There really isn't much in the way of commands that I've used - I
haven't gotten that far. So far, I've downloaded your binaries and then
attempted to set up my numpy site.cfg file to use your binaries. I used
the following as my site.cfg
[atlas]
On Mon, Mar 1, 2010 at 1:35 PM, James Bergstra
bergs...@iro.umontreal.ca wrote:
Could someone point me to documentation (or even numpy src) that shows
how to allocate a numpy.int8 in C, or check to see if a PyObject is a
numpy.int8?
In numpy, the type is described in the dtype type object, so
David Warde-Farley wrote:
My first
instinct would be to look for logdet, but I would also not expect such
a function to return the log determinant *and* the sign of the
determinant.
What about having logadet for the (common) case where log |A| only is
needed, and having the more complex
Dag Sverre Seljebotn wrote:
(I'd think one basically has to make the same blatant assumptions that
f2py makes about type conversion, name mangling etc., but that is also
much less dangerous/error-prone for Fortran 77.)
Everything related to name mangling can be handled by
Gael Varoquaux wrote:
On Fri, Feb 26, 2010 at 07:23:54PM +0900, David Cournapeau wrote:
David Warde-Farley wrote:
My first
instinct would be to look for logdet, but I would also not expect such
a function to return the log determinant *and* the sign of the
determinant.
What about having
On Sat, Feb 27, 2010 at 2:44 AM, josef.p...@gmail.com wrote:
I think I mixed up some things then,
scipy 0.7.1 cython files should be regenerated with the latest cython
release so that it doesn't check the sizeof anymore.
Then, a scipy 0.7.1 build against numpy 1.3 would also work without
On Sat, Feb 27, 2010 at 11:59 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
quote
So here is how I see things in the near future for release:
- compile a simple binary installer for mac os x and windows (no need
for doc or multiple archs) from 1.4.x
- test this with the scipy binary
On Sat, Feb 27, 2010 at 3:43 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Yes that is clear. Would it make sense to first release scipy 0.7.2 though?
Then numpy 1.4.1 can be tested against it and we can be sure it works. The
other way around it's not possible to test.
Yes it is, you
Charles R Harris wrote:
On Wed, Feb 24, 2010 at 1:15 AM, David Cournapeau courn...@gmail.com
mailto:courn...@gmail.com wrote:
On Wed, Feb 24, 2010 at 1:51 PM, Charles R Harris
charlesr.har...@gmail.com mailto:charlesr.har...@gmail.com wrote:
Boy, that code
Kurt Smith wrote:
I'm the developer of fwrap. It is coming along, but will be at least
a month, likely two before the first release. (The main areas that
need some TLC are the fortran parser and the build system; the build
system will leverage numpy's distutils unless waf is easy to get
On Wed, Feb 24, 2010 at 1:51 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
Boy, that code is *old*, it still uses Numeric ;) I don't think it can
really be considered a test suite, it needs lotsa love and it needs to get
installed. Anyway, f2py with py3k turns out to have string
On Wed, Feb 24, 2010 at 5:19 PM, Pauli Virtanen p...@iki.fi wrote:
I don't think the situation is that bad with f2py. I suppose it will be
enough to erect unicode vs. Bytes barrier where the file i/o is done, and let
f2py work internally with unicode. Doesn't sound so bad, but I'd have to
Pauli Virtanen wrote:
The best alternative, imho, is not to use dict as a variable name at
all. We should make that change manually in SVN sources, both for Py2
and Py3.
Agreed - the changes should be put in the sources. Will do so tonight
after work unless someone beats me to it.
Grepping
Ralf Gommers wrote:
On Wed, Feb 24, 2010 at 3:42 PM, David Cournapeau courn...@gmail.com
mailto:courn...@gmail.com wrote:
So here is how I see things in the near future for release:
- compile a simple binary installer for mac os x and windows (no need
for doc or multiple
On Mon, Feb 22, 2010 at 11:27 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Hi David, did you find time to put those Atlas binaries somewhere?
I am putting them into numpy subversion as we speak (in vendor:
http://svn.scipy.org/svn/numpy/vendor).
cheers,
David
On Wed, Feb 24, 2010 at 11:05 AM, josef.p...@gmail.com wrote:
On Tue, Feb 23, 2010 at 8:52 PM, David Cournapeau courn...@gmail.com wrote:
On Mon, Feb 22, 2010 at 11:27 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Hi David, did you find time to put those Atlas binaries somewhere?
I
On Wed, Feb 24, 2010 at 11:04 AM, David Carmean d...@halibut.com wrote:
Does anyone use/build this stuff on RHEL 5.3+ (x64)? :) Seems not so much.
I'd like to use numpy (and PyTables) for a few tasks where it would be much
more efficient to have much of the processing performed on the
On Wed, Feb 10, 2010 at 3:12 PM, David Cournapeau courn...@gmail.com wrote:
Hi,
I am a bit puzzled by the protocol for long(a) where a is a scalar
array. For example, for a = np.float128(1), I was expecting long(a) to
call a.__long__, but it does not look like it is the case. int(a) does
On Wed, Feb 24, 2010 at 11:19 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Wed, Feb 24, 2010 at 9:52 AM, David Cournapeau courn...@gmail.com
wrote:
On Mon, Feb 22, 2010 at 11:27 AM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Hi David, did you find time to put those
On Mon, Feb 22, 2010 at 10:01 PM, Nils Wagner
nwag...@iam.uni-stuttgart.de wrote:
ar x test.a
gfortran -shared *.o -o libtest.so -lg2c
to build a shared library. The additional option -lg2c was
necessary due to an undefined symbol: s_cmp
You should avoid the -lg2c option at any cost if
On Sun, Feb 21, 2010 at 7:30 PM, Charles R Harris
charlesr.har...@gmail.com 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
On Mon, Feb 22, 2010 at 7:06 AM, Robert Kern robert.k...@gmail.com 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).
Nils Wagner wrote:
Hi all,
I have a static library (*.a) compiled by gfortran but no
source files.
How can I call routines from that library using python ?
Is there any kind of interface (.h, etc...) ? If this is a proprietary
library, there has to be something so that it can be called
Nils Wagner wrote:
On Thu, 18 Feb 2010 18:32:18 +0900
David Cournapeau da...@silveregg.co.jp wrote:
Nils Wagner wrote:
Hi all,
I have a static library (*.a) compiled by gfortran but
no
source files.
How can I call routines from that library using python ?
Is there any kind
Nils Wagner wrote:
How do I convert the .a library to a .so library ?
You first uncompress the .a into a temporary directory, with ar x on
Linux. Then, you group the .o together with gfortran -shared
$LIST_OF_OBJECT + a few options. You can also look at how Atlas does it
in its makefile.
As
On Thu, Feb 18, 2010 at 10:22 PM, Nils Wagner
nwag...@iam.uni-stuttgart.de wrote:
On Thu, 18 Feb 2010 11:55:07 +0100
Matthieu Brucher matthieu.bruc...@gmail.com wrote:
Ok I have extracted the *.o files from the static
library.
Applying the file command to the object files yields
ELF 64-bit
Dag Sverre Seljebotn wrote:
Well, I think one can make a static executable with C or Cython and
embed the Python interpreter.
Yes, it is possible, but I think it is fair to say that if you don't
know how to write a C extension, statically build numpy into python
would be daunting :)
David
Hi Travis,
On Wed, Feb 17, 2010 at 4:13 AM, Travis Oliphant oliph...@enthought.com wrote:
I've made the ABI changes I think are needed in the SVN trunk. Please
feel free to speak up if you have concerns or problems (and if you want to
change white-space, just do it...).
Great, thanks for
On Thu, Feb 18, 2010 at 8:24 AM, Touisteur EmporteUneVache
touist...@gmail.com wrote:
Hi,
I'm trying to install numpy on a WinXP system, on which I have no
administrative rights.
I think it is not possible to install NumPy for python 2.6 if you
don't have admin priviledges. I believe the root
Hi Wayne,
Wayne Watson wrote:
I normally use IDLE on Win, but recently needed to go to command prompt
to see all error messages. When I did, I was greeted by a host of
deprecation and Numpy messages before things got running. The program
otherwise functioned OK, after I found the problem I
markus.proel...@ifm.com wrote:
numpy-discussion-boun...@scipy.org schrieb am 17.02.2010 01:43:03:
markus.proel...@ifm.com wrote:
Hello,
is there a possibility to create a dll from a numpy code?
What do you want to create a dll for ? For distribution purpose, to hide
Sebastian Haase wrote:
On Mon, Feb 15, 2010 at 11:17 AM, Francesc Alted fal...@pytables.org wrote:
A Sunday 14 February 2010 13:40:17 Stéfan van der Walt escrigué:
On 14 February 2010 01:23, David Cournapeau courn...@gmail.com wrote:
I think that there should be absolutely no change whatsoever
David Cournapeau wrote:
It is always an ABI change, but is mostly backward compatible (which is
neither the case of matplotlib or scipy AFAIK).
This sentence does not make any sense: I meant that it is backward
compatible from an ABI POV, unless the structure PyArray_Array itself
On Tue, Feb 16, 2010 at 4:08 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
I was wondering about that. Why do we have a private include directory?
Would it make more sense to move it to core/include/numpy/private.
No, the whole point is to avoid other packages to include that by
On Tue, Feb 16, 2010 at 7:04 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Mon, Feb 15, 2010 at 2:46 PM, David Cournapeau courn...@gmail.com
wrote:
On Tue, Feb 16, 2010 at 4:08 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
I was wondering about that. Why do we have
Charles R Harris wrote:
On Mon, Feb 15, 2010 at 8:13 PM, David Cournapeau da...@silveregg.co.jp
mailto:da...@silveregg.co.jp wrote:
Charles R Harris wrote:
On Mon, Feb 15, 2010 at 3:58 PM, Charles R Harris
charlesr.har...@gmail.com mailto:charlesr.har
Charles R Harris wrote:
Just to be clear, there are *already* macros in the ndarrayobject.h file
that aren't py3k compatible. How do you propose to fix those?
I don't understand the connection with the public vs private issue. If
the py3k compatibility header is to be shared by several
On Sat, Feb 13, 2010 at 6:20 PM, Wolfgang Kerzendorf
wkerzend...@googlemail.com wrote:
Dear all,
I don't know much about parallel programming so I don't know how easy it is
to do that: When doing simple arrray operations like adding two arrays or
adding a number to the array, is numpy able
On Sun, Feb 14, 2010 at 1:24 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
Hi All,
Since there has been talk of deprecating the numarray and numeric
compatibility parts of numpy for the upcoming 2.0 release I thought maybe we
could consider a few other changes. First, numpy imports a
On Thu, Feb 11, 2010 at 4:52 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
...this should be purely technical IMO. There are well established rules
here:
Simple, eh. The version should be 2.0.
It would be simple if it were not for the obligation of getting it
soon, in a matter of
On Fri, Feb 12, 2010 at 7:38 AM, Travis Oliphant oliph...@enthought.com wrote:
I don't want to go the route of marking things experimental which David's
pro-1.5 vote seemed to advocate.
In that case, I prefer the new release to be marked as 2.0. There will
then be no new numpy 1.4.x, and
On Fri, Feb 12, 2010 at 2:04 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
2010/2/11 Stéfan van der Walt ste...@sun.ac.za
On 11 February 2010 15:38, Darren Dale dsdal...@gmail.com wrote:
2010/2/11 Stéfan van der Walt ste...@sun.ac.za:
On 11 February 2010 09:52, Charles R Harris
Robert Kern wrote:
On Thu, Feb 11, 2010 at 18:23, Charles R Harris
charlesr.har...@gmail.com wrote:
What about python version? Do we want to bump that up from 2.4?
Only if it were *really* necessary for the Python 3 port. Otherwise, I
would resist the urge.
Me too, on the basis that 2.4
Charles R Harris wrote:
I do think a 1.4.1 should be released without the datetime changes just
so there would be an updated version out there for slow adopters. We
wouldn't maintain it, though, it would be the end of the 1.x line.
We could make a source release - we could do it from the
josef.p...@gmail.com wrote:
So 1.4.1 wouldn't resolve the cython issue, packages that use cython
still would need to be refreshed and recompiled, but non-cython
packages should run without recompiling?
It is impossible to solve the cython issue in numpy. The only solution
is to regenerate
josef.p...@gmail.com wrote:
scipy is relatively easy to compile, I was thinking also of h5py,
pytables and pymc (b/c of pytables), none of them are importing with
numpy 1.4.0 because of the cython issue.
As I said, all of them will have to be regenerated with cython 0.12.1.
There is no other
Charles R Harris wrote:
On Thu, Feb 11, 2010 at 7:00 PM, David Cournapeau da...@silveregg.co.jp
mailto:da...@silveregg.co.jp wrote:
josef.p...@gmail.com mailto:josef.p...@gmail.com wrote:
scipy is relatively easy to compile, I was thinking also of h5py,
pytables
Charles R Harris wrote:
On Thu, Feb 11, 2010 at 8:12 PM, David Cournapeau da...@silveregg.co.jp
mailto:da...@silveregg.co.jp wrote:
Charles R Harris wrote:
On Thu, Feb 11, 2010 at 7:00 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp
Charles R Harris wrote:
I don't see any struct definitions there, it looks clean.
Any struct defined outside numpy/core/include is fine to change at will
as far as ABI is concerned anyway, so no need to check anything :)
David
___
Charles R Harris wrote:
On Thu, Feb 11, 2010 at 10:03 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp wrote:
Charles R Harris wrote:
On Thu, Feb 11, 2010 at 8:12 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp
Charles R Harris wrote:
Well, so it goes. I don't see any reasonable way to fix that. I wonder
how recent the cython size check is?
See related discussion on Cython ML - the problem is known for some
time. That's when cython fixed the error into a warning that I started
looking into the
On Thu, Feb 11, 2010 at 5:31 AM, Travis Oliphant oliph...@enthought.com wrote:
Christopher's argument that having a NumPy 2.0 sets expectations for keeping
1.4 and 2.0 is a strong one in my mind. The policy of coupling ABI and
version numbers makes less and less sense to me as I hear the
Hi,
I am a bit puzzled by the protocol for long(a) where a is a scalar
array. For example, for a = np.float128(1), I was expecting long(a) to
call a.__long__, but it does not look like it is the case. int(a) does
not call a.__int__ either. Where does the long conversion happen in
numpy for scalar
On Mon, Feb 8, 2010 at 10:23 AM, David Cournapeau da...@silveregg.co.jp wrote:
Jarrod Millman wrote:
Just
to be clear, I would prefer to see the ABI-breaking release be called
2.0. I don't see why we have to get the release out in three weeks,
though. I think it would be better to use
Bruce Southey wrote:
Not that I actually know much about it, but I thought that datetime is
a 'rather large feature' difference both in terms of functionality and
code. Definitely it will allow a unified date/time usage across
various scikits and other projects that have time functions.
Darren Dale wrote:
On Mon, Feb 8, 2010 at 7:25 PM, Robert Kern robert.k...@gmail.com wrote:
Here's the problem that I don't think many people appreciate: logical
arguments suck just as much as personal experience in answering these
questions. You can make perfectly structured arguments until
Sebastian Haase wrote:
Hello,
Regarding this post - is there a non official numpy package for
64bit windows? And how about SciPy ?
There are both unofficial individual binaries and EPD-based numpy/scipy.
One example of unofficial builds are there:
http://www.lfd.uci.edu/~gohlke/pythonlibs/
Jarrod Millman wrote:
Just
to be clear, I would prefer to see the ABI-breaking release be called
2.0. I don't see why we have to get the release out in three weeks,
though. I think it would be better to use this opportunity to take
some time to make sure we get it right.
As a compromise,
Darren Dale wrote:
Why can't this be called 2.0beta, with a __version__ like 1.9.96? I
don't understand the reluctance to follow numpy's own established
conventions.
Mostly because 2.0 conveys the idea that there are significant new
features, and because it would allow breaking the API as
Charles R Harris wrote:
On Sun, Feb 7, 2010 at 6:53 PM, David Cournapeau da...@silveregg.co.jp
mailto:da...@silveregg.co.jp wrote:
Darren Dale wrote:
Why can't this be called 2.0beta, with a __version__ like 1.9.96? I
don't understand the reluctance to follow
Christopher Barker wrote:
David Cournapeau wrote:
Not exactly, although it prevents from building Atlas for 64 bits. The
main issue is gcc/VS interoperabilities, especially for gfortran.
I thought you didn't need fortran for numpy?
No, but you need it for Scipy. And we have always produced
On Sat, Feb 6, 2010 at 4:07 PM, Travis Oliphant oliph...@enthought.com wrote:
Given all the discussions that have happened. I want to be clear
about my proposal. It is:
* 1.4.1 is an ABI break including datetime, hasobject, and a few place-
holders in the structures
* no future ABI
On Sat, Feb 6, 2010 at 10:29 PM, josef.p...@gmail.com wrote:
On Sat, Feb 6, 2010 at 8:07 AM, Francesc Alted fal...@pytables.org wrote:
A Saturday 06 February 2010 13:17:22 David Cournapeau escrigué:
On Sat, Feb 6, 2010 at 4:07 PM, Travis Oliphant oliph...@enthought.com
wrote:
I think
On Sat, Feb 6, 2010 at 10:36 PM, Darren Dale dsdal...@gmail.com wrote:
I don't understand why there is any debate about what to call a
release that breaks ABI compatibility.
Because it means datetime support will come late (in 2.0), and Travis
wanted to get it early in.
David
On Sat, Feb 6, 2010 at 10:54 PM, Vicente Soler Fraile
vicentesolerfra...@hotmail.com wrote:
Hello,
I try to install Numpy without success.
Windows 7
Python 2.6.4
Numpy numpy-1.4.0-win32-superpack-
python2.6.exe
Are you using a 32 bits python ? We only provide 32 bits
Pauli Virtanen wrote:
Making structures opaque is a bit worrying. As far as I understand, so
far the API has been nearly compatible with Numeric.
I assumed that we would simply give up the Numeric compatibility - does
it really matter for a NumPy which is at best out in 2011/2012 ? It is
René Dudfield wrote:
Also audiolab uses bindings to libsndfile - so you can open a number of
formats. However it is pretty new, so isn't packaged by distros(yet),
and there are no mac binaries(yet). It's probably the best way to go if
you can handle compiling it yourself and the
On Thu, Feb 4, 2010 at 3:46 PM, Travis Oliphant oliph...@enthought.com wrote:
If the issue is having too many releases that are .X releases, then let's
just slow that down.
The issue is not so much version numbering - I think keeping
compatibility between .X releases is slightly better because
On Thu, Feb 4, 2010 at 4:37 PM, Travis Oliphant oliph...@enthought.com wrote:
On Feb 4, 2010, at 12:59 AM, Charles R Harris wrote:
On Wed, Feb 3, 2010 at 11:48 PM, Travis Oliphant oliph...@enthought.com
wrote:
On Feb 2, 2010, at 11:59 PM, David Cournapeau wrote:
Travis Oliphant wrote
On Fri, Feb 5, 2010 at 5:15 AM, Pauli Virtanen p...@iki.fi wrote:
to, 2010-02-04 kello 12:09 -0700, Charles R Harris kirjoitti:
Realistically, I don't think Py3k will be ready by April-May. Fall is
probably doable and maybe there will be some things for a SOC person
to work on this summer.
Gerardo Gutierrez wrote:
Hello.
I'm working with audio signals with wavelet analisys, and I want to know
if someone has work with some audio capture (with the mic and through a
file) library so that I can get the time-series...
I think the easiest for now is to record things in a file,
On Thu, Jan 28, 2010 at 3:11 PM, David Cournapeau da...@silveregg.co.jp wrote:
Jankins wrote:
Yes. I am using scipy.sparse.linalg.eigen.arpack.
The exact output is:
/usr/local/lib/python2.6/dist-packages/scipy/sparse/linalg/eigen/arpack/_arpack.so
I need the output of ldd on this file
On Wed, Feb 3, 2010 at 5:38 PM, Peter Notebaert p...@telenet.be wrote:
From an extension? How to import numpy from there and then test if that
succeeded and that without any annoying message if possible...
One obvious solution would be to simply call PyImport_Import, something like:
#include
On Thu, Feb 4, 2010 at 2:16 AM, Christopher Barker
chris.bar...@noaa.gov wrote:
David Cournapeau wrote:
Just so that there is no confusion: it is only about removing it for
1.4.x, not about removing datetime altogether. It seems that datetime in
1.4.x has few users,
Of course it has few
Hi,
This is a follow-up of the discussion about ABI-breakage in Numpy
1.4.0. To sum it up, it is caused by the new datetime support, and it
seems difficult to fix without removing datetime support altogether
for the 1.4.x series.
Both Chuck and myself are in favor of removing the datetime
Peter Notebaert wrote:
How can I test if numpy is installed on the system from the extension so
that I do not active the numpy functionality and that it is still able
to use my extension, but then without numpy support?
Is there some reason why you cannot try to import numpy first to check
Christopher Barker wrote:
Travis Oliphant wrote:
I'm still pretty strongly against it.
Me too. I was close to posing a note today saying it was fine, but then
I sat down with a developer I'm working with, and he happened to mention
that he had rebuilt something or other to accommodate
Robert Kern wrote:
On Tue, Feb 2, 2010 at 20:23, Neil Martinsen-Burrell n...@wartburg.edu
wrote:
This is useful feature for more than just datetime
support and should be complete and useful at this time.
Couldn't this be kept independently of the datetime support ? At least
as far as the
Robert Kern wrote:
On Tue, Feb 2, 2010 at 21:08, David Cournapeau da...@silveregg.co.jp wrote:
Robert Kern wrote:
On Tue, Feb 2, 2010 at 20:23, Neil Martinsen-Burrell n...@wartburg.edu
wrote:
This is useful feature for more than just datetime
support and should be complete and useful
On Wed, Feb 3, 2010 at 12:23 PM, David Cournapeau da...@silveregg.co.jp wrote:
Sorry, my question was badly worded: besides the metadata pointer, is
there any other change related to the metadata infratructure which may
potentially change changes the publicly exported structures ? I wonder
Robert Kern wrote:
On Tue, Feb 2, 2010 at 22:46, David Cournapeau courn...@gmail.com wrote:
On Wed, Feb 3, 2010 at 12:23 PM, David Cournapeau da...@silveregg.co.jp
wrote:
Sorry, my question was badly worded: besides the metadata pointer, is
there any other change related to the metadata
Travis Oliphant wrote:
On Feb 2, 2010, at 11:46 PM, David Cournapeau wrote:
On Wed, Feb 3, 2010 at 12:23 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp wrote:
Sorry, my question was badly worded: besides the metadata pointer, is
there any other change related
Travis Oliphant wrote:
On Feb 2, 2010, at 8:53 PM, David Cournapeau wrote:
Travis Oliphant wrote:
I think we just signal the breakage in 1.4.1 and move forward. The
datetime is useful as a place-holder for data. Math on date-time
arrays
just doesn't work yet.I don't think
josef.p...@gmail.com wrote:
On Mon, Feb 1, 2010 at 12:09 PM, Keith Goodman kwgood...@gmail.com wrote:
2010/2/1 Ernest Adrogué eadro...@gmx.net:
Hello,
Consider the following code:
for j in range(5):
f = np.bincount(x[y == j])
It fails with MemoryError whenever y == j is all False
On Tue, Feb 2, 2010 at 1:05 PM, josef.p...@gmail.com wrote:
I think this could be considered as a correct answer, the count of any
integer is zero.
Maybe, but this shape is random - it would be different in different
conditions, as the length of the returned array is just some random
memory
Charles R Harris wrote:
In this case I would expect an empty input to be a programming error and
raising an error to be the right thing.
Ok, I fixed the code in the trunk to raise a ValueError in that case.
Changing to return an empty array would be easy,
cheers,
David
On Sun, Jan 31, 2010 at 11:43 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Hi,
With only a few changes (see diff below) to pavement.py I managed to build a
dmg installer. For this I used the Python in the bootstrap virtualenv
however, instead of the one in
Charles R Harris wrote:
On Thu, Jan 28, 2010 at 12:33 AM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp wrote:
Because Travis was against it when it was suggested last september or
so. And removing in 1.4.x a feature introduced in 1.4.0 is weird
Bruce Southey wrote:
On Tue, Jan 26, 2010 at 11:02 PM, David Cournapeau
da...@silveregg.co.jp wrote:
Charles R Harris wrote:
Whatever we do, it would be good to figure out some way to avoid this
problem in the future. We could hide access to the array, for instance.
But again, that would
josef.p...@gmail.com wrote:
Can we/someone add a warning on the front page http://scipy.org/
(maybe under news for numpy download) about incompatibility of the
binaries on sourceforge of scipy =0.7.1 with numpy 1.4.0 ?
It seems that it will be quite difficult to fix the issue without
removing
Alan G Isaac wrote:
On 1/27/2010 7:57 PM, David Cournapeau wrote:
Guido explicitly asked not to break compatibility while staying under
py3k, so we should try to do it once numpy has been ported to py3k (e.g.
if numpy 1.5 still is not py3k compatible, do a 1.6 before a 2.0 -
iterate
josef.p...@gmail.com wrote:
If you are also able to provide new scipy binaries, then at least the
combination would be usable without intermittent import errors and
crashes.
The problem is that the new scipy would not be usable with older numpy.
That's why breaking the ABI is so painful.
Alan G Isaac wrote:
On 1/27/2010 7:57 PM, David Cournapeau wrote:
Guido explicitly asked not to break compatibility while staying under
py3k, so we should try to do it once numpy has been ported to py3k (e.g.
if numpy 1.5 still is not py3k compatible, do a 1.6 before a 2.0 -
iterate
Jankins wrote:
Dear all,
I am using scipy '0.8.0.dev6120'. And the scipy.sparse.eigen function
always produces error message.
_Description:_
linalg.eigen(A, k=6, M=None, sigma=None, which='LM', v0=None,
ncv=None, maxiter=None, tol=0, return_eigenvectors=True)_
Could you provide
Jankins wrote:
I tried on Ubuntu 9.10-32bit, gcc version 4.4.1, . Here is the
information of show_config():
Sorry, I forgot an additional information, the exact atlas you are
using. For example, assuming scipy is installed in /usr/local, I would
need the output of
Alan G Isaac wrote:
On 1/27/2010 8:56 PM, David Cournapeau wrote:
one could make the argument that releasing the API would avoid
having to port numpy twice (first to py3k with say numpy 1.5.0, then
to the new API for numpy 2.0). But I am not sure it is a big change in
practice ?
OK, I
Jankins wrote:
Yes. I am using scipy.sparse.linalg.eigen.arpack.
The exact output is:
/usr/local/lib/python2.6/dist-packages/scipy/sparse/linalg/eigen/arpack/_arpack.so
I need the output of ldd on this file, actually, i.e the output of ldd
Charles R Harris wrote:
On Wed, Jan 27, 2010 at 6:20 PM, David Cournapeau da...@silveregg.co.jp
mailto:da...@silveregg.co.jp wrote:
josef.p...@gmail.com mailto:josef.p...@gmail.com wrote:
Can we/someone add a warning on the front page http://scipy.org/
(maybe under news
Charles R Harris wrote:
On Wed, Jan 27, 2010 at 11:39 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp wrote:
Charles R Harris wrote:
On Wed, Jan 27, 2010 at 6:20 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp
501 - 600 of 2096 matches
Mail list logo
