Description of problem: Numeric.reshape raises ValueError exception when newshape has more than 1 dimension. This problem is observed only on x86_64 machines. Version-Release number of selected component (if applicable): python-2.4.3-24.el5 python-numeric-23.7-2.2.2 How reproducible: Only reproducible on x86_64. 32-bit machines are correct. Steps to Reproduce: On a RHEL 5 x86_64 machine: [root@dhcp6-118 ~]# python Python 2.4.3 (#1, Sep 17 2008, 16:07:08) [GCC 4.1.2 20071124 (Red Hat 4.1.2-41)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import Numeric >>> print Numeric.__version__ 23.7 >>> a = Numeric.array([x for x in xrange(20)]) >>> Numeric.reshape(a, (4,5)) Traceback (most recent call last): File "<stdin>", line 1, in ? ValueError: total size of new array must be unchanged >>> Expected results: As seen on a 32 bit RHEL 5 machine : >>> Numeric.reshape(a, (4,5)) array([[ 0, 1, 2, 3, 4], [ 5, 6, 7, 8, 9], [10, 11, 12, 13, 14], [15, 16, 17, 18, 19]]) Additional info: Bug was fixed in Fedora in bug 192895, by rebasing to 24.2. Customer would prefer that solution for RHEL if possible. 24.2 was released in 2005.
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
Will python-numeric be updated in RHEL6 to the later version? Or at least remove the buggy version? Thanks.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Created attachment 438212 [details] Patch for issue
This bug was fixed by the patch for Bug 703160, which was just a dup of this bug. This bug can be closed based on http://rhn.redhat.com/errata/RHBA-2011-0508.html