Hi Francesc, Logging directly to Source Forge sounds like a good idea, but as you say, only for what appear to be corner cases with minor impact. I think other bugs should be posted here. If the numarray bug chatter is annoying people, I hope they speak up now. If a bug isn't resolved in a few days by posting here, it should be logged on Source Forge to prevent becoming lost. There are multiple "trackers" on Source Forge. numarray bugs belong in the "Numarray Bugs" tracker, but generally they are "mis-filed" in the "Bugs" tracker which more properly belongs to Numeric. Bug reports can be moved between these two trackers with little effort. Todd On Tue, 2003-12-16 at 05:01, Francesc Alted wrote:

Hi,

Conversion between Numeric arrays and numarray fails for zero-sized Numeric arrays:

...

...

...

numarray.array(Numeric.zeros((0,), 'd')) Traceback (most recent call last): File "<stdin>", line 1, in ? File "/usr/local/lib/python2.3/site-packages/numarray/numarraycore.py", line 301, in array raise ValueError("Unknown input type") ValueError: Unknown input type

but this works:

...

...

...

numarray.array(Numeric.zeros((1,), 'd')) array([ 0.])

I'm wondering if it would be better to log a bug of the SF project site for such a no too grave bugs rather than report them to the list, although it seems to me that people only logs Numeric reports on the SF project. Would it be correct using the same place for numarray reports as well?

Cheers, -- Todd Miller <jmiller@stsci.edu>