Issue #112: Improvement to AmbiguousStep error (Change request)
Issue #113: Cleanup some typos, unneeded party (cherry-picked).
Add threading support
Update readme
Update README.rst

Update README.rst

Changing thread duration to be on same line as thread END

update readme

update readme again...

Would rather use multi processes, than threads, because trying to make stdout/err be
captured cleanly between mutliple threads in the same process is kinda crazy and
I see that python's nosetest & ruby's parallel_tests uses processes, not threads.

update readme

Updating readme again!

Almost got this working!

closer!

And... it works!

Renaming README.rst to README.md

Update README.md

Update README.md

Adding a progress indicator... of sorts...

Update README.md

Update README.md

Update README.md

Update README.md

Update README.md

Update README.md

printing tags on scenarios
moving scenario generating code in subprocesses out of while loop.
printing total scenarios found just before processing begins.

update readme

Changed multiprocessing.Queue to multiprocessing.Manager.JoinableQueue.
Apparently, this avoids some kind of deadlock that a child process may hang if the queue
it put stuff in is not emptied before the parent process calls join() on it.
See: http://docs.python.org/3/library/multiprocessing.html#multiprocessing-programming

Get rid of the runclone object because apparently referencing self is good enough

Oops, lost some work. Recovered using reflog
implement issue#1 and issue#2
update readme to document the newly added features
update readme.md with more details
Update readme yet again.
Update readme yet again#2
Re-adding status to each element in final report
Update README.md
Forgot a seperator in log output.
Decided @serial was better than @sequential
Add list of skipped steps due to error, to final report.
Update README.md
Change step.location to scenario.name for skipped-steps reporting.
Fix feature-counting bug in final report caused by code indentation. I need a vim plugin to show me things like that.
dont print a '@' in final-report for objects that have no tags
Update readme.