Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #42012

Re: From Perl to Python: restructuring a HPC workflow

Show all headers | View raw

On Wed, Mar 27, 2013 at 10:29 PM, neurino <lelli.luca@googlemail.com> wrote:
> We are a small group of people (approx. 10), working separetely on their own
> projects (each employee manages approx. 2-3 projects). We deal with high
> loads of data everyday.
>
> This workflow has been flawless now for at least 15 years. New generations
> of employees have been given Perl scripts and they developed the tools
> further.

I would recommend making sure the tools can all interoperate
regardless of language, and then you can change any one at any time.
Chances are that's already the case - working with stdin/stdout is one
of the easiest ways to do that, for instance. With a structure that
lets anyone use any language, you can then switch some of your things
to Python, and demonstrate the readability advantages (which would you
rather code in, pseudocode or line noise?). Make the switch as smooth
as possible, and people will take it when it feels right.

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

From Perl to Python: restructuring a HPC workflow neurino <lelli.luca@googlemail.com> - 2013-03-27 12:29 +0100
  Re: From Perl to Python: restructuring a HPC workflow rusi <rustompmody@gmail.com> - 2013-03-27 04:51 -0700
    Re: From Perl to Python: restructuring a HPC workflow Joel Goldstick <joel.goldstick@gmail.com> - 2013-03-27 08:23 -0400
  Re: From Perl to Python: restructuring a HPC workflow Chris Angelico <rosuav@gmail.com> - 2013-03-27 23:58 +1100
    Re: From Perl to Python: restructuring a HPC workflow rusi <rustompmody@gmail.com> - 2013-03-29 05:20 -0700

csiph-web