Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-04-05 Thread Vadim ProductEngine
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/129/#review558 --- The code has been integrated. Merov, please close the review reque

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-02-11 Thread Merov Linden
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/129/ --- (Updated Feb. 11, 2011, 6:23 p.m.) Review request for Viewer. Changes ---

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-02-10 Thread Oz Linden
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/129/#review353 --- Ship it! Those changes look good. For future reference, there's

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-02-09 Thread Merov Linden
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/129/ --- (Updated Feb. 9, 2011, 3:33 p.m.) Review request for Viewer. Changes

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-01-31 Thread Merov Linden
> On Jan. 31, 2011, 11:47 a.m., Kent Quirk wrote: > > I would much prefer that we put the /usr/bin/env python form, since env can > > find whichever python is currently set up, including someone that has it in > > /usr/local/bin, or wherever they've chosen. Env is more likely to be found > > i

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-01-31 Thread Balp Allen
> On Jan. 31, 2011, 6:27 a.m., Vadim ProductEngine wrote: > > Why didn't you choose "!/usr/bin/env python"? It seems more flexible. !/usr/bin/env python, is the standard python way, and i think is what should always be used on python scripts. - Balp -

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-01-31 Thread Vadim ProductEngine
> On Jan. 31, 2011, 11:47 a.m., Kent Quirk wrote: > > I would much prefer that we put the /usr/bin/env python form, since env can > > find whichever python is currently set up, including someone that has it in > > /usr/local/bin, or wherever they've chosen. Env is more likely to be found > > i

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-01-31 Thread Kent Quirk
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/129/#review286 --- I would much prefer that we put the /usr/bin/env python form, sinc

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-01-31 Thread Vadim ProductEngine
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/129/#review284 --- Why didn't you choose "!/usr/bin/env python"? It seems more flexib

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-01-29 Thread Boroondas Gupte
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/129/#review276 --- Ship it! Covers all occurrences of the variant with env, so shoul

Re: [opensource-dev] Review Request: Use consistent path for all *.py scripts

2011-01-28 Thread Nicky Perian
--- This is an automatically generated e-mail. To reply, visit: http://codereview.secondlife.com/r/129/#review275 --- Ship it! Looks like a good consistency improvement. - Nicky On