[issue33112] SequenceMatcher bug

Tim Peters added the comment: Please see the response to issue31889. Short course: you need to pass `autojunk=False` to the SequenceMatcher constructor. -- nosy: +tim.peters resolution: -> duplicate stage: -> resolved status: open -> closed

[issue33112] SequenceMatcher bug

79, 43, 43), ('equal', 79, 81, 43, 45), ('replace', 81, 122, 45, 80), ('equal', 122, 123, 80, 81), ('replace', 123, 284, 81, 284)] -- messages: 314163 nosy: mcft priority: normal severity: normal status: open title: SequenceMatcher bug type: behavior versions: Python 3.5

[issue1711800] SequenceMatcher bug with insert/delete block after replace

Peter Waller peter.wal...@gmail.com added the comment: Apologies for the bump, but it has been more than a year and I did attach a patch! :-) What next? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1711800

[issue1711800] SequenceMatcher bug with insert/delete block after replace

R. David Murray rdmur...@bitdance.com added the comment: No need to apologize for the bump. The trick is catching the interest of someone who feels qualified to judge the patch. I've added a couple people to nosy who worked on difflib recently. If no one speaks up in the next few days, it

[issue1711800] SequenceMatcher bug with insert/delete block after replace

Terry J. Reedy tjre...@udel.edu added the comment: I believe this issue should be closed and have set it to pending. The original report of a 'bug' and the two 'testcases' were and are invalid as they are based on an incorrect understanding of SequenceMatcher. It is not a diff program and in

[issue1711800] SequenceMatcher bug with insert/delete block after replace

Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1711800 ___

[issue4622] SequenceMatcher bug with long sequences

Terry J. Reedy tjre...@udel.edu added the comment: This appears to be one of at least three duplicate issues: #1528074, #2986, and #4622. I am closing two, leaving 2986 open, and merging the nearly disjoint nosy lists. (If no longer interested, you can delete yourself from 2986.) #1711800

Re: SequenceMatcher bug ?

Gabriel Genellina [EMAIL PROTECTED] wrote: En Wed, 10 Dec 2008 15:14:20 -0200, eliben [EMAIL PROTECTED] escribió: What ? This can't be. 1. Go to http://try-python.mired.org/ 2. Type import difflib 3. Type difflib.SequenceMatcher(None, [4] + [5] * 200, [5] * 200).ratio() Don't you get 0

Re: SequenceMatcher bug ?

On Tue, 9 Dec 2008 at 22:15, eliben wrote: On Dec 10, 4:12?am, [EMAIL PROTECTED] wrote: On Mon, 8 Dec 2008 at 23:46, eliben wrote: This is about Python 2.5.2 - I don't know if there were fixes to this module in 2.6/3.0 I think I ran into a bug with difflib.SequenceMatcherclass.

Re: SequenceMatcher bug ?

En Wed, 10 Dec 2008 12:00:30 -0200, [EMAIL PROTECTED] escribió: On Tue, 9 Dec 2008 at 22:15, eliben wrote: On Dec 10, 4:12 am, [EMAIL PROTECTED] wrote: On Mon, 8 Dec 2008 at 23:46, eliben wrote: This is about Python 2.5.2 - I don't know if there were fixes to this module in 2.6/3.0 I think

Re: SequenceMatcher bug ?

My system is Gentoo, which installs python from source.  Maybe gentoo applies patches that the binary releases don't have. I can't reproduce the problem. I got exactly the same results (0.999...)   with all the releases I have at hand, ranging from 3.0 back to 2.1.3, all   on Windows.

Re: SequenceMatcher bug ?

eliben wrote: My system is Gentoo, which installs python from source. Maybe gentoo applies patches that the binary releases don't have. I can't reproduce the problem. I got exactly the same results (0.999...) with all the releases I have at hand, ranging from 3.0 back to 2.1.3, all on

Re: SequenceMatcher bug ?

En Wed, 10 Dec 2008 15:14:20 -0200, eliben [EMAIL PROTECTED] escribió: My system is Gentoo, which installs python from source.  Maybe gentoo applies patches that the binary releases don't have. I can't reproduce the problem. I got exactly the same results (0.999...)   with all the releases

[issue1711800] SequenceMatcher bug with insert/delete block after replace

Martin v. Löwis [EMAIL PROTECTED] added the comment: Without a patch, this is not a candidate for 2.5.3. -- nosy: +loewis versions: +Python 2.7 -Python 2.5.3 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1711800

[issue1711800] SequenceMatcher bug with insert/delete block after replace

Raymond Hettinger [EMAIL PROTECTED] added the comment: Tim, any comments or interest? -- assignee: - tim_one nosy: +rhettinger, tim_one ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1711800 ___

[issue4622] SequenceMatcher bug with long sequences

it on Linux, Windows (AS 2.5.2) and Try Python (http://try-python.mired.org/) -- components: Library (Lib) messages: 77559 nosy: eliben severity: normal status: open title: SequenceMatcher bug with long sequences versions: Python 2.5 ___ Python tracker [EMAIL

[issue4622] SequenceMatcher bug with long sequences

David W. Lambert [EMAIL PROTECTED] added the comment: Python 3.0rc1+ similar. -- nosy: +LambertDW versions: +Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4622 ___

[issue4622] SequenceMatcher bug with long sequences

Gabriel Genellina [EMAIL PROTECTED] added the comment: Python 2.3.4 and later have this bug. But release 2.1.3 doesn't: Python 2.1.3 (#35, Apr 8 2002, 17:47:50) [MSC 32 bit (Intel)] on win32 Type copyright, credits or license for more information. import difflib difflib.SequenceMatcher(None,

[issue4622] SequenceMatcher bug with long sequences

Gabriel Genellina [EMAIL PROTECTED] added the comment: #2986 may be a duplicate of this; #1528074 is relevant too. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4622 ___

Re: SequenceMatcher bug ?

On Mon, 8 Dec 2008 at 23:46, eliben wrote: This is about Python 2.5.2 - I don't know if there were fixes to this module in 2.6/3.0 I think I ran into a bug with difflib.SequenceMatcher class. Specifically, its ratio() method. The following: SequenceMatcher(None, [4] + [10] * 500 + [5], [10] *

Re: SequenceMatcher bug ?

On Dec 10, 4:12 am, [EMAIL PROTECTED] wrote: On Mon, 8 Dec 2008 at 23:46, eliben wrote: This is about Python 2.5.2 - I don't know if there were fixes to this module in 2.6/3.0 I think I ran into a bug with difflib.SequenceMatcherclass. Specifically, its ratio() method. The following:

SequenceMatcher bug ?

Hello, This is about Python 2.5.2 - I don't know if there were fixes to this module in 2.6/3.0 I think I ran into a bug with difflib.SequenceMatcher class. Specifically, its ratio() method. The following: SequenceMatcher(None, [4] + [10] * 500 + [5], [10] * 500 + [5]).ratio () returns 0.0

[issue1711800] SequenceMatcher bug with insert/delete block after replace

Andrew Inglis [EMAIL PROTECTED] added the comment: Are there any updates for this issue? I am having the same problem, or, lack of feature, with SequenceMatcher. Gabriel, Differ doesn't seem to have the functionality, or an easy way to patch it to get the functionality, that Christian is talking

[ python-Bugs-1711800 ] SequenceMatcher bug with insert/delete block after replace

thread, including the initial issue submission, for this request, not just the latest update. Category: Python Library Group: Python 2.6 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Hammond (chipx86) Assigned to: Nobody/Anonymous (nobody) Summary: SequenceMatcher bug

[ python-Bugs-1711800 ] SequenceMatcher bug with insert/delete block after replace

thread, including the initial issue submission, for this request, not just the latest update. Category: Python Library Group: Python 2.6 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Hammond (chipx86) Assigned to: Nobody/Anonymous (nobody) Summary: SequenceMatcher bug

[ python-Bugs-1711800 ] SequenceMatcher bug with insert/delete block after replace

: SequenceMatcher bug with insert/delete block after replace Initial Comment: difflib.SequenceMatcher fails to distinguish between a replace block and an insert or delete block when the insert/delete immediately follows a replace. It will lump both changes together as one big replace block. This happens