IPython(x,y) hijacks opening drives in Windows Explorer

[GoogleCodeExporter]

If relevant, please answer to the following questions:
1. What version of Python(x,y) have you installed?
-Latest

2. Which components have you installed (Python(x,y) installer: component
page):
-Added some unsupervised learning, networks, parallelism and image 
processing packages.  Removed all Eclipse packages.  

3. Have you selected the option "Customize installation directories"?
-No

5. Where did you install Python(x,y) itself?
-Default

6. Have you installed Python(x,y):
-Current user

7. What is your operating system?
-Vista x64

8. When you installed Python(x,y), were you logged in as :
-Administrator

9. If you are using Windows Vista, have you installed Python(x,y):
-Double-clicking installed

10. Regarding installed softwares on your machine, how did you clean your
machine before installing Python(x,y) (multiple answers are possible):
b. you uninstalled any previous Python distribution (including the
official .msi)

What steps will reproduce the problem?
1. Install Python(x,y) with IPython(x,y)
2. Try to open a drive.  
3. Uninstalling Python(x,y) restores proper context menu order / default 
behaviour.  

What is the expected output? What do you see instead?
-I want to open my fucking D:\ and instead I get one of five interactive 
consoles included in this package.  I am not going to edit the registry to 
keep Python(x,y) installed and will be installing Spyder and packages 
manually instead.  

Original issue reported on code.google.com by juggerna...@gmail.com on 13 Mar 2010 at 7:39

[GoogleCodeExporter]

What do you mean by "I want to open my fucking D:\"?

Original comment by pierre.raybaut on 29 Mar 2010 at 4:53

[GoogleCodeExporter]

If I have the IPython(x,y) console installed in any form, whenever I 
double-click on a 
root drive in Explorer ("Computer") it opens a console window instead of that 
drive.  
It's hijacking the default double-click action.  

I've since installed only Spyder and certain libraries from Python(x,y) in 
order to 
avoid this behaviour.  

Original comment by juggerna...@gmail.com on 29 Mar 2010 at 7:46

[GoogleCodeExporter]

Wow that is a strange behaviour indeed, never reported before!
Well if it works for you to install libraries by hand, then I think I can close 
this 
issue.
Thanks for reporting this.

Original comment by pierre.raybaut on 30 Mar 2010 at 6:32

• Changed state: WontFix

[GoogleCodeExporter]

Why are you setting this to "wontfix"?  That's a glaring issue that prevents me 
from 
using the Python(x,y) launcher without modifying my context menus in the 
registry.

Original comment by juggerna...@gmail.com on 2 Apr 2010 at 8:30

[GoogleCodeExporter]

Well, that's because you wrote "fucking" earlier, so I guess you won't have the 
patience to help me debug this... and since I'm doing all this on my free time, 
I don't 
want to spend time to convince anyone to do anything like a commercial support 
staff 
would do.

Original comment by pierre.raybaut on 2 Apr 2010 at 6:35

[GoogleCodeExporter]

Can you not understand my exasperation when your product hijacks a fundamental 
operation in Windows Explorer?  I'd be happy to help you debug this as I cannot 
use 
certain useful features of Python(x,y) without IPython(x,y) being installed, 
but if you 
don't care then I guess it's back to PyDev.  

Original comment by juggerna...@gmail.com on 2 Apr 2010 at 9:37

[GoogleCodeExporter]

Yes I can understand your exasperation: welcome to the Windows world! 
...because if 
you can make such an installer on Windows without any significant side effect 
on the 
system, you're welcome to do so! Unfortunately, Windows is designed in a way 
that it 
is very difficult to avoid this kind of situation at 100%. The fact is that I'm 
testing Python(x,y) installation on virtual machines, i.e. on a clean Windows 
XP 
installation. So the only thing that I can guarantee is that it will work on a 
clean 
Win XP installation. One of my testing machine is running on Vista 32bits and a 
lot 
of users are using Vista too, so it has been installed a lot on this OS without 
detecting this bug. All these precautions are intended to minimize the 
probability to 
encounter such a bug, but Windows is designed in a way that I can't tell that 
this 
probability is zero.

And you can hardly put it on me and write that *I* don't care... would I do all 
the 
things that I do by sharing all this work if I didn't care?? On the contrary, 
my 
problem is that I care too much and I spend too much time on these 
developments, much 
more that my close friends and family can understand.

Original comment by pierre.raybaut on 3 Apr 2010 at 8:48

[GoogleCodeExporter]

I think I may have found where this bug comes from.
If you try the new version of console's plugin, it could work:
http://pythonxy.googlecode.com/files/console-2.0.145.exe

Original comment by pierre.raybaut on 10 Apr 2010 at 6:56

• Changed state: Fixed