Guido van Rossum <[EMAIL PROTECTED]> writes:
> On 9/30/05, Thomas Heller <[EMAIL PROTECTED]> wrote:
>> On several occasions I have seen tracebacks in my code pointing to PIL's
>> __init__.py file. That is strange, because I have installed PIL but it
>> is used nowhere.
>>
>> Finally I traced it do
On 9/30/05, Thomas Heller <[EMAIL PROTECTED]> wrote:
> On several occasions I have seen tracebacks in my code pointing to PIL's
> __init__.py file. That is strange, because I have installed PIL but it
> is used nowhere.
>
> Finally I traced it down to a problem in the linecache code, which tries
>
Oleg Broytmann <[EMAIL PROTECTED]> writes:
> On Fri, Sep 30, 2005 at 09:17:39AM +0200, Thomas Heller wrote:
>> On several occasions I have seen tracebacks in my code pointing to PIL's
>> __init__.py file. That is strange, because I have installed PIL but it
>> is used nowhere.
> [skip]
>> The bug
On Fri, Sep 30, 2005 at 09:17:39AM +0200, Thomas Heller wrote:
> On several occasions I have seen tracebacks in my code pointing to PIL's
> __init__.py file. That is strange, because I have installed PIL but it
> is used nowhere.
[skip]
> The bug is present in 2.3, 2.4, and current CVS.
I have
On several occasions I have seen tracebacks in my code pointing to PIL's
__init__.py file. That is strange, because I have installed PIL but it
is used nowhere.
Finally I traced it down to a problem in the linecache code, which tries
to be smart in up updatecache function. When os.stat() on the f