![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
| Wed, 12 Dec 2001 03:23:14 +0000 (03:23 +0000) | ||
| committer | richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
| Wed, 12 Dec 2001 03:23:14 +0000 (03:23 +0000) | ||
| commit | c03acba5eb8438b6ad702c413735eed77764149d | |
| tree | 0aa3a5fa438593bf1afefe414da4282b371c02c4 | tree | snapshot |
| parent | e62eea814e1d35544f2337b2170963b889fd27b5 | commit | diff |
Cor blimey this anydbm/whichdb stuff is yecchy. Turns out that whichdb
incorrectly identifies a dbm file as a dbhash file on my system. This has
been submitted to the python bug tracker as issue #491888:
https://sourceforge.net/tracker/index.php?func=detail&aid=491888&group_id=5470&atid=105470
git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@456 57a73879-2fb5-44c3-a270-3262357dd7e2
incorrectly identifies a dbm file as a dbhash file on my system. This has
been submitted to the python bug tracker as issue #491888:
https://sourceforge.net/tracker/index.php?func=detail&aid=491888&group_id=5470&atid=105470
git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@456 57a73879-2fb5-44c3-a270-3262357dd7e2
| roundup/backends/back_anydbm.py | diff | blob | history |