I back you up on this. The problem, on the other hand, is that : to see changes we need a dynamic, a momentum Lately, the work has been to maintain and not to push evolutions. What I'm currently trying to acheive, orchestrating that from the Grok community, is to try and open more and more zope packages to the outside world pluggability. If we can submit concrete ideas to the zope dev list and push them without giving it up to the global inertia, we might acheive something that would benefit everybody 2011/3/28 Sebastien Douche <sdouche@gmail.com>:
On Sat, Mar 26, 2011 at 15:18, Wolfgang Schnerring <ws@gocept.com> wrote:
Hi folks,
An honest counter question: Why not use zope.testrunner? What advantages does py.test offer?
On the technical side, I don't know. But from my point of view, the most important thing is the "social" side. I'm a bit tired to be "compartmentalized" : you must use "generics" tools (Nose, WebOb, Paster...) or Zope tools (Zope3, KGS, zope.testbrowser, zope.testing, zc.buildout, z3c.testsetup...). Pyramid is the first step in the right direction : the fusion of 3 communities (bfg, pylons, tg) with some Zope ideas. Thanks so much Chris and Ben, for the first time in my Python life, I see a fusion and not a fork. PSF said at last Pycon "PSF is the Python foundation, not the CPython foundation" and offers 10k$ to PyPy.
Sincerely, you rock my word: Buildout, Zope2, Zope3, Doctest, you created so many fantastic tools (I use Zope tools since 99), but now it's time to see outside the Zope world and share ideas and tools.
Sorry for the noise, it's just a cry of my heart.
-- Sebastien Douche <sdouche@gmail.com> Twitter: @sdouche (agile, lean, python, git, open source) _______________________________________________ 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 )