Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #30279
| From | Dieter Maurer <dieter@handshake.de> |
|---|---|
| Subject | Re: python application file format |
| Date | 2012-09-27 08:55 +0200 |
| References | <5062F9D6.2060402@abzinc.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1477.1348728933.27098.python-list@python.org> (permalink) |
Benjamin Jessup <bsj@abzinc.com> writes: > ... > What do people recommend for a file format for a python desktop > application? Data is complex with 100s/1000s of class instances, which > reference each other. > > ... > Use cPickle with a module/class whitelist? (Can't easily port, not > entirely safe, compact enough, expandable) This is the approach used by the ZODB (Zope Object DataBase). I like the ZODB. It is really quite easy to get data persisted. It uses an elaborate caching scheme to speed up database interaction and has transaction control to ensure persistent data consistency in case of errors. Maybe not so relevant in your context, it does not require locking to safely access persistent data in a multi thread environment. > ...
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: python application file format Dieter Maurer <dieter@handshake.de> - 2012-09-27 08:55 +0200
csiph-web