BlueBream

Generation 4 evolution script doesn't remove RegistrationManagers

Bug #98355 reported by Philipp von Weitershausen
2
Affects Status Importance Assigned to Milestone
BlueBream
New
Undecided
Unassigned
Zope 3
Won't Fix
Critical
Unassigned
Zope 3 3.4rc1
Declined for 3.1 by Christian Theune
3.4
Won't Fix
Critical
Unassigned
Zope 3 3.4rc1

Bug Description

The generation 4 evolution script (evolve4.py) doesn't remove RegistrationManagers. I took a Zope 3.1-based ZODB instanced, evolved it and still get:

/Users/philipp/dev/Zope3/src/ZODB/broken.py:187: DeprecationWarning: RegistrationManager is deprecated. The old registration APIs, are deprecated and will go away in Zope 3.5

Of course, if the "fix" is to remove RegistrationManagers when evolving, we need a new generation because people might already have evolved to generation 4.

Revision history for this message
Stephan Richter (srichter) wrote :

Changes: submitter email, importance (medium => critical)

Revision history for this message
Christian Theune (ctheune) wrote :

Targetting the RC.

Revision history for this message
Albertas Agejevas (alga) wrote :

Hypothesis: evolve4.py only evolves the root site manager, and this is a bug. Could it be that the database you were migrating had a local site manager other than the one on the root folder?

Christian Theune (ctheune)
Changed in zope3:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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