[Python-Dev] PEP 397 (Python launcher for Windows) reference implementation (original) (raw)
Vinay Sajip vinay_sajip at yahoo.co.uk
Sun Jul 3 15:06:43 CEST 2011
- Previous message: [Python-Dev] PEP 397 (Python launcher for Windows) reference implementation
- Next message: [Python-Dev] PEP 397 (Python launcher for Windows) reference implementation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark Hammond <skippy.hammond gmail.com> writes:
But this only happens when they install a later version, then uninstall the later one and continue to use the old one. I'd suggest that is (a) rare and (b) possibly already broken (ie, the old association may not be restored now). If the old association currently is correctly restored, then I'd expect things to just magically work in this new model without any effort.
I've now checked, and it appears that we don't do the right thing now anyway.
On a clean Win7-x64, I installed Python 2.7 (32-bit), for all users, with registration of extensions - and Python.File etc. were added to the registry pointing at Python 2.7.
I then installed Python 3.2 the same way, and rhe registry entries then pointed to 3.2.
I then uninstalled 3.2, and the registry entries were gone! No magical restoration to the earlier values :-(
Okay - if users have to do this now anyway, we at least wouldn't be naking things worse :-)
Regards,
Vinay Sajip
- Previous message: [Python-Dev] PEP 397 (Python launcher for Windows) reference implementation
- Next message: [Python-Dev] PEP 397 (Python launcher for Windows) reference implementation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]