Same problem in karmic 9.10 x64 (Numeric 24.2, python 2.6.4 and 2.5.4). It may be a 64/32bit problem, since it doesn't happen on my 32bit 9.04 machines (don't have a 32bit 9.10 install to test)
The problem is that an unspecified stride gets set to 0 under some circumstances. Here's a minimal fragment to show the problem: >>> Import Numeric, numpy >>> Numeric.arange(1,5)[2:] >>> zeros((0,), 'l') >>> numpy.arange(1,5)[2:] array([3, 4]) >>> range(1,5)[2:] [3, 4] numpy and builtin range show the correct behavior, Numeric's wrong. This is a fairly serious problem for people using Numeric for number crunching.. -- Some slices of Numeric.array are wrong https://bugs.launchpad.net/bugs/263781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
