* Chris McDonough <chr...@plope.com> [2011-08-28 21:35]: > Pyramid doesn't actually require ZCML or zope.schema; it only uses > the parts of zope.configuration related to actions, conflict > resolution, and the "ConfigurationMachine" itself. These bits have > proven useful outside the context of ZCML and other schema-driven > configuration. > > I have tackled this issue by factoring zope.configuration into > two pieces: > - I have moved the bits that don't rely on ZCML or zope.schema > into a new 'zope.configmachine' package > - I have made zope.configuration which depends on > zope.configmachine in a branch:
Splitting zope.configuration into core mechanics and ZCML support makes a lot of sense to me. I'm not too hot about the "zope.configmachine" name, because it's all mechanics and not much intention, but I realize the bikeshedding danger here. So, +1 from me. Wolfgang -- Wolfgang Schnerring · w...@gocept.com · software development gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 219401 0 · fax +49 345 1229889 1 Python, Pyramid, Plone, Zope - consulting, development, hosting _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
