Package Details: python-scipy-mkl 1.3.1-1

Git Clone URL: (read-only)
Package Base: python-scipy-mkl
Description: SciPy is open-source software for mathematics, science, and engineering.
Upstream URL:
Licenses: BSD
Conflicts: python-scipy
Provides: python-scipy=1.3.1
Submitter: bred
Maintainer: petronny
Last Packager: petronny
Votes: 27
Popularity: 0.059002
First Submitted: 2012-09-06 19:34
Last Updated: 2019-08-15 13:08

Required by (298)

Sources (2)

Pinned Comments

petronny commented on 2019-06-26 08:47

Prebuilt binaries of this package can be found in arch4edu.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

L0ric0 commented on 2018-07-06 18:02

Hi, the fails the sha256sums check.

Please update the checksums.

bred commented on 2018-07-06 17:46

@petronny TNX !!! :)

petronny commented on 2018-07-04 04:46

Hi, after intel-parallel-studio-xe has been updated to 2018.3.222, I finally figured out how to build this package and update it to 1.1.0.

Here is my PKGBUILD and please update it.

PS. I think we should use a patch rather than the sed command in this case. Please update my PKGBUILD.

alleut commented on 2018-02-08 19:15

How to tell builder what compiler to use?

Found executable /opt/intel/compilers_and_libraries_2018.1.163/linux/bin/intel64/icc customize IntelEM64TFCompiler
Found executable /opt/intel/compilers_and_libraries_2018.1.163/linux/bin/intel64/ifort
Traceback (most recent call last):
File "", line 418, in <module>setup_package()
File "", line 414, in setup_packagesetup(**metadata)
File "/usr/lib/python3.6/site-packages/numpy/distutils/", line 169, in setupreturn old_setup(**new_attr)
File "/usr/lib/python3.6/site-packages/setuptools/", line 129, in setupreturn distutils.core.setup(**attrs)
File "/usr/lib/python3.6/distutils/", line 148, in setupdist.run_commands()
File "/usr/lib/python3.6/distutils/", line 955, in run_commandsself.run_command(cmd)
File "/usr/lib/python3.6/distutils/", line 974, in
File "/usr/lib/python3.6/site-packages/numpy/distutils/command/", line 75, in runself.run_command('build_src')
File "/usr/lib/python3.6/distutils/", line 313, in run_commandself.distribution.run_command(command)
File "/usr/lib/python3.6/distutils/", line 974, in
File "/usr/lib/python3.6/site-packages/numpy/distutils/command/", line 148, in runself.build_sources()
File "/usr/lib/python3.6/site-packages/numpy/distutils/command/", line 165, in build_sourcesself.build_extension_sources(ext)
File "/usr/lib/python3.6/site-packages/numpy/distutils/command/", line 324, in build_extension_sourcessources = self.generate_sources(sources, ext)
File "/usr/lib/python3.6/site-packages/numpy/distutils/command/", line 377, in generate_sourcessource = func(extension, build_dir)
File "scipy/_lib/", line 32, in get_messagestream_configif config_cmd.check_func('open_memstream', decl=True, call=True):
File "/usr/lib/python3.6/site-packages/numpy/distutils/command/", line 312, in check_funcself._check_compiler()
File "/usr/lib/python3.6/site-packages/numpy/distutils/command/", line 83, in _check_compilerself.fcompiler.customize(self.distribution)
File "/usr/lib/python3.6/site-packages/numpy/distutils/fcompiler/", line 499, in customizeget_flags('opt', oflags)
File "/usr/lib/python3.6/site-packages/numpy/distutils/fcompiler/", line 490, in get_flagsflags.extend(getattr(self.flag_vars, tag))
File "/usr/lib/python3.6/site-packages/numpy/distutils/", line 39, in __getattr__return self._get_var(name, conf_desc)
File "/usr/lib/python3.6/site-packages/numpy/distutils/", line 53, in _get_varvar = self._hook_handler(name, hook)
File "/usr/lib/python3.6/site-packages/numpy/distutils/fcompiler/", line 697, in _environment_hookreturn hook()
File "/usr/lib/python3.6/site-packages/numpy/distutils/fcompiler/", line 125, in get_flags_optv = self.get_version()
File "/usr/lib/python3.6/site-packages/numpy/distutils/fcompiler/", line 430, in get_versionraise CompilerNotFound()

bred commented on 2017-12-26 11:40

The bug in icc 18.0.0 has been fixed in the icc 18.0.1.

If you are still using the icc 18.0.0 uncomment the lines 62 and 79. and comment out the lines 61 and 78.

hcb commented on 2017-12-04 09:57

Replacing .. with ${srcdir} worked for me:

# copy python3 build files
cp ${srcdir}/ scipy-${pkgver}

# copy python2 build files
cp -r scipy-${pkgver} scipy-${pkgver}-py2
cp ${srcdir}/ scipy-${pkgver}-py2

gwaterst commented on 2017-11-08 15:09

Yes, it probably is the BUILDDIR variable that changes the behaviour.

According to the documentation a proper solution would be to put the copy processes into a prepare() section and use $srcdir as target folder:

prepare() {
# copy python3 build files
cp $srcdir/scipy-${pkgver}

# copy python2 build files
cp -r $srcdir/scipy-${pkgver} srcdir/scipy-${pkgver}-py2
cp $srcdir/scipy-${pkgver}-py2

An alternative would be to use the $startdir variable instead of '../'

arvidsaur commented on 2017-11-08 14:01

@gwatterst well that did not work for me, could it be because I have set "BUILDDIR=/tmp/makepkg" ? this is the first pkgbuild that has failed for me with that setting, removing "../" worked for me.

gwaterst commented on 2017-11-08 12:39

No, that should be correct, since "makepkg will change the current directory to $srcdir before executing the build()" (from the wiki page).

So, during build() we already are in src/ and the 2 shell scripts are still in ../

However, one might consider copying all the files during prepare()

arvidsaur commented on 2017-11-08 07:28

I think there is a minor error in the PKGBUILD it should be
"cp scipy-${pkgver}" instead of "cp ../ scipy-${pkgver}" same for the python2 file.