Most of these programs have been tested on
Python 2.3.4 / VPython-Py2.3.4-2003-10-05b.exe
I am trying to gradually update them to work with the newer versions.
If you have made any upgrades, please share them with me.

Ideally, we would have liked to use the latest versions of
the various software packages [which should be possible].
However, for now, the combination of versions that worked for us
[with our program] is:

Note: This was just thrown together as a proof of concept.
The code isn't the prettiest. The tracking and the visualization could certainly be improved.

Some Hardware details:
I bought two LED-flashlights (less than $5 each) and replaced the LEDs with
IR-LEDs from DealExtreme.
I mounted the flashlights onto a pair of safety goggles. (The first version is pictured here.)
The Wiimote is sitting on top of my monitor, pointing toward me.
[Note, I only use the Wiimote. I don't have a Wii console.]

My current version uses
IR-LEDs from Radio Shack
[which seem to have a better viewing angle]
and
two
MAGLITE Solitaire flashlights
[found at Walmart] which feature replaceable LEDs.
So, no soldering is needed! However, since my standard-size LEDs were too big,
I had to leave off the moveable mirror/cover used to adjust the beam.

If you don't have these IR parts available, you can try using a
pair of standard (IR-based) remote controls. By the way, it's helpful to
use your typical webcam or cameraphone to see the IR light to check that the LEDs
are hooked-up correctly.

(Think of the accelerometer as "a small sphere suspended by
identical springs attached to the corners of a cube".)

When your Wiimote is sitting normally upright on your desk, it will read a_z=1.
(The small sphere is displaced downwards, and the net force on the sphere
due to the springs is upward.)

When your Wiimote is in freefall (and not rotating), it will read zero.
To show this, gently toss (without rotation) your Wiimote to someone.
When the accelerometer value is small enough, the background color of the
scene changes to white (since the corresponding small arrow is hard to see).

The only file you need from the downloaded package is WiimoteLib.dll.
(It is helpful to also use WiimoteTest.exe to see all sorts of data from the wiimote.
You'll find documentation
for the library, WiimoteLib.chm, in the docs/ folder. )

Fortunately, Feihong Hsu
figured out that one can compile the
Python for .NET source code
and tweak switches to make it work in Python 2.5 and in Python 2.6.
In the end, all you need are the two files
Python.Runtime.dll
and
clr.pyd
placed in the Python folder (e.g. C:\Python25 ).

VPythonWiimote-examples.zip
contains some example programs
(including the required library files mentioned above).
(Tested for Python 2.5/VPython 3.2.11.
Some modifications may be needed
for Python 2.6 or for Visual 5.)

Here's a registration-file for Windows 2000 and Windows XP
that will fix that problem with the IDLE editor closing completely
when terminating an animation you are working on.
Python-File-new.reg
It assumes that you installed Python in the C:\ drive.
If so, you may just "Open" it.
Otherwise,
download [Right-click->Save Link to...]
the appropriate pair to your desktop, then after reading the .reg files and making any desired changes,
merge with your registry.
Then, "Merge" it by double-clicking on it.

If you mess up, you can try to clean things up in Explorer
via Tools->FolderOptions->FileTypes...->PY Python File->Advanced
..or else use regedit.Use at your own risk! (Backup your registry before merging!)

Using Python 2.3 and Python 2.4

These registry hacks to allowed me to select which VPython version is used to execute a .py file.
They may work for you.Use at your own risk! (Backup your registry before merging!)
Download [Right-click->Save Link to...]
the appropriate pair to your desktop, then after reading the .reg files and making any desired changes,
merge with your registry.

If you mess up, you can try to clean things up in Explorer
via Tools->FolderOptions->FileTypes...->PY Python File->Advanced
..or else use regedit.Use at your own risk! (Backup your registry before merging!)