loggerdb revamp:

We now support resuming on an old database, so long as it falls into the
previous genconfig.CandleSize period.

A new issue and TODO:
the avarice threading is still constant. What that means, is that if you
have a genconfig.CandleSize of 10, kill avarice, start it 5 minutes
later, then you will have a 15 minute candle on startup.

Also, even though we're no longer getting rid of this table, indicators
are still populating lists (not rows). This also means that RS gain avgs
are only read from the last and second to last price_list entries from
an avarice resume.
avarice: cleanup indicator cruft @Attious

I was failing with getattr, and it wasn't a python issue at all.
Rework indicators + Fast StochasticK Osc:

  - Rework SMA to support better external calling (will be useful with
    Stochastic %D style oscillators and more)
  - Run all indicators all the time, still only trade off one (see TODO)
  - Add a Fast StochasticK Oscillator
  - Rename StochRSI to StochRSIK as a preface to a StochRSID
    implementation
  - README: No longer planning on implementing indicators in sqlite
    tables. This is unnecesary since we now have persist capable
    price_list. The only indicator calculations which don't currently
    additionally persist are RS avg_gain and avg_loss calculations. This
    can be worked around in the future with a simple for/while set for
    the period when it exists, and not be done in real time two price
    pairs at a time (like current).
[WIP] indicators: massive common code cleanup

Does not yet function properly, but much needed cleanup
trader: catch possible exception

If we check and an order exists, but it completes before we either try
to get the order id, or cancel the order, we will get an IndexError
due to the list being out of range.

Let's catch this exception and let the user know the order has actually
completed
Merge branch 'indicator-cleanup'
README: project status update
Revert "loggerdb revamp:"

This reverts commit 0d0783117e88c08ae024e7fa134457f705e2fb87.
This caused major issues, and is not worth the possible convenience.

This software is intended to be run contiguously with fresh data each
instance.

Conflicts:
	README.md
	avarice.py
	indicators.py
Merge branch 'master' into working

Conflicts:
	avarice.py