BadPickleGet error during import in XML format

Bug #143381 reported by Adam Smith
2
Affects Status Importance Assigned to Milestone
Zope 2
Won't Fix
Medium
Unassigned

Bug Description

I am getting an error when exporting from Zope 2.7.4, Python 2.3.4 and importing to Zope 2.7.5, Python 2.4.1. If I do it as ZEXP file, everything works fine, but if I do it in XML format, I get an error that says: Error type: BadPickleGet Error value: 1. I want to do it in XML format because I want to save the file in a CVS repository along with a Zope product I am developing. When I tried to do this with a ZEXP file, I couldn't import it once it was checked into and out of CVS, so I figured a text formatted file would be a better choice. (But note that the BadPickleGet error I received was after doing a direct export and import, so CVS was not in the picture yet.)

Please let me know what other information might be helpful. Thanks in advance for any guidance you can give.

Tags: bug zope
Revision history for this message
Chris McDonough (chrism-plope) wrote :

Can't comment much on the XML export error, but note that as a workaround you can check a .zexp file into CVS with the -kb flag... e.g.

cvs add -kb myfile.zexp

That will tell CVS to treat the file as binary and won't attempt to expand keywords on a checkout.

Revision history for this message
Adam Smith (ajs17) wrote :

Thank you so much for the advice--that did the trick and makes an eventual fix a pretty low priority for me at least.

Revision history for this message
Hanno Schlichting (hannosch) wrote :

Chris suggested a workaround that fixed the reporters issue.

Changed in zope2:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.