Re: [Zope-dev] RFC: proposal to split zope.configuration into ZCML and non-ZCML related packages
On Wed, 2011-08-31 at 10:59 +0200, Hanno Schlichting wrote: On Wed, Aug 31, 2011 at 9:17 AM, Wolfgang Schnerring w...@gocept.com wrote: Splitting zope.configuration into core mechanics and ZCML support makes a lot of sense to me. So, +1 from me. +1 here too It turns out that we were using so little of zope.configuration in the Pyramid core that it was much to replace it than it is to port this stuff (and write docs/unittests) so I withdraw this proposal. FTR, apologies, it's a bit lame of me to not help with a zope.configuration Python 3 porting effort and just fork and steal bits of code I need. We do still depend on the entirety of zope.configuration in an add-on package named pyramid_zcml, so if there is call to port that to Python 3, I may revisit this topic. - C ___ 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 )
Re: [Zope-dev] RFC: proposal to split zope.configuration into ZCML and non-ZCML related packages
* 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 )
Re: [Zope-dev] RFC: proposal to split zope.configuration into ZCML and non-ZCML related packages
On Wed, Aug 31, 2011 at 9:17 AM, Wolfgang Schnerring w...@gocept.com wrote: Splitting zope.configuration into core mechanics and ZCML support makes a lot of sense to me. So, +1 from me. +1 here too Hanno ___ 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 )
