-
-
Notifications
You must be signed in to change notification settings - Fork 381
Configuration Problems and Solutions
Despite our best efforts to ensure that bootcamp attendees configure their computers ahead of time, installation and configuration issues pop up frequently during bootcamps. This page collates common configuration problems encountered by instructors and presents their solutions.
To instructors: Please feel free to edit this page to add new problems and solutions to the appropriate sections as you encounter them. The only requirement is that you should have only add a problem once you have identified and confirmed a solution that at least worked for the cases that you encountered personally. If you encounter a problem that you don't know how to solve, please raise it in an issue in the bc
repo so that the community can find a resolution.
Windows (Git Bash)
-
None of the bash commands seem to work, although the student opened "Git Bash" and the command window is open
- Ensure that the student has run the program
mysys
and notgit-cmd
- the latter will not open the bash emulator environment.
- Ensure that the student has run the program
-
User has created/saved files and doesn't know where they are
- Have users run
cd
after opening Git Bash and before doing anything else - this will place users in a home directory with Desktop as a subdirectory.cd
thencd Desktop
will place users on their Desktop. (#56)
- Have users run
-
Copy/paste doesn't work in the command window
- To copy, right click the title bar and find "Mark" in the menu. Then you can use the mouse to select text - anything you select is automatically copied. There's a menu item for paste, but the "Insert" key is a shortcut. (#140)
All
-
Command
ipython notebook
fails withipython not found
-type error- Very likely that Canopy or Anaconda did not properly append path to Python installation on system path (on Canopy, this easily occurs if students do not open GUI after installation or if they accidentally select "No" when asked if they want to make Canopy the default Python environment). To fix, export path in .bash_profile. On a Mac using Canopy, command is
PATH=/Users/<username>/Library/Enthought/Canopy_64bit/User/bin:$PATH; export PATH
- Very likely that Canopy or Anaconda did not properly append path to Python installation on system path (on Canopy, this easily occurs if students do not open GUI after installation or if they accidentally select "No" when asked if they want to make Canopy the default Python environment). To fix, export path in .bash_profile. On a Mac using Canopy, command is
-
Imports of scientific Python packages fails from a command line interpreter or script (i.e.,
python myfile.py
) even though user installed Canopy/Anaconda- Ensure that path to Canopy/Anaconda python comes before path to system Python (see above). Check with
which python
and make sure it is Canopy/Anaconda version.
- Ensure that path to Canopy/Anaconda python comes before path to system Python (see above). Check with
-
IPython notebook appears to be running but no output is shown after cells are run
- Ensure that Ad blocker extensions are not active in browser
- If all else fails and user has Canopy, notebooks can be opened and run directly from Canopy GUI
Windows (Git Bash)
-
User is prompted to enter email address on first commit
- Appears to be a bug in 1.8.4, as user is prompted even if global config is set with email address. This should only occur on first commit.
-
git push
to a Github repo fails with errorcould not read Username for https:...: No such device or address
- Bug in Git Bash 1.8.5 - have users install 1.8.4. (#234)
- This appears to be an issue with the default credential store. Changing the credential store will solve the problem, but I don't see the right command in a quick Google search. I'll look again later...
Linux
-
Permission denied (public key) on pushing to Github
- Has several causes and thus several solutions. Github has a list, in a nutshell:
- Don't use sudo (and check whether the permissions for SSH keys are correct)
- Connection problems or weird routing problems:
ssh -vT [email protected]
should printgithub.com
and port 22 - Connect only as user
git
- Check whether
ssh-add -l
prints a key, if not, create one - Check whether
ssh-keygen -lf ~/.ssh/id_rsa.pub
prints several keys, and check which one GitHub uses in the account settings - You can always troubleshoot more using
ssh -vT [email protected]
- Has several causes and thus several solutions. Github has a list, in a nutshell: