From d6a7000aee1613564bdacab31bdb45236eb73ce6 Mon Sep 17 00:00:00 2001 From: Erik Schnetter Date: Thu, 16 Mar 2017 10:45:09 -0400 Subject: py-numpy: Correct typos in comment (#3462) --- var/spack/repos/builtin/packages/py-numpy/package.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'var') diff --git a/var/spack/repos/builtin/packages/py-numpy/package.py b/var/spack/repos/builtin/packages/py-numpy/package.py index 3571ff1f15..3ed0d0bdb5 100644 --- a/var/spack/repos/builtin/packages/py-numpy/package.py +++ b/var/spack/repos/builtin/packages/py-numpy/package.py @@ -96,11 +96,11 @@ class PyNumpy(PythonPackage): # FIXME: as of @1.11.2, numpy does not work with separately # specified threading and interface layers. A workaround is # a terribly bad idea to use mkl_rt. In this case Spack - # won't no longer be able to guarantee that one and the + # will no longer be able to guarantee that one and the # same variant of Blas/Lapack (32/64bit, threaded/serial) # is used within the DAG. This may lead to a lot of # hard-to-debug segmentation faults on user's side. Users - # may also break working installation by (unconciously) + # may also break working installation by (unconsciously) # setting environment variable to switch between different # interface and threading layers dynamically. From this # perspective it is no different from throwing away RPATH's -- cgit v1.2.3-60-g2f50