durusmail: quixote-users: Re: Removing pltc files on compilation failures, fails.
Removing pltc files on compilation failures, fails.
2003-03-17
Re: Removing pltc files on compilation failures, fails.
2003-03-17
Re: Removing pltc files on compilation failures, fails.
2003-03-17
Re: Removing pltc files on compilation failures, fails.
2003-03-17
Re: Removing pltc files on compilation failures, fails.
2003-03-17
Removing pltc files on compilation failures, fails.
2003-03-17
Removing pltc files on compilation failures, fails.
2003-03-17
Re: Removing pltc files on compilation failures, fails.
Michael Watkins
2003-03-17
I've seen this too - long ago. I didn't bother looking for root causes -
when I make a syntax mistake and receive one of the unhelpful unlink error
messages, I run a windows cmd file that contains

del /s *.pyc
del /s *.ptlc

from the 'root' of my quixote application.



At 02:03 PM 3/17/2003 -0500, Graham Fawcett wrote:
>David Ascher wrote:
>>The _load_ptl code in ptl_import.py results in 'unhelpful' tracebacks on
>>Windows (in at least some circumstances), in the case of a syntax error
>>in a PTL file.
> > [snip]
> >
>>fails in the event of a SyntaxError, on at least three Win2k machines,
>>with the os.unlink() call raising an OSError, "Permission denied".  I
>>haven't been able to figure out why that happens, but in the meantime am
>>running with code like:
> > [snip]
>
>
>Thank you! I've been flying in the dark with PTL errors, and had
>desensitized myself to the OSErrors and lack of decent feedback. This is a
>great help!
>
>-- Graham
>
>
>
>_______________________________________________
>Quixote-users mailing list
>Quixote-users@mems-exchange.org
>http://mail.mems-exchange.org/mailman/listinfo/quixote-users
>


reply