Hello again John -- your hack/fix seems to work. Thanks a lot, now
let's hope timbot will indeed be here shortly with a proper fix =)
--
http://mail.python.org/mailman/listinfo/python-list
John Machin wrote:
> koara wrote:
> > John Machin wrote:
> There is a bug.
> I'll report it.
Reported.
http://sourceforge.net/tracker/index.php?func=detail&aid=1528074&group_id=5470&atid=105470
--
http://mail.python.org/mailman/listinfo/python-list
koara wrote:
> John Machin wrote:
> > --test results snip---
> > Looks to me like the problem has nothing at all to do with the length
> > of the searched strings, but a bug appeared in 2.3. What version(s)
> > were you using? Can you reproduce your results (500 & 499 giving
> > different answers)
John Machin wrote:
> --test results snip---
> Looks to me like the problem has nothing at all to do with the length
> of the searched strings, but a bug appeared in 2.3. What version(s)
> were you using? Can you reproduce your results (500 & 499 giving
> different answers) with the same version?
koara wrote:
> Hello, it might be too late or too hot, but i cannot work out this
> behaviour of find_longest_match() in difflib.SequenceMatcher:
>
> string1:
[snipped 500-byte string]
>
> string2:
>
[snipped 500-byte string]
>
> find_longest_match(0,500,0,500)=(24,43,10)="version01t"
>
> What? O_
Hello, it might be too late or too hot, but i cannot work out this
behaviour of find_longest_match() in difflib.SequenceMatcher:
string1:
releasenotesforwildmagicversion01thiscdromcontainstheinitialreleaseofthesourcecodethataccompaniesthebook"3dgameenginedesign:apracticalapproachtorealtimecomputer