-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

yuppie wrote:
> Tres Seaver wrote:

>> How was this template working at all before?  If it was, do we have a
>> backwards-compatibility issue on these nocall; changes -- that is, will
>> this change break compatibility with a still-supported older version of
>> Zope?
> 
> This is related to upgrading zope.formlib and zope.app.form to 4.x. A 
> new base class seems to have a __call__ method that did not exist before.
> 
> But I didn't try to figure out what exactly changed because nocall: is 
> anyway what we always wanted. As long as the view can't be called it 
> doesn't make a difference, so I don't think we have a BBB issue.

Ah, ok -- thanks for the explanation.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tsea...@palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkwaFYQACgkQ+gerLs4ltQ6CJQCcCzUeJjJOM6opAh04P2ZAkoRN
A2EAniY+o8nhjOth709TxHhXirnG0eBh
=yW70
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

Reply via email to