> I fixed it. Please try to run "./gump test" before every commit, and
> make sure it completes without errors.

I will. (Further, I'll even add some test sooner or later, not just dilute
the code to test ratio. Promise. :-)

Since I'm trying to grab precious minutes of time here and there, the
problem will be me being in a big rush and forgetting. Sometimes I wish this
was something we could build into a script (tied into SVN, or wrapped
around) so we could make it an easy habit to adhere to.

Further, what I tried doing (before) was have gumptest be an entry that gump
runs, that is a <script> that do:

1) Run unit tests
2) Runs PyChecker [ http://pychecker.sourceforge.net/ ] (although I had
troubles figuring out how to dynamically find/pass modules as it wanted
them)
2) Exercises some command lines (e.g. "bash gump test").

I'd really appreciate completing the Gump3 workspace on Brutus (or wherever)
so we could have this working. It is "gump-like" to do this, and I'd like
this to be a first milestone in getting Gump3 working for folks.

regards,

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to