Bug 43617 - Port PrettyPatch.rb to Python
Summary: Port PrettyPatch.rb to Python
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-06 04:12 PDT by Kent Tamura
Modified: 2012-04-05 20:32 PDT (History)
4 users (show)

See Also:


Attachments
Patch (24.47 KB, patch)
2010-08-06 04:25 PDT, Kent Tamura
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kent Tamura 2010-08-06 04:12:34 PDT
Port PrettyPatch.rb to Python in order to avoid ruby dependency
Comment 1 Kent Tamura 2010-08-06 04:25:40 PDT
Created attachment 63713 [details]
Patch
Comment 2 Adam Roben (:aroben) 2010-08-06 06:57:34 PDT
Interesting. Is Ruby not available on some systems that need to use PrettyPatch?

I have no philosophical objection to rewriting in Python.

I think Python's difflib.SequenceMatcher could replace your DiffBuilder.
Comment 3 Mark Rowe (bdash) 2010-08-06 14:51:59 PDT
The WebKit project has a number of scripts that are written in Ruby.  Why is this suddenly a problem?
Comment 4 Kent Tamura 2010-08-07 00:59:59 PDT
Ruby is used only for PrettyPatch on Chromium port.  Ruby is available on all Chromium platforms, but we'd like to minimize dependency as possible.

We're setting up Chromium buildbots for tests.  The webkitpy-test step is failing because the buildbot machine has no ruby [1].  We can install ruby, but we'd like to avoid to install it if possible.


> I think Python's difflib.SequenceMatcher could replace your DiffBuilder.

Thanks. I'll try it after I confirm the Python version of PrettyPatch works.


[1] http://build.webkit.org/builders/Chromium%20Linux%20Release%20(Tests)/builds/3340/steps/webkitpy-test/logs/stdio
Comment 5 Mark Rowe (bdash) 2010-08-07 01:17:50 PDT
I would prefer that Ruby be installed, since several recently-added scripts have been written in Ruby and it’s not out of the question that they may be used by the Chromium build in the future.  Rewriting in a different language for the sake of it seems like a bad idea to me.
Comment 6 Kent Tamura 2012-04-05 20:32:50 PDT
I won't work on it because of objections.