initial commit, setting up for py 2 & 3
create first fixture for gdbm
create first test for gdbm fixture
take advantage of teardown of fixture to delete temp db file
added test to confirm correct number of keys in db, key exists, and key has correct value
add dubmdbm fixture and recognition test
removed the mixed remove statement from dumbdbm in gdbm and used the appropriate filename remove
adapted reading for dumbdbm.  also removed the '.dir' from the name being passed through.   Not needed for whichdb or .open
added test for dump-anydbm that uses module subprocess to run script
updated keys & vals to global predefined, added db type specification (for the differences between py2 & 3), finished up test for dump-anydbm with gdbm
updated test for dumbdbm.  dump-anydbm cannot run any dubmdbm, the test now reflects that
still having trouble gettting the ndbm module to correctly make an ndbm instead of bsd db. this fixture setup seems to work, tho bogglingly.  It creates 2 files, one ndbm & the other bsd db.  requires further investigation
updating the test fixture for ndbm.  whichdb needs the filename w/o '.db' to correctly identify and dbm.open does not the extension to read it
reconfigured dump-anydbm to check the output of whichdb instead of checking for file existence first.  This helps bypass the issue of an ndbm database only be recognized without its extension.  If which returns None, then the file does not exist, and if it returns '' then it cannot process it
cleaned up tests and removed unnecessary testing of fixtures.  Only test of dump-anydbm remain
Merge branch 'master' of https://github.com/khawley/warcprox

* 'master' of https://github.com/khawley/warcprox:
  ensure request headers always use \r\n (some servers barf if not, e.g. http://cleftomaniacsnyu.wix.com