0.3 release of peabody
README still points to bitbucket, fixing
updating README

- changed README.txt to README.rst to make GitHub happy
- added ideas about logstash output to the README
bitbucket -> github

found another bitbucket reference
collect stdout/stderr from child process!

this is in no way useful, but it is functional so I want to get it in
here for archaeologists to find and laugh at 100 years from now
refactored poller, way less of a mess

I still don't think I quite like the loop to do my own readline
splitting, and I don't really like the extra variable just to check if
we're at EOF, but this seems to work and seems to work pretty damn well
just some design notes, mostly

I added a debug print back in because I was testing with the child
process doing usleeps between writing output
nonfunctional poller module

committing so I can get some assistance as I try to wrap my head around
python's modules
extracted the poller out to its own module

also:
python has some interesting namespace issues.
stubbing out poller.loop method
logstash redis output!

it works. now I just need to make it ... less crappy :)
removing : in field names

apparently kibana doesn't like the : in field names.
make sure to send the rest of the buffer at EOF

previously the code was simply throwing anything away before EOF if
there wasn't a newline before the EOF.

I'd like to figure out a cleaner way to split these lines, but
.readline() blocks
fully configurable logstash redis output
make output capture optional
add in custom fields and tags, and custom type

forgot this in the last commit
make the logstash-tag metavar a little nicer
updating README
Merge branch 'feature/logstash-redis-output' into develop
ignore peabody.egg-info