[Schevo-devel] please read: latest changes will break existing databases.

[Matthew Scott]

On 9/22/05, David Binger <dbinger at mems-exchange.org> wrote:
>
>
> I think you could, on startup,
>
> import schevo.durus # or whatever
> sys.modules['durus'] = schevo.durus
>
> to keep your pickles operable.


Good tip. I'll make use of that in my conversion script, so that an
export/svn-update/import process won't be necessary.


Isn't there a way to have a software distribution that installs in
> one directory but
> acts as a collection of top-level python packages? I wonder if
> that would be
> better for cases like this.
>

I am not quite sure how exactly one does that. FYI, the main focus of
integrating PyDispatcher and Durus into the 'schevo' package is to prepare
it for making Python eggs. The cleanest way that Pat and I could come up
with to make sure Schevo always uses specific versions of those two packages
was to make sure they were inside the 'schevo' namespace.


Thanks for your help,

--
Matthew R. Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://schevo.org/lists/archives/schevo-devel/attachments/20050922/4dd1ca39/attachment.htm