Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #21364 > unrolled thread

Re: pickle/unpickle class which has changed

Started byGelonida N <gelonida@gmail.com>
First post2012-03-08 01:16 +0100
Last post2012-03-08 01:16 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: pickle/unpickle class which has changed Gelonida N <gelonida@gmail.com> - 2012-03-08 01:16 +0100

#21364 — Re: pickle/unpickle class which has changed

FromGelonida N <gelonida@gmail.com>
Date2012-03-08 01:16 +0100
SubjectRe: pickle/unpickle class which has changed
Message-ID<mailman.498.1331165808.3037.python-list@python.org>
On 03/07/2012 09:04 AM, Peter Otten wrote:
> Gelonida N wrote:

> If you know in advance that your class will undergo significant changes you 
> may also consider storing more stable data in a file format that can easily 
> be modified, e. g. json.
> 
Good point, that's what I'm partially doing. I just wondered whether
there were already some kind of pre-existing data migration tools /
concepts / helpers like for example south for Django or whether I had to
roll my own migration scheme for persistent non DB data.




[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web