[Zope-CMF] changing typeinfo_name behaviour in CMF 1.6

Rob Miller ra at burningman.com
Fri Dec 30 05:41:49 EST 2005


currently, in the TypesTool.manage_addTypeInformation method in CMF 1.6, 
if a typeinfo_name argument is passed in and the corresponding fti is 
not found in the results of listDefaultTypeInformation, an error is 
raised.  in CMF 2.0, this argument is ignored completely.

in 1.6, some types will be listed in the listDefaultTypeInformation 
while others will not, depending on whether those types were defined 
using a GenericSetup profile or if it was done old-style.

would anyone foresee a problem w/ changing the behaviour of this such 
that an error isn't raised when the typeinfo_name isn't found?

-r



More information about the Zope-CMF mailing list