On Wednesday, April 2, 2014 4:33:07 PM UTC-7, Jason Swails wrote:
> From there, you can implement a method interface in which the child Cmd
> subclasses can call to indicate to BossCmd that do_exit has been called and
> it should quit after the child's cmdloop returns. So something like this:
>
On Wed, Apr 2, 2014 at 1:03 AM, Josh English wrote:
> I have a program with several cmd.Cmd instances. I am trying to figure out
> what the best way to organize them should be.
>
> I've got my BossCmd, SubmissionCmd, and StoryCmd objects.
>
> The BossCmd object can start either of the other two, a
On Apr 2, 2014, at 1:03 AM, Josh English wrote:
> I have a program with several cmd.Cmd instances. I am trying to figure out
> what the best way to organize them should be.
>
> I've got my BossCmd, SubmissionCmd, and StoryCmd objects.
>
> The BossCmd object can start either of the other two, a
I have a program with several cmd.Cmd instances. I am trying to figure out what
the best way to organize them should be.
I've got my BossCmd, SubmissionCmd, and StoryCmd objects.
The BossCmd object can start either of the other two, and this module allows
the user switch back and forth between
