Code

I fixed the problems with people whose anydbm was using the dbm module at the
authorrichard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2>
Wed, 12 Dec 2001 02:30:51 +0000 (02:30 +0000)
committerrichard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2>
Wed, 12 Dec 2001 02:30:51 +0000 (02:30 +0000)
commite62eea814e1d35544f2337b2170963b889fd27b5
tree9411b1d83b4431f5324c35a6a0bf7fe80b3a11a3
parentb27bf56b09a9630efe6fc809a4d9c4ff0d084fad
I fixed the problems with people whose anydbm was using the dbm module at the
backend. It turns out the dbm module modifies the file name to append ".db"
and my check to determine if we're opening an existing or new db just
tested os.path.exists() on the filename. Well, no longer! We now perform a
much better check _and_ cope with the anydbm implementation module changing
too!
I also fixed the backends __init__ so only ImportError is squashed.

git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@455 57a73879-2fb5-44c3-a270-3262357dd7e2
CHANGES.txt
roundup/backends/__init__.py
roundup/backends/back_anydbm.py