Error importing objects 2.8 > 2.7
*Been working up some code on a zope 2.8.0 install, and I wanted to move it over to a live server. I keep getting this error: Error Type: AttributeError* *Error Value: 'module' object has no attribute '__newobj__' The new server is curious becuase it reads: * Zope Version (unreleased version, python 2.2.3, linux2) Python Version 2.2.3 (#1, Aug 8 2003, 08:44:02) [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-13)] This was an RPM install as far as I remember. 2.7 I think Do I need to get 2.8.0 on this production box, or is there an easy fix to get this .zexp imported? thanks for any tips! -e-
On 1/27/06, Ed Colmar <ed@greengraphics.net> wrote:
*Been working up some code on a zope 2.8.0 install, and I wanted to move it over to a live server. I keep getting this error:
i've had problems moving stuff (zclass, .zexp) between 2.7 and 2.8 iirc, there were major changes between the two. your best bet would be upgrading your live server to 2.8 too hth -- http://myzope.kedai.com.my - my-zope org
--On 26. Januar 2006 14:55:40 -0800 Ed Colmar <ed@greengraphics.net> wrote:
*Been working up some code on a zope 2.8.0 install, and I wanted to move it over to a live server. I keep getting this error:
Importing stuff from a new Zope version into an older Zope version was _never_ a supported feature. Only import between _identical_ versions. Anything else makes little sense and is unsupported. -aj
Andreas Jung wrote at 2006-1-27 07:04 +0100:
... Importing stuff from a new Zope version into an older Zope version was _never_ a supported feature. Only import between _identical_ versions. Anything else makes little sense and is unsupported.
Of course, you might be happy when you can import into a newer Zope version from an older one. At least, that makes some sense :-) -- Dieter
--On 27. Januar 2006 22:32:07 +0100 Dieter Maurer <dieter@handshake.de> wrote:
Andreas Jung wrote at 2006-1-27 07:04 +0100:
... Importing stuff from a new Zope version into an older Zope version was _never_ a supported feature. Only import between _identical_ versions. Anything else makes little sense and is unsupported.
Of course, you might be happy when you can import into a newer Zope version from an older one. At least, that makes some sense :-)
Of course we would be happy if we could do that. But export/import was never designed to deal with migration issue. This is very much an application side problem. Btw. Jim has written a "generations" module which looks like a promising framework to deal with implicit migrations in a sane way. -aj
Andreas Jung wrote at 2006-1-28 09:04 +0100:
--On 27. Januar 2006 22:32:07 +0100 Dieter Maurer <dieter@handshake.de> wrote:
Andreas Jung wrote at 2006-1-27 07:04 +0100:
... Importing stuff from a new Zope version into an older Zope version was _never_ a supported feature. Only import between _identical_ versions. Anything else makes little sense and is unsupported.
Of course, you might be happy when you can import into a newer Zope version from an older one. At least, that makes some sense :-)
Of course we would be happy if we could do that. But export/import was never designed to deal with migration issue.
Export/import is essentially what the ZODB does all the time. If export/import does not work between given Zope versions, it is quite likely that the same Zope versions will have difficulties with storages exchange -- and this *IS* a migration issue, Zope should be concerned with (and not the applications). If it does, export/import will simply follow (in most cases). -- Dieter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dieter Maurer wrote:
Andreas Jung wrote at 2006-1-28 09:04 +0100:
--On 27. Januar 2006 22:32:07 +0100 Dieter Maurer <dieter@handshake.de> wrote:
Andreas Jung wrote at 2006-1-27 07:04 +0100:
... Importing stuff from a new Zope version into an older Zope version was _never_ a supported feature. Only import between _identical_ versions. Anything else makes little sense and is unsupported.
Of course, you might be happy when you can import into a newer Zope version from an older one. At least, that makes some sense :-)
Of course we would be happy if we could do that. But export/import was never designed to deal with migration issue.
Export/import is essentially what the ZODB does all the time.
If export/import does not work between given Zope versions, it is quite likely that the same Zope versions will have difficulties with storages exchange -- and this *IS* a migration issue, Zope should be concerned with (and not the applications).
If it does, export/import will simply follow (in most cases).
Agreed: for "forward-migration" of data, Zope has historically tried *very* hard to ensure that objects which had been created under an older version of Zope would be unpicklable under a newer version: we have treated the exceptions as serious bugs (where the problem was not due to third-party application code, anyway). However, the original poster wants to be able to import a .zexp file exported from a *newer* version of Zope into an *older* version. Keeping that path open has *not* been a goal for Zope, and so the OP needs to find another way to solve his problem. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD2/hz+gerLs4ltQ4RAjcnAKC8wR36zfc8Q5X8PduwYnWYr26tOgCdE0ca GTQkMwmmhXM76Y67b3PBg7w= =s9Qh -----END PGP SIGNATURE-----
--On 28. Januar 2006 20:34:06 +0100 Dieter Maurer <dieter@handshake.de> wrote:
Export/import is essentially what the ZODB does all the time.
If export/import does not work between given Zope versions, it is quite likely that the same Zope versions will have difficulties with storages exchange -- and this *IS* a migration issue, Zope should be concerned with (and not the applications).
Possibly we are talking about different things. A most common mistake of Zope especially Plone users is to think that export/import acts as a migration tool (export your Plone 2.0 site on system A and reimport it into a Plone 2.1 installation on system B). This does usually never work when the internal data structures have changes (you know that :-)). Supporting such migration support for Zope core was/is always a goal since we have the app (Zope) in our hands but we can not sell export/import as a universal migration tool. 3rd-party apps have to deal with that. -aj
participants (5)
-
Andreas Jung -
Bakhtiar A Hamid -
Dieter Maurer -
Ed Colmar -
Tres Seaver