-> 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? This seems more like test-code, rather than a real-world usage -> case...
The problem is that while it doesn't make *too* much sense in a script, it is something that one could inadvertently or casually do in a framework or larger program where multiple files might be communicating by saving stuff in pygr.Data. cheers, --titus -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
