From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RzHeL-00034L-8b for garchives@archives.gentoo.org; Mon, 20 Feb 2012 01:02:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AD281E0C21 for ; Mon, 20 Feb 2012 01:02:40 +0000 (UTC) Received: from mxi2.callplus.net.nz (mx194.callplus.net.nz [202.180.66.194]) by pigeon.gentoo.org (Postfix) with ESMTP id E7EC1E0CF6 for ; Mon, 20 Feb 2012 00:28:50 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap0EAPaSQU/KtEIE/2dsb2JhbABEhRKuHoIdbh0CFQIPAoENh26ZV44NkQCBL4pMBAIKBQEGAgEJBwUBAQECAQUFBQ0GFAMCg2A0JgsGgXeBFgSVNpME X-IronPort-AV: E=Sophos;i="4.73,447,1325415600"; d="scan'208";a="243634699" Received: from wmsrv3.tranzpeer.net (HELO localhost) ([202.180.66.4]) by ismtp2.tranzpeer.net with ESMTP; 20 Feb 2012 13:28:48 +1300 Received: from 202.36.179.68 ([202.36.179.68]) by webmail.slingshot.co.nz (Horde) with HTTP for ; Mon, 20 Feb 2012 13:21:07 +1300 Message-ID: <20120220132107.2sgkccsog880g4c4@webmail.slingshot.co.nz> Date: Mon, 20 Feb 2012 13:21:07 +1300 From: fbissey@slingshot.co.nz To: gentoo-science@lists.gentoo.org Subject: [gentoo-science] [sage-on-gentoo] python 3.2 + numpy-1.5.1 + scipy = hurt Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-science@lists.gentoo.org Reply-to: gentoo-science@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 202.36.179.68 X-Archives-Salt: d1b73744-e61a-441b-9caf-5e8c83cc9206 X-Archives-Hash: 4053f0693abf94db08095fe338cd447b Ok folks so python 3.2 has hit stable and a few problem that were plaguing people using ~arch are now hitting us squarely in the face. Namely you cannot emerge scipy (0.9/0.10) with python 3.2 and numpy-.1.5.1... Using numpy-.16 is kind of functional... Coercion of sage numerical type to available numpy numerical type is broken - in a strange way. Numpy functions coded in C are not broken: numpy.arange for example. Numpy functions coded in python are broken: numpy.linspace for example. For a long time I didn't quite grasp the problem in http://trac.sagemath.org/sage_trac/ticket/11334 But now with these details I think there is something either broken or undocumented in numpy-1.6.x. Moving sage to numpy 1.6 will break doctest and will require you to do explicit casting if you want to do numerical stuff with numpy from sage. So I propose that we move sage to numpy 1.6 with a warning to users about the problems encountered. The other solution is to tell people not use python 3.2 for scipy. This could be done by adding a file in /etc/portage/env/sci-libs/ called scipy with just the line: USE_PYTHON="2.7" I am using the later right now. Other suggestions welcome. Francois