On Sunday 25 March 2007 16:44, Steven Bethard wrote:
> Anastasios Hatzis wrote:
> > I'm working on a tool which is totally command-line based and consisting
> > of multiple scripts. The user can execute a Python script in the shell,
> > this script does some basic verification before delegating a c
Anastasios Hatzis wrote:
> I'm working on a tool which is totally command-line based and consisting of
> multiple scripts. The user can execute a Python script in the shell, this
> script does some basic verification before delegating a call into my tool's
> package and depending on some argumen
On Saturday 24 March 2007 18:55, [EMAIL PROTECTED] wrote:
> On Mar 24, 10:31 am, Anastasios Hatzis <[EMAIL PROTECTED]> wrote:
> > I'm looking for a pattern where different client implementations can use
> > the same commands of some fictive tool ("foo") by accessing some kind of
> > API. Actually I
On Mar 24, 10:31 am, Anastasios Hatzis <[EMAIL PROTECTED]> wrote:
> I'm looking for a pattern where different client implementations can use the
> same commands of some fictive tool ("foo") by accessing some kind of API.
> Actually I have the need for such pattern for my own tool
> (http://openswar
I'm looking for a pattern where different client implementations can use the
same commands of some fictive tool ("foo") by accessing some kind of API.
Actually I have the need for such pattern for my own tool
(http://openswarm.sourceforge.net). I already started restructuring my code
to separat
