public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
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
Date: Mon, 20 Feb 2012 13:21:07 +1300	[thread overview]
Message-ID: <20120220132107.2sgkccsog880g4c4@webmail.slingshot.co.nz> (raw)

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




                 reply	other threads:[~2012-02-20  1:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120220132107.2sgkccsog880g4c4@webmail.slingshot.co.nz \
    --to=fbissey@slingshot.co.nz \
    --cc=gentoo-science@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox