On Dec 18, 1:36 pm, Christopher Lee <[email protected]> wrote:
> The only question is what behavior you want. Why would anyone want to
> save an object to pygr.Data only to immediately ask for it back
> again?
Ok, but this was the shortest code that reproduces the behavior so it
does not have to make that much sense.
On the other hand saving an object, then retrieving the same object
later seems a common thing to do. It is really strange when you start
getting back different things just because another module may have
reloaded pygr.Data. Imagine a threaded webserver that reloads a
changed module, or a failed data attempt that now wants to obtain a
fresh copy of the data.
More to the point, in this particular case I don't even know what else
should one be doing (other than reload) to actually get the file
itself.
Istvan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
