[issue5942] Ambiguity in dbm.open flag documentation

Georg Brandl added the comment: It was my mistake -- anydbm is called dbm in py3k. -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue5942] Ambiguity in dbm.open flag documentation

Mitchell Model added the comment: No, I mean dbm.open. The third paragraph of its documentation says "'c' to create the database if it doesn’t exist, or 'n', which will always create a new empty database". This could easily be read as opening the database just for writing, although come to think

[issue5942] Ambiguity in dbm.open flag documentation

Georg Brandl added the comment: I think you meant anydbm? It's already documented well for dbm.open -- I've copied over that table to anydbm in r72710. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue5942] Ambiguity in dbm.open flag documentation

New submission from Mitchell Model : It isn't clear from the explanation of dbm.open's flag values at the beginning of the dbm documentation page whether 'c' and 'n' open the database just for writing or for reading and writing. I'm sure it's obvious to anyone familiar with dbm, and the example d