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

Do we want to support non-dict backends? #220

Open
fwkoch opened this issue Feb 15, 2018 · 0 comments
Open

Do we want to support non-dict backends? #220

fwkoch opened this issue Feb 15, 2018 · 0 comments

Comments

@fwkoch
Copy link
Contributor

fwkoch commented Feb 15, 2018

This was a thought very early in the life of properties, but nothing has come of it. The idea is that properties may become an interface for a database, where underlying property values are stored somewhere a bit more robust than just a dictionary.

In practice, though, properties has worked well as a user interface separated from the database by serialize/deserialize. The close connection of _backend to a database has not been necessary.

Is there any merit to the idea of "swappable backends"? My current thinking is "no" but maybe there is.

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

No branches or pull requests

1 participant