Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25938 - [numpy+scipy] python 3.2 and soabi compatibility
Attached to Project:
Arch Linux
Opened by Andrzej Giniewicz (Giniu) - Friday, 09 September 2011, 19:58 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 21 December 2011, 21:15 GMT
Opened by Andrzej Giniewicz (Giniu) - Friday, 09 September 2011, 19:58 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 21 December 2011, 21:15 GMT
|
DetailsDue to http://www.python.org/dev/peps/pep-3149/ distutils.sysconfig.get_config_vars('SO') behaves differently on Python 3.2 that is default on Arch now. This leads to situation when Python 3 packages using numpy cannot find dynamic libraries used trough it. For example scipy requires symlinks:
ln -sf /usr/lib/liblapack.so liblapack.cpython-32mu.so ln -sf /usr/lib/libblas.so libblas.cpython-32mu.so The symlinks in there were created, because no easy solution existed at the time. But this isn't good solution in the long run, especially because the bug can touch other Python 3 packages requiring numpy, either on build or runtime/testing. The proper fix is implemented in NumPy 1.6.1 that is released and flagged for longer than month now. Update to numpy package is as simple as change from 1.6.0 to 1.6.1 and generating new md5sum. While update is trivial, I believe the bug is not and should be taken care of either by updating numpy to 1.6.1, or by backporting the patch from 1.6.1 to 1.6.0 if for any reason update isn't desired. At same time workaround earlier applied to scipy should be removed. |
This task depends upon
Closed by Ionut Biru (wonder)
Wednesday, 21 December 2011, 21:15 GMT
Reason for closing: Fixed
Additional comments about closing: python-numpy 1.6.1-1
python-scipy 0.10.0-1
python2-numpy 1.6.1-1
python2-scipy 0.10.0-1
Wednesday, 21 December 2011, 21:15 GMT
Reason for closing: Fixed
Additional comments about closing: python-numpy 1.6.1-1
python-scipy 0.10.0-1
python2-numpy 1.6.1-1
python2-scipy 0.10.0-1
Comment by Rémy Oudompheng (remyoudompheng) -
Saturday, 10 September 2011, 07:23 GMT
Please don't report outdated packages in the bug tracker.
Comment by Andrzej Giniewicz (Giniu) -
Saturday, 10 September 2011, 10:00 GMT
I don't care much when it is updated - but I'd like this bug to disappear, so I reported it. So this isn't "please update", but please make sure that http://projects.scipy.org/numpy/attachment/ticket/1749/soabi_pep3149.patch is applied and numpy is working with Python 3.2.
Comment by Andrzej Giniewicz (Giniu) -
Saturday, 17 September 2011, 08:49 GMT
I just noticed that the numpy side of issue is fixed in numpy package as of today, it remains to remove the workaround from scipy package now.
Comment by Thomas Dziedzic (tomd123) -
Wednesday, 21 December 2011, 21:08 GMT
Since this has been fixed in the latest numpy and I removed the scipy workaround with the 0.10.0 bump, we can safely close this bug