Re: [Zope3-dev] zope.testbrowser packaging
extras are a terrible feature. They aren't fully supported by setuptools and they make it more complicated. Did you write tests for every permutation of your extras? Jim On Sep 15, 2007, at 9:44 PM, Stephan Richter wrote: On Saturday 15 September 2007 08:48, Benji York wrote: 1) introduce a zope extra that everyone will have to use (basically just rename test to zope; I prefer this solution. I have done this before for z3c.rml, where I put the page template support into a pagetemplate extra declaration. I liked this solution a lot. I would have never considered developing another package for a fairly trivial extension of a few lines. I think eggs have the potential for package proliferation and senseless overhead. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/jim%40zope.com -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.testbrowser packaging
Hi Benji. I don't like the first option. I am already using a zope extras to group packages for other reasons and don't really want to mix this with the test extra. I am trying to use extras as much as possible opposed to listing reams of packages in buildout.cfg to keep it cleaner and simpler. I don't mind the strange name to be honest, the namespaces are informative. Many thanks. Regards, David Benji York wrote: I have a small issue with zope.testbrowser packaging I'd like to get some input on. If I were to have started the project today, it would likely have been zc.testbrowser, which would have no Zope 3 dependencies (or functionality) and zc.testbrowser.zope, which would have, and depended on zc.testbrowser. Well, that didn't happen, but there are parallels to the current situation that might be informative. There is a configuration bug in testbrowser that means that unless you include the test extra, you won't get the Zope 3 dependencies. I suspect most people either include that extra, or accidentally include the dependencies through other packages. I have two ideas for fixing this: 1) introduce a zope extra that everyone will have to use (basically just rename test to zope; 2) take a lesson from the fictional zc.testbrowser and introduce another package (zope.testbrowser.zope) that contains the Zope 3 bits and depends on zope.testbrowser. I think I prefer the second, despite it's strange appearance. Thoughts? ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.testbrowser packaging
On Saturday 15 September 2007 08:48, Benji York wrote: 1) introduce a zope extra that everyone will have to use (basically just rename test to zope; I prefer this solution. I have done this before for z3c.rml, where I put the page template support into a pagetemplate extra declaration. I liked this solution a lot. I would have never considered developing another package for a fairly trivial extension of a few lines. I think eggs have the potential for package proliferation and senseless overhead. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com