Python Development Environment: Deployment & Capability Validation Lab

STEP 1.1 Pre-Flight System Inventory

Before installing anything, document baseline system information. A real deployment specialist always begins with an inventory.

Open Windows Terminal or PowerShell (press Win + X, then choose Terminal or Windows PowerShell) and run each command below. Capture the output — screenshot or copy/paste — into your working notes.

PS> # Identify the machine
PS> hostname
PS> whoami
PS> # Operating system version
PS> (Get-CimInstance Win32_OperatingSystem).Caption
PS> (Get-CimInstance Win32_OperatingSystem).Version
PS> # Check if Python is already deployed
PS> python --version
PS> py --version
PS> # Check if VS Code is already deployed
PS> code --version

STEP 1.2 Verify Python 3 (Pre-Deployed via Software Center)

Python is already deployed to these lab machines through the district Software Center. Your job is to verify the deployment — confirm it is present, confirm it is on the PATH, and confirm it actually runs. This is exactly what an IT technician does after a managed software push.

Verification: Open a fresh terminal (PowerShell or Windows Terminal — important to use a fresh one, since PATH only refreshes for new shells) and run:

PS> python --version
PS> pip --version
PS> where python

If all three commands succeed, Python is deployed correctly — record the version and the install path, then move on to Step 1.3.

If any command fails: the Software Center deployment did not land cleanly on your machine. Open the Software Center app from the Start menu, search for Python, and click Install (or Repair / Reinstall if it shows as already installed). Wait for it to finish, then close and reopen the terminal and re-run the verification commands.

If Software Center reinstall still fails or the package is missing: these are documented fallback deployment paths. Try them in order, stopping at the first that succeeds. Whichever you used, write it in your report — different machines using different install paths is itself a deployment-drift finding.

1. Microsoft Store: Open the Microsoft Store, search for Python 3.12 (or the latest 3.x), and click Install. The Store version installs per-user and usually works without admin rights.
2. python.org installer: Visit python.org/downloads and download the Windows installer. Run it and — critically — check the box "Add python.exe to PATH" on the first screen.

STEP 1.3 Deploy Visual Studio Code

Attempt the deployment paths in this order:

1. Software Center / Company Portal: Search for Visual Studio Code and install if available.
2. Direct download: Visit code.visualstudio.com/download and choose the User Installer (64-bit). The User Installer does not require administrator privileges.

Verify:

PS> code --version

If code still is not recognized but VS Code does open from the Start menu, launch VS Code, press Ctrl + Shift + P, and run Shell Command: Install 'code' command in PATH.

STEP 1.4 Install the VS Code Python Extension

Open VS Code. Click the Extensions icon in the left sidebar (or press Ctrl + Shift + X). Search for Python (publisher: Microsoft) and click Install.

Test the install: open the Command Palette (Ctrl + Shift + P) and run Python: Select Interpreter. The Python you installed in Step 1.2 should appear in the list. Select it.

STEP 1.5 First Python Program — Terminal Path

Create a working folder and a first script. Use your own name in the folder.

PS> cd $env:USERPROFILE\Documents
PS> mkdir python-validation-lab
PS> cd python-validation-lab
PS> notepad hello.py

In Notepad, paste the following code, save, and close:

import sys
import platform

print("Hello from", platform.node())
print("Python version:", sys.version.split()[0])
print("Executable path:", sys.executable)

Run it from the terminal:

PS> python hello.py

STEP 1.6 First Python Program — VS Code Path

In VS Code, choose File > Open Folder... and open the python-validation-lab folder you just created. Open hello.py.

Run the file three different ways. Confirm each works and document any that do not:

1. Press the Run (▶) triangle in the top-right of the editor.
2. Open the integrated terminal (Ctrl + `) and run python hello.py from inside VS Code.
3. Right-click in the editor and choose Run Python File in Terminal.

Phase 1 Sign-Off Checklist

Before moving to Phase 2, work through this list. You do not need every item to be a green check to continue. Mark each item ✅ (passed), ❌ (failed — error captured), or ⚠️ (partial / workaround applied), and proceed.

• Hostname and OS version recorded
• Python 3.x verified (Software Center install or fallback); python --version works in a fresh terminal
• pip --version works
• VS Code installed; code --version works
• Microsoft Python extension installed; interpreter selected
• hello.py runs from terminal
• hello.py runs from VS Code Run button
• hello.py runs from VS Code integrated terminal
• Screenshots captured for terminal and VS Code execution (or for the failures, if any)

Test Matrix You Will Complete

Use this exact table format in your final report. Fill it in as you work.

TEST 2.1 pip Functionality

PS> python -m pip --version
PS> python -m pip list

If pip list prints a table of packages (even a small one), pip is functional. Note whether you needed to upgrade pip:

PS> python -m pip install --upgrade pip

TEST 2.2 Install CMU Graphics via pip

CMU Graphics is the same library used in the CMU CS Academy online environment. Determining whether it can be installed locally is a major decision point for whether this lab can host serious Python coursework offline.

PS> python -m pip install cmu-graphics

If the install fails because of a permission error, retry with the user flag:

PS> python -m pip install --user cmu-graphics

Verify the install completed:

PS> python -m pip show cmu-graphics

TEST 2.3 CMU Graphics — Local Execution

If Test 2.2 succeeded, create cmu_test.py with the following content and run it:

from cmu_graphics import *

Label('Lab Validation: CMU Graphics OK', 200, 100, size=18)
Rect(50, 150, 300, 50, fill='lightBlue', border='black')
Circle(200, 250, 30, fill='red')

cmu_graphics.run()

You should see a graphics window open with text, a rectangle, and a red circle. Close the window when done.

TEST 2.4 tkinter (Built-in GUI)

tkinter ships with most Python distributions. Run the built-in self-test from the terminal:

PS> python -m tkinter

A small "TK" window should appear with a "Click me!" button and a "QUIT" button. If it does, screenshot it and close it.

Then create tk_test.py and confirm you can build your own:

import tkinter as tk

root = tk.Tk()
root.title("Lab Validation Window")
tk.Label(root, text="tkinter is functional on this machine.").pack(padx=20, pady=20)
tk.Button(root, text="Close", command=root.destroy).pack(pady=10)
root.mainloop()

TEST 2.5 turtle Graphics

turtle is also built in. Create turtle_test.py:

import turtle

t = turtle.Turtle()
t.shape("turtle")
for _ in range(6):
    t.forward(80)
    t.left(60)
turtle.done()

You should see a hexagon traced by a small turtle.

TEST 2.6 Loading External Image Assets

Place any .png file in your python-validation-lab folder (download a small image, or grab one from the school site). Then create image_test.py:

import tkinter as tk

root = tk.Tk()
root.title("Image Load Test")
img = tk.PhotoImage(file="test.png")  # adjust filename to match yours
tk.Label(root, image=img).pack()
root.mainloop()

If the image displays, the file system + GUI pipeline supports asset loading. Note whether the image renders, errors, or is silently blocked.

TEST 2.7 Audio Playback

Place any short .wav file in your folder. Then run:

import winsound
winsound.PlaySound("test.wav", winsound.SND_FILENAME)

If audio plays, sound output is available to Python. If not, document whether the failure is a missing codec, a permission issue, or simply muted hardware.

TEST 2.8 Internet Access from Python

This is one of the most informative tests in a managed environment. Create net_test.py:

import urllib.request

url = "https://example.com"
try:
    response = urllib.request.urlopen(url, timeout=5)
    print("STATUS:", response.status)
    print("FIRST 200 BYTES:", response.read(200))
except Exception as e:
    print("BLOCKED OR FAILED:", type(e).__name__, "-", e)

Possible outcomes — all of them are findings worth recording:

• Status 200 — open internet from Python
• SSL error — content filter is intercepting HTTPS
• Timeout — outbound traffic blocked at the firewall
• 403 / proxy authentication — district proxy in front of all traffic

TEST 2.9 Local File Read & Write

Run the following from the integrated terminal in VS Code:

PS> python -c "open('write_test.txt','w').write('ok'); print(open('write_test.txt').read())"

Repeat the test, but write the file to a Documents subfolder and to your Desktop. Some managed environments allow writing to Documents but block Desktop, and some redirect both to OneDrive without telling the user. Note any redirection.

BOUNDARY A Extension & Package Installation Limits

• Install one additional, harmless VS Code extension (e.g., Code Spell Checker). Does it install? Does it require admin?
• Try python -m pip install requests. Does pip respect proxy settings? Is there an SSL trust issue?
• Try installing a package that is large, like numpy. Note install time — is the network bandwidth comparable to a pro environment, or visibly throttled?

BOUNDARY B Performance Under Load

Create perf_test.py and run it. This is a deliberately heavy loop to expose CPU performance characteristics on the lab hardware.

import time

start = time.perf_counter()
total = 0
for i in range(10_000_000):
    total += i * i
elapsed = time.perf_counter() - start

print(f"Sum: {total}")
print(f"Elapsed: {elapsed:.3f} seconds")

Run it three times. Record the median elapsed time. Compare with a classmate on a different machine — are the numbers consistent across the lab, or do some machines run noticeably slower?

BOUNDARY C Animation & Real-Time Behavior

If CMU Graphics installed in Phase 2, try a continuous animation:

from cmu_graphics import *

ball = Circle(50, 200, 20, fill='red')
app.dx = 4

def onStep():
    ball.centerX += app.dx
    if ball.centerX > 380 or ball.centerX < 20:
        app.dx = -app.dx

cmu_graphics.run()

Does the animation run smoothly, or does it stutter? Does the window remain responsive while the script runs? Inconsistent frame rates between machines indicate uneven graphics driver deployment.

BOUNDARY D Cross-Machine Consistency

Walk through the lab with your notes and compare results with at least three other classmates on different machines. For each test in the Phase 2 matrix, note where machines disagree:

• Did everyone get the same Python version?
• Did pip succeed on every machine?
• Did internet access behave identically?
• Did CMU Graphics open everywhere or only some places?

Inconsistencies between machines indicate deployment drift — a real-world IT problem that managers care about deeply, because it means students cannot rely on identical behavior across the lab.

BOUNDARY E Documented Restrictions

List every action that the system actively blocked today. Include the exact error text. Examples might include:

• "This app has been blocked by your system administrator"
• "The requested operation requires elevation"
• HTTPS certificate intercept warnings
• OneDrive folder redirect notices
• Group Policy-enforced password prompts

This list, by itself, is one of the most professionally useful artifacts you will produce today.

Producing the PDF

Author the report in Microsoft Word, Google Docs, or any equivalent tool. To export to PDF:

• Word: File > Save As > PDF (*.pdf)
• Google Docs: File > Download > PDF Document (.pdf)
• Any app: File > Print > Microsoft Print to PDF

Filename convention: LASTNAME_FIRSTNAME_PythonCapabilityReport.pdf