This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author richard_b_martin
Recipients georg.brandl, richard_b_martin
Date 2008-08-21.20:24:23
SpamBayes Score 1.0498021e-07
Marked as misclassified No
Message-id <1219350265.84.0.067322027975.issue3636@psf.upfronthosting.co.za>
In-reply-to
Content
I installed a 3.0 beta for the first time in Windows.  I was surprised
when my 2.5 scripts started to fail.  I traced it down to the 3.0
install modifying the registry.  

If you run "assoc .py" from a command line, the return value is
Python.File.  If you search the registry for references to Python.File,
you'll find a path that points to python.exe.   The 3.0 install changed
this value.  

So at least a warning in the installation instructions would be nice. 
Probably better would be a script that allow a user to switch between
2.x and 3.0 installations.  That would include having to perhaps modify
the env. variables, Path and PYTHONPATH (see bug 2375) and the registry.

Many thanks, by the way, to all the python developers over the years.
History
Date User Action Args
2008-08-21 20:24:26richard_b_martinsetrecipients: + richard_b_martin, georg.brandl
2008-08-21 20:24:25richard_b_martinsetmessageid: <1219350265.84.0.067322027975.issue3636@psf.upfronthosting.co.za>
2008-08-21 20:24:25richard_b_martinlinkissue3636 messages
2008-08-21 20:24:23richard_b_martincreate