Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not configure backends which require Python objects #4

Closed
sqlalchemy-bot opened this issue May 2, 2012 · 5 comments
Closed

Can not configure backends which require Python objects #4

sqlalchemy-bot opened this issue May 2, 2012 · 5 comments
Labels

Comments

@sqlalchemy-bot
Copy link

Migrated issue, originally created by kaukas (kaukas)

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.

@sqlalchemy-bot
Copy link
Author

Changes by kaukas (kaukas):

  • edited description

@sqlalchemy-bot
Copy link
Author

Michael Bayer (zzzeek) wrote:

I put a basic translator for int, false, true, None in [[https://bitbucket.org/zzzeek/dogpile.cache/changeset/fcb7446102bd34713d5072f53ff829878b3c61c7|fcb7446102bd34713d5072f53ff829878b3c61c7]]. Hopefully this is enough; if not, we will have to make the backends receive a typed dictionary object from which they can request specific types.

@sqlalchemy-bot
Copy link
Author

Changes by Michael Bayer (zzzeek):

  • changed status to closed

@sqlalchemy-bot
Copy link
Author

kaukas (kaukas) wrote:

Thank you for the very quick response and fix! I will try it out and report how it works.

@sqlalchemy-bot
Copy link
Author

kaukas (kaukas) wrote:

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant