1 |
Ok folks so python 3.2 has hit stable and a few problem that were plaguing |
2 |
people using ~arch are now hitting us squarely in the face. |
3 |
Namely you cannot emerge scipy (0.9/0.10) with python 3.2 and numpy-.1.5.1... |
4 |
|
5 |
Using numpy-.16 is kind of functional... Coercion of sage numerical type to |
6 |
available numpy numerical type is broken - in a strange way. |
7 |
Numpy functions coded in C are not broken: numpy.arange for example. |
8 |
Numpy functions coded in python are broken: numpy.linspace for example. |
9 |
|
10 |
For a long time I didn't quite grasp the problem in |
11 |
http://trac.sagemath.org/sage_trac/ticket/11334 |
12 |
|
13 |
But now with these details I think there is something either broken or |
14 |
undocumented in numpy-1.6.x. |
15 |
|
16 |
Moving sage to numpy 1.6 will break doctest and will require you to do explicit |
17 |
casting if you want to do numerical stuff with numpy from sage. |
18 |
|
19 |
So I propose that we move sage to numpy 1.6 with a warning to users about the |
20 |
problems encountered. |
21 |
|
22 |
The other solution is to tell people not use python 3.2 for scipy. This could be |
23 |
done by adding a file in /etc/portage/env/sci-libs/ called scipy with just the |
24 |
line: |
25 |
USE_PYTHON="2.7" |
26 |
|
27 |
I am using the later right now. Other suggestions welcome. |
28 |
|
29 |
Francois |