dumpdb does not take dep_file configuration into account because it does not read (or require a dodo.py). It would be better to use dep_file information if available.
Original report:
.doit.delayed.db file exists.
$ ./delayed.py dumpdb
DBM type is 'None'
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/doit-0.29.0-py2.7.egg/doit/doit_cmd.py", line 168, in run
return command.parse_execute(args)
File "/usr/lib/python2.7/site-packages/doit-0.29.0-py2.7.egg/doit/cmd_base.py", line 122, in parse_execute
return self.execute(params, args)
File "/usr/lib/python2.7/site-packages/doit-0.29.0-py2.7.egg/doit/cmd_dumpdb.py", line 51, in execute
data = dbm.open(dep_file)
File "/usr/lib64/python2.7/anydbm.py", line 79, in open
raise error, "need 'c' or 'n' flag to open new db"
error: need 'c' or 'n' flag to open new db
[delayed.py.txt](https://github.com/pydoit/doit/files/159206/delayed.py.txt)
pydoit / doit
CLI task management & automation tool
1.9k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too