| re: Can anyone confirm this modulefinder bug?
Thomas Heller <theller@python.net> writes:
[color=blue]
> "Roger Binns" <rogerb@rogerbinns.com> writes:
>[color=green]
>> - Create foo.py
>>
>> # -*- coding: mbcs -*-
>> "string"
>> var1="1.2.3.4"
>> var2=0x123345
>>
>> - Do this at a python prompt
>>[color=darkred]
>>> > > import modulefinder
>>> > > m=modulefinder.ModuleFinder()
>>> > > m.run_script("foo.py")[/color]
>>
>> You then get a traceback with a MemoryError (sorry I can't paste
>> the traceback due to this being via display protocol that doesn't
>> support the clipboard).
>>
>> I get this on Linux for sure and believe it is also being seen on Mac.
>> The issue does not occur on Windows.[/color]
>
> Yes, I can confirm this (Python 2.3+, linux x86).
> The problem appears to be this:
>[color=green][color=darkred]
>>>> compile("# -*- coding: mbcs -*-", "<string>", "exec")[/color][/color]
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> MemoryError[color=green][color=darkred]
>>>>[/color][/color][/color]
For Windows, it's possible to also trigger it:
[color=blue][color=green][color=darkred]
>>> compile("# -*- encoding: abc -*-", "<string>", "exec")[/color][/color][/color]
Traceback (most recent call last):
File "<stdin>", line 1, in ?
MemoryError[color=blue][color=green][color=darkred]
>>>[/color][/color][/color]
Who files the bug?
Thomas |