File Handles

Hello all,

After opening files for editing in Wing, and then closing
them, Wing 
holds file handles for the closed files. That makes it
impossible for me 
to delete the directory containing these files whilst Wing
is open.

This is something I do a lot whilst debugging. (I verified
that it was 
Wing that had the file handles using Process Explorer - OS
Windows XP 
SP2, Wing version 2.1.1.)

All the best,

Michael Foord
http:/
/www.voidspace.org.uk/python/index.shtml
_________________________________________________
Wing IDE users list
http://wingware.com
/lists/wingide

On Monday 21 August 2006 18:12, Michael Foord wrote:
> Hello all,
>
> After opening files for editing in Wing, and then
closing them, Wing
> holds file handles for the closed files. That makes it
impossible for me
> to delete the directory containing these files whilst
Wing is open.

Perhaps it's got 'em open in the source analyzer?

Not to start an OS war, but this is a known bit of Windows
silliness - Unix 
lets you delete open files quite nicely. ;)
-- 
Peter Fein                                                  
  pfeinpobox.com
773-575-0694                                      Jabber:
peter.feingmail.com
http://www.pobox.com/~pf
ein/                     irc://irc.freenode.net/#chipy
_________________________________________________
Wing IDE users list
http://wingware.com
/lists/wingide

Peter Fein wrote:
> On Monday 21 August 2006 18:12, Michael Foord wrote:
>> After opening files for editing in Wing, and then
closing them, Wing
>> holds file handles for the closed files. That makes
it impossible for me
>> to delete the directory containing these files
whilst Wing is open.
> 
> Perhaps it's got 'em open in the source analyzer?
> 
> Not to start an OS war, but this is a known bit of
Windows silliness - Unix 
> lets you delete open files quite nicely. ;)

Yes, it is partly the source analyzer code and the win32
file 
modification watching code.  We will look at improving this
in future 
Wing versions.

Cheers,

John
_________________________________________________
Wing IDE users list
http://wingware.com
/lists/wingide

Wingware Support schrieb:
> Peter Fein wrote:
>> On Monday 21 August 2006 18:12, Michael Foord
wrote:
>>> After opening files for editing in Wing, and
then closing them, Wing
>>> holds file handles for the closed files.
>> Perhaps it's got 'em open in the source analyzer?
> Yes, it is partly the source analyzer code and the
win32 file 
> modification watching code.  We will look at improving
this in future 
> Wing versions.
Would a "disengage / suspend all scripts" toggle
be a possibility?
I have similar problems working with my project. The python
code is 
called from within a c++ program and the only way I can make
it work 
right, is to always close WingIDE first, then start the
calling program.

Cheers,
Rex
_________________________________________________
Wing IDE users list
http://wingware.com
/lists/wingide

Rex Turnbull wrote:
> Would a "disengage / suspend all scripts"
toggle be a possibility?
> I have similar problems working with my project. The
python code is 
> called from within a c++ program and the only way I can
make it work 
> right, is to always close WingIDE first, then start the
calling program.

Does your program delete the files or is it failing for some
other reason?

Also, does anyone know how to watch for file modifications
on win32 but 
let the file be deleted (this is the core of the problem)?

Thanks,

John
_________________________________________________
Wing IDE users list
http://wingware.com
/lists/wingide