Checking Your pandas Version

Author

Steven Bogaerts

Why This Matters

We’ll start using pandas in a week or two. Tools like pandas release new versions now and then, so the exact versions on your computer depend on the day you first ran setup.py. Before we start, let’s make sure everyone is up to date and consistent with the autograder, which uses Python 3.14.7 and pandas 3.0.6. That way, code that works on your computer also works the same way on the autograder.

Everyone should follow the steps below, even if you think your setup is already fine. They don’t change any code you’ve written. They only update your setup files and the tools inside your .venv folder.

Step 1: Get the Updated Setup Files

Download EECS_183_update.zip. It contains updated versions of three files you already have: requirements.txt, setup.py, and test_env.py. We’ll replace your old copies with these. After downloading, click to expand the appropriate box below.

  • Open your Downloads folder in File Explorer. (Paste C:\Users\%username%\Downloads into the address bar, as in tutorial 1.)
  • Right-click EECS_183_update.zip and choose Extract All..., then click Extract. A new window opens showing the three files.
  • In that window, press ctrl+A to select all three files, then ctrl+C to copy them.
  • Open your EECS_183 folder (double-click the shortcut on your desktop). Click in an empty area of the window and press ctrl+V to paste.
  • Windows will say the destination already has files with these names. Choose Replace the files in the destination.
  • Open your Downloads folder in Finder. You should see a new EECS_183_update folder. (If you see EECS_183_update.zip instead, double-click it to unzip it.)
  • Open the EECS_183_update folder. Press ⌘+A to select all three files, then ⌘+C to copy them.
  • Open your EECS_183 folder (double-click the alias on your desktop). Click in an empty area of the window and press ⌘+V to paste.
  • Finder will say that items with these names already exist. Check Apply to all, then choose Replace.

Step 2: Run setup.py

  • Open your EECS_183 folder in VS Code, as usual. If you have any Python programs or Jupyter notebooks running, stop or close them first.
  • In the EXPLORER area, double-click setup.py to open it.
  • With setup.py open, hit the right-pointing triangle (“play” button) in the upper-right corner of VS Code to run it.

This may take several minutes, since it downloads the exact versions of several tools. You can let it run in the background. It’s done when you see this at the end of the output in the TERMINAL area:

==================================================
SUCCESS! Your environment is ready.
==================================================

(Below that it also lists some “next steps” you already did when you first set up VS Code. You can ignore them.)

Step 3: Run test_env.py

  • In the EXPLORER area, double-click test_env.py to open it.
  • With test_env.py open, hit the “play” button again to run it.

You should see output like the following. The .venv folder location on the second line will be different for you, but everything else should match exactly, with [OK] on every line:

Checking Python environment... (Python 3.14.7)
[OK]    Python 3.14
[OK]    Virtual Environment Active (C:\Users\Steve\Documents\EECS_183\.venv)
------------------------------------------------------------
[OK]    numpy                2.5.3
[OK]    pandas               3.0.6
[OK]    matplotlib           3.11.2
[OK]    seaborn              0.13.2
[OK]    scikit-learn         1.9.1
[OK]    jupyterlab           4.6.3
[OK]    imageio              2.37.4
[OK]    flake8               7.3.0
[OK]    pep8-naming          0.15.1
[OK]    flake8-bugbear       26.9.9
------------------------------------------------------------

SUCCESS! Your environment is ready for class.

If so, you’re done! If not, check the troubleshooting notes below.

Troubleshooting

VS Code is using the wrong version of Python.

  • Look in the lower-right corner of VS Code (with setup.py open). If it shows a version other than 3.14, follow the steps in Opening a Python File (and Selecting the Python Interpreter If Necessary) to choose Python 3.14, then run setup.py again.
  • If Python 3.14 isn’t one of the choices, you’ll need to install it first by following the Installing Python tutorial. You don’t need to uninstall any other version of Python you have. Then choose Python 3.14 as described above, and run setup.py again.
  • If setup.py says your existing .venv uses a different version of Python and deletes it, that’s expected. It builds a new one. When it finishes, close and reopen VS Code, and then go to Step 3.

Some program is still using the tools that setup.py is trying to update. Close VS Code completely (and any Jupyter notebooks or other Python programs), reopen VS Code, and run setup.py again.

VS Code is not using your .venv, so the versions shown aren’t the ones your programs normally use. Follow the steps in Selecting the Python Interpreter (with a venv), then run test_env.py again.

Make sure you completed Step 1: open requirements.txt in VS Code and check that it contains the line pandas==3.0.6. If it doesn’t, the old file wasn’t replaced; repeat Step 1. Then run setup.py again (Step 2), and wait until you see SUCCESS! before running test_env.py.

If none of these help, come to office hours or post on Piazza. Include a screenshot of the output of both setup.py and test_env.py.