[Zope3-checkins] SVN: Zope3/trunk/src/zope/app/authentication/principalfolder.py Added BBB for older instances

Roger Ineichen r.ineichen at projekt01.ch
Thu Nov 3 18:37:44 EST 2005


Hi Dimitry

> 
> Roger Ineichen wrote:
> > Log message for revision 39855:
> >   Added BBB for older instances
> > 
> > Changed:
> >   U   Zope3/trunk/src/zope/app/authentication/principalfolder.py
> > 
> > -=-
> > Modified: Zope3/trunk/src/zope/app/authentication/principalfolder.py
> > ===================================================================
[...]
> >  
> >      interface.implements(IInternalPrincipal, 
> IInternalPrincipalContained)
> >  
> > +    _passwordManagerName = "Plain Text"
> > +
> >      def __init__(self, login, password, title, description=u'',
> >              passwordManagerName="Plain Text"):
> >          self._login = login
> 
> This is unnecessary since there is new database generation at 
> http://localhost:8080/++etc++process/@@generations.html which add 
> self._passwordManagerName and also convert self.password to 
> self._password, so 
> you need to evolve anyway. I think this change just will be 
> masks future 
> password problems, since self.password is a property now.

I see, I didn't recognize the evolve implementation.

Is there a way to evolve durring the bootstrap process? Or is the 
manuel process via the ZMI the right way?

What do you think,should I remove the _passwordManagerName
class attribute, which will break instances in un-evolved 
databases. Right now with this changes the views are not broken.
Without the _passwordManagerName the views where will access the 
InternalPrincipal are broken because oft the missing attribute they 
call. What do you recommend?

Regards
Roger Ineichen

Projekt01 GmbH
_____________________________
END OF MESSAGE 

> Dmitry Vasiliev (dima at hlabs.spb.ru)
>      http://hlabs.spb.ru
> 



More information about the Zope3-Checkins mailing list