[Persistence-sig] persistence to code-related-object?

[Jeff Sasmor]

I'd respectfully suggest looking at the augmented
imputils found on the mcmillan website:

http://www.mcmillan-inc.com/importhooks.html

I found this reasonably easy to extend this to
my project. How one would wedge this in
to supporting any arbitrary Python code, that is,
something without a way of specifying 
a 'path' to a class as in:

from whatever.x import something

is another matter; I never explored that aspect 
since I was only trying to solve one problem!


jeff

#--------------------------------
Jeff Sasmor
jeff@sasmor.com
----- Original Message ----- 
From: "Jeremy Hylton" <jeremy@alum.mit.edu>
To: "Jeff Sasmor" <jsasmor@gte.net>
Cc: <persistence-sig@python.org>
Sent: Monday, August 26, 2002 11:53 AM
Subject: Re: [Persistence-sig] persistence to code-related-object?


I suspect that transparently storing code in the database is an
advanced topic that won't be addressed by the PEPs, although I'm happy
to consider it if it ends up being an important requirement.

It is an important requirement for Zope, and we've got an incomplete
version in the ZODB4 code base.  It's based on ihooks, rather than
imputils.  Paolo has also pointed out that we've got a write-only
implementation at the moment :-(.  None of the tests verify that a
class can be reloaded from the database.

Jeremy




_______________________________________________
Persistence-sig mailing list
Persistence-sig@python.org
http://mail.python.org/mailman-21/listinfo/persistence-sig