Oh, I didn't see your second post either. Sounds like porting everything into Python would speed up new-run-webkit-tests? Then I'm all for it. I think other folks would be equally convinced as well if you could kindly measure the time difference between Ruby + Python + shell script implementation vs Python implementation.
Hi Sam,
Did you see the reply I sent on this thread? There are actually decent
reasons to rewrite the code into Python, to simplify and speed up the
new-run-webkit-tests implementation. Given that, do you still object
to the patch landing (since the work has already been done)?
-- Dirk
> Sorry, I seemed to have missed this thread. Please do not rewrite scripts
> just to rewrite them in a language you like. WebKit's dependency on Ruby is
> here to stay. Just because python is common at Google does not make it
> universal.
> -Sam
>
> On Wed, Sep 1, 2010 at 4:48 PM, TAMURA, Kent <tkent@chromium.org> wrote:
>>
>> Thanks.
>> So porting PrettyPatch to Python will make good benefit and should have no
>> drawbacks. I should go ahead.
>>
>> On Wed, Sep 1, 2010 at 09:21, William Siegrist <wsiegrist@apple.com>
>> wrote:
>>>
>>> On Aug 31, 2010, at 4:43 PM, TAMURA, Kent wrote:
>>>
>>> > Can we run python scripts on bugs.webkit.org server?
>>>
>>> Yes.
>>>
>>> -Bill
>>>
>>
>>
>>
>> --
>> TAMURA Kent
>> Software Engineer, Google
>>
>>
>>
>>
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>
>
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev