Can not configure backends which require Python objects

Issue #4 resolved
created an issue

In order to skip rw_lockfile and dogpile_lockfile for DBMBackend one needs to provide False. There is no way to provide False from .ini files though.

Comments (4)

  1. kaukas reporter

    It works for my case.

    I use *.arguments.dogpile_lockfile = false to prevent the dogpile lock to temporarily circumvent the #5 bug about the nested creators.

    Thank you for the quick fix again!

  2. Log in to comment