> Ignoring most that's been said in this thread, would it be possible > for the installer to detect the presence of python15.dll in the system > directory and offer to delete it? This should only be done if the installer can be very sure that the user _tried_ to uninstall 1.5, but this DLL remains. This could be done in a number of ways, none of which are foolproof (eg, you could check for a 1.5 registry key, but of the user has added their own PythonPath entries, for example, the installer wont remove them (as it didnt add them) - meaning you end up with a partial 1.5 registry tree remaining. A big of experimentation could provide something that works in a majority of cases. IMO, it is very important 1.5 and x.x can coexist on the same machine; especially in the light of this thread, where it should be obvious that many extension wont be available for post 1.5 releases until quite some time after that core release hits the street... Mark. \
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4