Erik Rose
Erik Rose
Wow, your tests are pretty CPU-intense. We're going to start doing multiprocess at Mozilla in the next few months, so I'm also interested in having this work.
Factoring Django out… ``` (py27)[12:34:50 ~/Checkouts/more-itertools]% time nosetests --processes=2 ~/Desktop/timetests.py .. ---------------------------------------------------------------------- Ran 2 tests in 10.036s OK nosetests --processes=2 ~/Desktop/timetests.py 0.20s user 0.08s system 2% cpu 10.239 total (py27)[12:35:59...
Hmm, this makes it look like the nose framework is hostile to incremental reporting of multiprocess results: "As each test or suite executes in a worker process, results (failures, errors,...
Of course, we should be able to at least not stymie parallelization.
Thanks for the patch! I'd actually like to generalize it a bit: because nose-progressive uses blessings (http://pypi.python.org/pypi/blessings/) under the covers, we can stop passing in codes for colors and start...
Not as is, I'm afraid, as I don't want to have to support the numeric specification of color forever. But supporting a textual description (like bold_red) should be a pretty...
Confirmed on my machine.
Moved from a code comment: We can either have extending callers pull the rule text out of repr, or we could get fancy and define `__add__` on Grammars and strings....
I guess we'll have to go with something heavier, like `__add__`, since the introduction of custom rules means Grammars are no longer completely round-trippable as strings.