Can't drag and drop onto .py in Windows XP?

[Sizer]

I have several python utils that look at sys.argv to get a list of
filenames to process and mangle the files in various ways. If I have a
bar.bat file in Windows XP then I can just drag foo.avi onto bar.bat and
bar.bat gets called with foo.avi as an argument, everyone's happy. But if I
have a bar.py (or .pyw) and try to drag and drop foo.avi to it, I get a big
NO cursor and nothing happens.

Now I can work around this by creating a _bar.bat and having the _bar.bat
call bar.pyw with the filenames it was passed (this is obviously
ridiculous). Or I can create a shortcut which has the target of
c:\python25\pythonw.exe c:\mybar\bar.pyw
and that works, but makes telling people how to install my utilities on
their computer a pain in the rear. It's just a little weird that I can't
just drag and drop file names onto .pyw or .py files. Am I missing
something here?

Thanks for any help.

[Ian Kelly]

On Tue, May 6, 2008 at 9:12 PM, Sizer <Si***@nospam.comwrote:

I have several python utils that look at sys.argv to get a list of
filenames to process and mangle the files in various ways. If I have a
bar.bat file in Windows XP then I can just drag foo.avi onto bar.bat and
bar.bat gets called with foo.avi as an argument, everyone's happy. But if I
have a bar.py (or .pyw) and try to drag and drop foo.avi to it, I get a big
NO cursor and nothing happens.

Now I can work around this by creating a _bar.bat and having the _bar.bat
call bar.pyw with the filenames it was passed (this is obviously
ridiculous). Or I can create a shortcut which has the target of
c:\python25\pythonw.exe c:\mybar\bar.pyw
and that works, but makes telling people how to install my utilities on
their computer a pain in the rear. It's just a little weird that I can't
just drag and drop file names onto .pyw or .py files. Am I missing
something here?

I believe the problem is that Windows doesn't view bar.py as an
executable file, but as a data file with an associated launcher. It's
not smart enough to figure out that when you try to drop a file onto a
..py file, you want it to run python.exe with both the .py file and the
dropped file as arguments. I don't think there's any way to change
this behavior, but I could be mistaken.

[Roger Upole]

Sizer wrote:

>I have several python utils that look at sys.argv to get a list of
filenames to process and mangle the files in various ways. If I have a
bar.bat file in Windows XP then I can just drag foo.avi onto bar.bat and
bar.bat gets called with foo.avi as an argument, everyone's happy. But if
I
have a bar.py (or .pyw) and try to drag and drop foo.avi to it, I get a
big
NO cursor and nothing happens.

Now I can work around this by creating a _bar.bat and having the _bar.bat
call bar.pyw with the filenames it was passed (this is obviously
ridiculous). Or I can create a shortcut which has the target of
c:\python25\pythonw.exe c:\mybar\bar.pyw
and that works, but makes telling people how to install my utilities on
their computer a pain in the rear. It's just a little weird that I can't
just drag and drop file names onto .pyw or .py files. Am I missing
something here?

Thanks for any help.

You can register a DropHandler for the Python file class.
Put this in a .reg file and merge it into the registry:

REGEDIT4

[HKEY_CLASSES_ROOT\Python.File\shellex\DropHandler]
@="{86C86720-42A0-1069-A2E8-08002B30309D}"
Roger

[Sizer]

"Roger Upole" <ru****@hotmail.comwrote in
news:ma**************************************@pyth on.org:

Sizer wrote:

>It's just a little weird that I
can't just drag and drop file names onto .pyw or .py files. Am I
missing something here?

Thanks for any help.

You can register a DropHandler for the Python file class.
Put this in a .reg file and merge it into the registry:

REGEDIT4

[HKEY_CLASSES_ROOT\Python.File\shellex\DropHandler]
@="{86C86720-42A0-1069-A2E8-08002B30309D}"

Sir, you rock! I found that it actually worked a little better if I used
a generic wsh drop handler instead of the .exe handler, but I would never
have known where to start looking without your suggestion. I ended up
with the following .reg file, and now I can drag and drop files onto my
..py, .pyw, and .pyc files and off they go as you'd expect. It kind of
seems like this should be the default installer behavior unless there's a
good reason not to do it. Thanks again for your help.

REGEDIT4

[HKEY_CLASSES_ROOT\Python.File\shellex\DropHandler]
@="{60254CA5-953B-11CF-8C96-00AA00B8708C}"

[HKEY_CLASSES_ROOT\Python.NoConFile\shellex\DropHan dler]
@="{60254CA5-953B-11CF-8C96-00AA00B8708C}"

[HKEY_CLASSES_ROOT\Python.CompiledFile\shellex\Drop Handler]
@="{60254CA5-953B-11CF-8C96-00AA00B8708C}"