shelve

I'm trying to write a program that uses a shelve database of sorted letters as key, and a list of words that can be created from them as values. e.g: db['mnoo'] = ['moon', 'mono'] So I wrote a function that takes a filename and loads it into a shelve. The first part, that turns the file into a dictionary with the same layout as the shelve works fine, but the shelve part takes really long. I'm trying it with a dictionary of ~100k entries, each value being a list. It seems to take 15-20 seconds for each 1000 enteries, and each entry seems to take ~1kb of space. Is this nromal? the code: def save

I've been saving a bunch of dictionaries to file using Python's shelve module (with Python 3.4 on OSX 10.9.5). Each key is a string of an int (e.g., "84554" ), and each value is a dictionary of dictionaries of a few smallish strings. No keys are used twice, and I know the total superset of all possible keys. I am adding these key-value pairs to the shelf via threads and which keys/values are added changes each time I run it (which is expected). The problem I've been having is that the number of keys iterable/visible with shelve 's shelf.keys() and the number of unique keys for which key in

I am trying to make a simple password-storing program in Python, and it seems pretty simple so I am wondering if I am using shelve wrong. I have the main .py file: import shelve passwords = shelve.open('./passwords_dict.py') choice = raw_input("Add password (a) or choose site (c)?") if choice[0] == 'a': site_key = raw_input("Add for which site? ").lower() userpass = raw_input("Add any info such as username, email, or passwords: ") passwords[site_key] = userpass else: site = raw_input("Which site? ").lower() if site in passwords: print "Info for " + site + ": " + passwords[site] else: print

If i'm working on some files that I don't want to commit, I just save them. I then have other files I want to push to the server, however if someone else has made changes to the repository, and I pull them down, it asks me to merge or rebase.. but either of these options will cause me to lose my local changes that I have not committed . What are other people doing to get around this? I find the documentation for the shelving extension hard to get my head around. Note: I'm using Mercurial Eclipse to push and pull files to/from the server. Any explanation of this would be greatly appreciated!

How can I serialize hash objects?, I'm using shelve to store a lot of objects. Hierarchy: - user - client - friend user.py: import time import hashlib from localfile import localfile class user(object): _id = 0 _ip = "127.0.0.1" _nick = "Unnamed" _files = {} def __init__(self, ip="127.0.0.1", nick="Unnamed"): self._id = hashlib.sha1(str(time.time())) self._ip = ip self._nick = nick def add_file(self, localfile): self._files[localfile.hash] = localfile def delete_file(self, localfile): del self._files[localfile.hash] if __name__ == "__main__": pass client.py: from user import user from friend

I just tried a Python shelve module as the persistent cache for data fetched from the external service. The complete example is here . I was wondering what would the best approach if I want to make this multiprocess safe? I am aware of redis, memcached and such "real solutions", but I'd like to use only the parts of Python standard library or very minimal dependencies to keep my code compact and not introduce unnecessary complexity when running the code in single process - single thread model. It's easy to come up with a single-process solution, but this does not work well current Python web

Our team is just getting started with Mercurial. One of the first things we've started to play with is hg shelve . Locally, I have no problem shelving changes. It all works perfectly from what I can tell. However, when I try to unshelve, I get the restoring backup files message, but when I run hg diff , there are no changes, and my changes are missing from the code. If i do hg unshelve -i I can see the diff, but again, trying to unshelve seems to have no effect. I've been trying to test it with some very simple changes that shouldn't be a problem in terms of conflicts, e.g. adding a test