registry

Scripting Issues
1

I just finished installing the nightly build thanks to rdb, and in the process, found a bug in the windows version for 1/3/10. The python version changed from 2.5 to 2.6, but the installer still puts in the registry as if the python version was 2.5.
All works until you try to install something like PIL or psyco and then they get very confused, as the 2.5 versions will try to install and fail while the 2.6 versions won’t find the python directory. It is a simple fix to change the 2.5 to 2.6 in the registry, although I have not dug into the code to see how to fix it from there.

Thanks!

2

Ah, so it does. Thanks! I’ve just checked in the fix and triggered the Windows devbuild scheduler. It should finish build #5 soon.

This is exactly why the snapshots are so useful - to catch these kind of stupid mistakes early. :slight_smile: