Tom,
You appear to be running a 64-bit Enthought Python Distribution, dtd 4-12-2012 as you default Python.
From your screen capture, the C:\Python27 directory listing contains a full Python distribution--python.exe, pythonw.exe which look by date to be the 64-bit EPD you show running in IDLE. Would likewise impact Python run from command prompt as your environment variables are pointing to that directory.
But you also have an Esri ArcGIS 10.1 installation done on 5-9-2013. When, since the C:\Python27 would not have been detected as a 32-bit python installation, the Esri ArcGIS installer laid down the 32-bit Python in C:\Python27\ArcGIS10.1--a look in that directory will show you probably have another python.exe and pythonw.exe installed. Fortunately the Windows registry, ArcGIS for Desktop registry settings keep it pointed to the correct Python executables where it reads the Desktop101.pth for proper path actions.
But since the system environment variables are pointing to the C:\Python27 directory, the 64-bit python is what is always being called from command prompt or Python IDE environment like IDLE.
[INDENT]To clean things up, you should simply be able to uninstall the Enthought Python Distribution Free 64-bit Python from Add/Remove programs (appwiz.cpl).
Then check your Environment variables to adjust the PATH value to reflect a path to "C:\Python27\ArcGIS10.1" and perhaps set a PYTHONHOME variable to "C:\Python27\ArcGIS10.1"
Your IDLE session, or a windows command line or system scripted launch of Python, will then run with the 32-bit pythonw.exe[/INDENT]
And, if you need 64-bit python, or want a packaged Python bundle like Enthought Canopy Express, you have to manage your environment adjusting it to use the appropriate versions. That would include use of Esri's ArcGIS 10.1 SP1 64-bit Desktop Background Geoprocessing installation when running it "out of process", i.e. without the ArcGIS Desktop GUI.
The 64-bit Desktop Background Geoprocessing installation replaces some 32-bit components of the ArcPy site library with 64-bit equivalents--and the ArcGIS for Desktop does not use the system environment variables to keep track of the executable to run while in-process. But when running scripts outside ArcGIS for Desktop GUI, you have to manage the path and working directories for your 32-bit or 64-bit Python scripting.
Hope that is clear enough for you, post back if not.
Stuart
P.S. not sure why your Windows 7 command line use of where.exe is not responding correctly with executable location, it should be.