Don't install python shell script, as we now want to fall thru to cygwin....

Don't install python shell script, as we now want to fall thru to cygwin.

BUG=None
TEST=None


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=75789

[M-A Ruel, 2011-02-23 21:21:24]

lgtm

let's see the world auto-destroy. :)

[nsylvain, 2011-03-03 00:56:07]

Just noticed that this is actually breaking the bots because they call out to
depot_tools/svn directly. 

I can most likely fix the scripts on the bots to call svn.bat directly, but I'm
curious as why this change was made.  Is python/svn in cygwin not evil?

[Peter Kasting, 2011-03-03 01:00:15]

On 2011/03/03 00:56:07, nsylvain wrote:
> I can most likely fix the scripts on the bots to call svn.bat directly, but
I'm
> curious as why this change was made.  Is python/svn in cygwin not evil?

It is not evil, whereas running the non-cygwin python/svn are very evil.  They
are much slower and don't interact well with the shell/console.

[nsylvain, 2011-03-03 01:05:55]

On Wed, Mar 2, 2011 at 5:00 PM, <pkasting@chromium.org> wrote:

> On 2011/03/03 00:56:07, nsylvain wrote:
>
>> I can most likely fix the scripts on the bots to call svn.bat directly,
>> but
>>
> I'm
>
>> curious as why this change was made.  Is python/svn in cygwin not evil?
>>
>
> It is not evil, whereas running the non-cygwin python/svn are very evil.
>  They
> are much slower and don't interact well with the shell/console.

Ok, I guess your use case is different.  on the bots we use the command
prompt (with normal svn) 98% of the
time, but once in a while we need to use cygwin to run more complex scripts,
and if we use the cygwin svn there, it
might screw up our use of the normal svn later on.

But... I just convinced myself that the right thing to do is to force my
script to use svn.bat, as I'm the one with the weird use case.

Nicolas


>
>
> http://codereview.chromium.org/6579008/
>