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


Groups > comp.lang.python > #8002

Re: running multiple scripts -- which way is more elegant?

References <BANLkTi=t9cHtPN6QOa4eUWuraZToOZxnoQ@mail.gmail.com> <BANLkTi=hHPo3ap9Cys40DX7wGdTEbn44OQ@mail.gmail.com>
Date 2011-06-20 08:21 +0200
Subject Re: running multiple scripts -- which way is more elegant?
From Florencio Cano <florencio.cano@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.172.1308550899.1164.python-list@python.org> (permalink)

Show all headers | View raw


> I'd be inclined toward the second solution if I'm writing all the code
> myself, but very definitely the first if someone else might write one
> of the subscripts (especially so if this is going to be distributed
> widely) - spawning a new process means that the system's isolation of
> processes keeps your system safe. If you don't need that measure of
> protection, I would still surround the import and check() call with
> try/except and gracefully handle any errors.

I'm with Chris, if the config_scripts are going to be implemented in
Python always, the second solution is better for me as the operative
system is less involved. But if you would like to have scripts with
different nature, the first one is best. What about to implement the
two alternatives depending on the config_script type?

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


Thread

Re: running multiple scripts -- which way is more elegant? Florencio Cano <florencio.cano@gmail.com> - 2011-06-20 08:21 +0200

csiph-web