Hi, I am running Debian GNU/Linux 8 on a BBB. I have been trying to download numpy but when I use pip install numpy the installation process crashes.
I’ve been using the following process: http://docs.scipy.org/doc/numpy-1.10.1/user/install.html#id6
root@beaglebone:~# python setup.py install
python: can’t open file ‘setup.py’: [Errno 2] No such file or directory
root@beaglebone:~#
root@beaglebone:~# python setup.py build_ext --inplace
python: can’t open file ‘setup.py’: [Errno 2] No such file or directory
root@beaglebone:~#
Your help appreciated!
On Thu, 29 Sep 2016 15:35:57 -0700 (PDT), Lidia Toscano
<lidia.toscano@gmail.com> declaimed the
following:
Hi, I am running Debian GNU/Linux 8 on a BBB. I have been trying to
download numpy but when I use pip install numpy the installation process
crashes.
So what error messages does it generate?
root@beaglebone:~# python setup.py install
python: can't open file 'setup.py': [Errno 2] No such file or directory
root@beaglebone:~#
No surprise if you don't have the download in the first place... Or
extracted the contents of the download into a directory... OR CD'd into the
directory with the package contents (you're still in the root home
directory -- at the least the package should be in a subdirectory
somewhere)
$ ls .
Would determine if the script is in the current working directory.
Now, that is an interesting thought. When I go out and look for instructions on downloading packages, the instructions usually only say to
pip install . . . . whatever. They never specify sub directories. This is somewhat confusing for the newbies like me because installations just do their thing and I never really know where to find the installed packages. If I save all of the script on the screen, I can then look for the path but this is a tedious way of “knowing” where packages are installed.
As it turns out, I input the instructions again and left the laptop for a long while and then . . . ta da! numpy was installed. Because it took so long to install, I thought it had crashed. Apparently it was still working in the background.
Thanks for all of your assistance