For those of you who typically do all your Python dev work on a Mac or Linux and are now faced with teaching eager NICAR16 attendees on a Windows computer, fear not. We've taken steps this year to provide Python virtual environments for each scheduled class that work fine with both the standard Windows command prompt or Windows PowerShell.
The path to the Python virtual environments on the lab computers:
C:\venvs\
#NICAR16 Hands-on Teacher Information
First, thank you so much for sharing your time and expertise. This conference wouldn't be possible without your commitment to teach. We truly appreciate your help!
Unless specifically noted as having registration required, all hands-on classes are first-come, first-served. Each hands-on room is equipped with 24 student computers (except for Mattie Silks, which has 30) and one for the presenter. IRE staff will limit attendance if the room becomes too crowded; this is at the hotel's request to comply with local fire code. For the same reason, the rooms will already be set with the maximum number of chairs allowed.
For the most part, everything will be done using OS X's Terminal.
We need to install the following (in this order) to get up and running:
From a comment by user laymonk...
The simple fix involves just cd'ing into the virtualenv, and deleting all the stale links to the upgraded python by running:
find . -type l -delete
(return to home dir)
.. and then re-installing your virtualenv:
mkvirtualenv venv-name
(Last updated 6/20/17)
| http://azaleasays.com/2014/08/25/homebrew-warnings-about-unbrewed-dylibs-installed-by-r/ |