On Tuesday, February 17, 2015 at 1:30:01 PM UTC-5, David Glick wrote: > > It's an explicit design goal of Pyramid that application developers not > have to understand the ZCA even when it's used internally: > > http://docs.pylonsproject.org/projects/pyramid/en/latest/designdefense.html#ameliorations > > > As a long time developer of Plone, which misuses the ZCA as a public API > a lot, I'd hate to see Pyramid go very far in that direction. >
I'm concerned about people needing to extend Pyramid via plugins. Basically these people on that document: However, unlike application developers, *framework developers*, including people who want to override Pyramid functionality via preordained framework plugpoints like traversal or view lookup *must* understand the ZCA registry API. One only needs a very small understanding of zope in order to create plugins/etc that rely on Pyramid's various interfaces -- but the must do a lot of reading on zope to find that relevant material. A few paragraphs, in line with the docs on Michael's new package which are ridiculously amazing, could eliminate the need to sift through any of zope's documents. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
