Broken classes pickled when container changed
Bug #589756 reported by
Sylvain Viollon
This bug report is a duplicate of:
Bug #143531: Broken objects should give access to their state.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zope 2 |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
How to reproduce in Zope 2.12:
1. Create two objects in a folder in your ZODB,
2. Remove the filesystem code of those objects (to get Broken objects), and restart your Zope,
3. Select one of those object and delete it (ZMI, code, whatever),
4. You get a pickling error on the folder (container) trying to pickle the Broken object that have been removed at step 3.
This worked perfectly in the past, including Zope 2.11.
The change triggering this bug most likely occurred in ExtensionClass and Persistance 2.13.0 (with 2.12.0 the bug is not reproducible).
Revision history for this message
| Hanno Schlichting (hannosch) wrote | #1 |
| Changed in zope2: | |
| importance: | Undecided → Low |
| Changed in zope2: | |
| status: | New → Confirmed |
Revision history for this message
| Sylvain Viollon (thefunny) wrote | #2 |
To post a comment you must log in.
Could you try to reproduce this with the current Zope 2.12 SVN branch. Godefroid fixed LP143531 which gives broken objects access to their state (it's reusing the ZODB.broken implementation now).