Working Locally Guide: Select your operating system and follow the guides or videos below to learn how to set yourself up to work locally! If you run into any issues, post to Ed Discussion under the logistic tag!

These steps are to install/ensure the correct version of python and pytest are installed locally on your computer.

  1. In terminal, run python --version to get the python version you are running. If it says 3.7.3 you are good to go, if not:
    • Run python3 --version.
      • If you don't get 3.7.3 install python 3.7.3
      • If you get 3.7.3 you must type python3 to run anything, or setup an alias as shown below.
    • Setting up an alias:
      • What an alias is: a (usually short) command that the shell (terminal) translates into another (usually longer) command. For example, if instead of typing cs0160_install you wanted to type i you could set up an alias so i was interpreted as cs0160_install in your terminal
      • We are going to make an alias so python is interpreted as python3 by default.
        Note: If your shell is zsh (look at top of terminal and see if it says bash or zsh), you should be modifying the .zshrc file instead of the .bash_profile.
        • In your local terminal (not over ssh) type open -e ~/.bash_profile if a file does not exist type touch ~/.bash_profile first and then open -e ~/.bash_profile
        • Then add the following line to the end of the document: alias python="python3.7"
    • Now run source ~/.bash_profile (essentially refreshing your terminal) and then run python --version to confirm that you've correctly set the version to python 3. It should now say: 3.7.3
  2. Make sure pytest is installed by running python and then in the python shell run import pytest If you get no errors doing this, you are fine, If not:
    • Type exit() to exit the python shell
    • Run pip3.7 install -U pytest
    • Now go back into the python shell by running python and then in the shell write import pytest once more to confirm it is installed by making sure you no longer have errors

Important note: if you have python 3.7.3, then you're good to go. If not:

  1. Follow this link to download python 3.7.3
  2. To determine which download you want to do, go into system info and look at system type.
    • If it is x64 you want the x86-64 executable installer
    • If it is x86 you want the x86 installer
  3. Once that downloads open the executable.
  4. There will be a box in at the bottom that says add python 3.7 to path, make sure this box is checked.
  5. Press install now. Python 3.7.3 takes about 30 seconds to a minute to download
  6. Once the download is complete, open either powershell or cmd prompt and type python --version, you should see Python 3.7.3
  7. Continue only if NOTHING or the WRONG version comes up:
    • If nothing comes up, or you receive a different version, python probably hasn’t been added to the path. To add it to the path manually, press the windows key and type edit the system environment variables
    • The bottom right hand corner will have an option “environment variables” that you should click on
    • In user variables, click “path” then edit.
    • You will be adding two new lines. Press new, then add

        C:\Users\\AppData\Local\Programs\Python\Python37\Scripts\

        C:\Users\\AppData\Local\Programs\Python\Python37\

  8. Make sure pytest is installed by running python and then in the python shell run import pytest If you get no errors doing this, you are fine, If not:
    • Type exit() to exit the python shell
    • Run pip3.7 install pytest
    • Now go back into the python shell by running python and then in the shell write import pytest once more to confirm it is installed by making sure you no longer have errors

These steps are to make sure the correct version of java is installed on your local computer. You must do this before doing your local Eclipse setup!

  1. In terminal type, java -version and check that the number following “java version” starts with 1.8 or 8, if it does, you're done! If not, read on.
  2. Visit this website, and download the program that corresponds with your computer (ie Mac, Linux, or Windows), and download the 64-bit version. If you don't have an Oracle account and don't want to make one, you can also download jdk8 here. That said, we highly recommend making an Oracle account -- you'll be able to download jdk8 directly from the source, and it may come in handy later on.
  3. In your terminal type java -version again to check if the version is now 1.8 or 8, and if it is not type the following into your terminal:
    • cd /Library/Java/JavaVirtualMachines
    • ls you should see at least one file that starts with “jdk”, look for the file whose number starts with 1.8 or 8 and copy the file name. The full copied file name should look something like jdk.1.8.0_181.jdk
    • cd ~
    • open -e .bash_profile
    • if it says no bash_profile file exists, type touch .bash_profile then open -e.bash_profile
    • Add the below code line to the end of your .bash_profile file. However, fill in the part <fill me in> with the copied file name from the second bullet point:
      • export JAVA_HOME=/Library/Java/JavaVirtualMachines/<fill me in>/Contents/Home
  4. Now type java -version to make sure the correct version of java is being used
  1. Type java -version to see your version of java, if it is 1.8, you’re done
  2. Visit this website, and download the program that corresponds with your computer (ie Mac, Linux, or Windows). If you don't have an Oracle account and don't want to make one, you can also download jdk8 here. That said, we highly recommend making an Oracle account -- you'll be able to download jdk8 directly from the source, and it may come in handy later on.
  3. Follow the install setup provided from the download until it completes
  4. Check to make sure the path of java has been updated by running java -version in powershell or cmd prompt. If nothing or the wrong version comes up, continue following these instructions
  5. To add it to the path manually, press the windows key and type edit the system environment variables
  6. The bottom right hand corner will have an option “environment variables” that you should click on
  7. In system variables, click “path” then edit. You will be adding 1 line, press new, then add: C:\Program Files\Java\jdk1.8.0_231\bin
    Note: To make sure this runs properly, make sure this new line added to the path goes to the top, you can do so by clicking on the newly added line and pressing “move up” until it is at the top.

Follow this guide.
Follow this guide.

There are many different IDEs that work for writing in python (IDEs are platforms in which you can write code). You can edit your python files in whatever program you like. Some recommended ones are Atom, VS Code, Sublime, and Pycharm. Atom, VS Code, and Sublime are free whereas Pycharm can be downloaded for free by first creating a GitHub account and then registering it as a GitHub student account here. The video tutorial shows these off more.

There are many different IDEs that work for writing in python (IDEs are platforms in which you can write code). You can edit your python files in whatever program you like. Some recommended ones are Atom, VS Code, Sublime, and Pycharm. Atom, VS Code, and Sublime are free whereas Pycharm can be downloaded for free by first creating a GitHub account and then registering it as a GitHub student account here. The video tutorial shows these off more.

Zoom will be used for all interactions that used to be in person :(. This is the link to log in to your Zoom account. This is how Zoom will work for each of its implementations:

Code Hours:

  1. At the beginning of an hours slot, TAs will release a link to join a Zoom video call.
  2. Sign up on signmeup as normal.
  3. You can join the call at any time. However, you will be placed in a waiting room before actually meeting with TAs until it comes to your spot in line. As a result, please constantly be monitoring the hours line and/or your Zoom account when it comes close to being your turn in line.
  4. You will then be accepted to join the meeting. After being accepted into the meeting you will have 2 minutes to initiate conversation with the TA. If you fail to do so, the TA will release you back to the waiting room, where you will have 30 minutes to email the TAs who are currently on hours to unmark you missing. If it has been more than 30 minutes, we reserve the right to delete your sign up.
  5. Once in hours, in order to debug over Zoom, you will have to rely on Zoom’s screen-sharing feature.
  6. To screen share over Zoom: in the panel on the bottom of the meeting, there is a “Screen Share” or “Share” option in which you can choose which screen you’d like to share. You should select your Eclipse Workspace/FastX Session/Atom File/whatever, and then click share in the bottom right hand corner. Your TA should be able to see your screen. After you’re done screen sharing, at the top of your screen, select the “Stop Share” option.

Conceptual Hours/Clinic:

  1. At the beginning of the Conceptual Hours/Clinic TAs will be posting a link for you to join them for Conceptual Hours/Clinic.
  2. TAs will answer questions by demand, and split you into supervised breakout sessions if necessary.

Section:

    Your section TAs will send out invitations to join a Zoom meeting 5 minutes before your section. Joining the meeting will earn you attendance points for that session. (All mini assignments are to be emailed to your section TAs before your section.)

Zoom will be used for all interactions that used to be in person :(. This is the link to log in to your Zoom account. This is how Zoom will work for each of its implementations:

Code Hours:

  1. At the beginning of an hours slot, TAs will release a link to join a Zoom video call.
  2. Sign up on signmeup as normal.
  3. You can join the call at any time. However, you will be placed in a waiting room before actually meeting with TAs until it comes to your spot in line. As a result, please constantly be monitoring the hours line and/or your Zoom account when it comes close to being your turn in line.
  4. You will then be accepted to join the meeting. After being accepted into the meeting you will have 2 minutes to initiate conversation with the TA. If you fail to do so, the TA will release you back to the waiting room, where you will have 30 minutes to email the TAs who are currently on hours to unmark you missing. If it has been more than 30 minutes, we reserve the right to delete your sign up.
  5. Once in hours, in order to debug over Zoom, you will have to rely on Zoom’s screen-sharing feature.
  6. To screen share over Zoom: in the panel on the bottom of the meeting, there is a “Screen Share” or “Share” option in which you can choose which screen you’d like to share. You should select your Eclipse Workspace/FastX Session/Atom File/whatever, and then click share in the bottom right hand corner. Your TA should be able to see your screen. After you’re done screen sharing, at the top of your screen, select the “Stop Share” option.

Conceptual Hours/Clinic:

  1. At the beginning of the Conceptual Hours/Clinic TAs will be posting a link for you to join them for Conceptual Hours/Clinic.
  2. TAs will answer questions by demand, and split you into supervised breakout sessions if necessary.

Section:

    Your section TAs will send out invitations to join a Zoom meeting 5 minutes before your section. Joining the meeting will earn you attendance points for that session. (All mini assignments are to be emailed to your section TAs before your section.)