[Zope-dev] zope-tests - FAILED: 10, OK: 91
This is the summary for test reports received on the zope-tests list between 2011-07-02 00:00:00 UTC and 2011-07-03 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received Bluebream / Python2.4.6 64bit linux Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.5 64bit linux [1]Repository policy check found errors in 305 projects Total languishing bugs for zope2: 0 [2]Total languishing bugs for zope: 59 [3]Total languishing bugs for zopeapp: 2 [4]Total languishing bugs for zopetoolkit: 200 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope Buildbot / zope2.12-py2.6 slave-osx Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.6 slave-osx Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-osx Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 [5]Zope Buildbot / zope2.13_win-py2.6 slave-win [6]Zope Buildbot / zope2.13_win-py2.7 slave-win Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-osx Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-osx Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win Zope Buildbot / zopetoolkit-1.1-py2.5 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-osx Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 [7]Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win [8]Zope Buildbot / zopetoolkit-1.1_win-py2.6 slave-win Zope Buildbot / zopetoolkit-py2.5 slave-osx Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-osx Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 [9]Zope Buildbot / zopetoolkit_win-py2.5 slave-win [10] Zope Buildbot / zopetoolkit_win-py2.6 slave-win Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_1
Re: [Zope-dev] [Zope-Checkins] SVN: Zope/trunk/ Removed the last remaining code to support `SOFTWARE_HOME` and `ZOPE_HOME`.
Hi Hanno,
I haven't checked deeply, but the change below seems to break
Products.ZSQLMethods. At least there is an import in
Products.ZSQLMethod from this location. And we depend heavily on it...
Since you're already around that piece of code, would you mind moving
it over there and releasing a new version of Products.ZSQLMetods? I
would be most thankful.
Cheers,
Leo
On Sun, Jul 3, 2011 at 17:19, Hanno Schlichting wrote:
> Log message for revision 122084:
> Removed the last remaining code to support `SOFTWARE_HOME` and `ZOPE_HOME`.
>
>
> Changed:
> [...]
> U Zope/trunk/src/App/Extensions.py
> [...]
> -
> -class NoBrains:
> - pass
> -
> -
> -def getBrain(module, class_name, reload=0, modules=None):
> - """ Check/load a class from an extension.
> - """
> - if not module and not class_name:
> - return NoBrains
> -
> - if modules is None:
> - c=getObject(module, class_name, reload)
> - else:
> - c=getObject(module, class_name, reload, modules=modules)
> -
> - if getattr(c, '__bases__', None) is None:
> - raise ValueError('%s, is not a class' % class_name)
> -
> - return 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] direction
On Sun, 2011-07-03 at 17:44 +0200, Hanno Schlichting wrote: > > I don't have any skin in this game, but FTR, Mike Bayer isn't feeling > > all that confident about Beaker's sessioning component (or so he has > > told me). Beaker was originally made as a caching component, and had > > sessioning jammed into it quite late; nobody is really maintaining the > > sessioning component of it now. > > Well, if I can choose between modern unmaintained code from Mike Bayer > and stone-age unmaintained code from Zope, it's still an easy choice > ;-) You might want to talk to Wiggy about that. He has a lot of experience with Beaker. > And looking at the basics of what Beaker does here, it's still much > more useful and of better quality than what we have in Zope 2. > > If there's any other non-framework-specific session machinery out > there, we could use that as well. But I think most other stuff is tied > into Django. Our attempt at penance (still framework specific) is here: http://agendaless.com/Members/tseaver/software/faster/faster-0.5.1/README.txt I don't know of any other sessioning libraries. - 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] direction
On 2011-7-3 17:48, Martin Aspeli wrote: > FWIW, we have a high-performance, high-load application in production on > Plone 4 with collective.beaker relying heavily on sessions, and I'm not > aware of any problems with it. We use the memcached backend across two > physical servers and a large number of Zope clients. In my experience it depends highly on the memcache client library you use with beaker. With some the results are disastrous, with other it is stable. Where possible I have switched to cookie-based sessions to prevent stability problems. Wichert. -- Wichert AkkermanIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ 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] direction
On 3 July 2011 16:44, Hanno Schlichting wrote: > On Sun, Jul 3, 2011 at 7:09 AM, Chris McDonough wrote: > > Zope still needs to the virtual host monster (or something like it) even > > with the WSGI publisher; there's nothing equivalent in the WSGI world > > (unless you could repoze.vhm, which is essentially just the virtual host > > monster, and probably doesn't need to live in middleware; no one uses it > > except people who use repoze.zope2). > > I'm expecting us to use repoze.vhm. But I've left the VHM in the code, > so it's easy to install one if you still need it. For some time I > expect Plone to install a VHM as part of its installation process. > > > I don't have any skin in this game, but FTR, Mike Bayer isn't feeling > > all that confident about Beaker's sessioning component (or so he has > > told me). Beaker was originally made as a caching component, and had > > sessioning jammed into it quite late; nobody is really maintaining the > > sessioning component of it now. > > Well, if I can choose between modern unmaintained code from Mike Bayer > and stone-age unmaintained code from Zope, it's still an easy choice > ;-) > > And looking at the basics of what Beaker does here, it's still much > more useful and of better quality than what we have in Zope 2. > > If there's any other non-framework-specific session machinery out > there, we could use that as well. But I think most other stuff is tied > into Django. FWIW, we have a high-performance, high-load application in production on Plone 4 with collective.beaker relying heavily on sessions, and I'm not aware of any problems with it. We use the memcached backend across two physical servers and a large number of Zope clients. Martin ___ 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] direction
On Sun, Jul 3, 2011 at 7:09 AM, Chris McDonough wrote: > Zope still needs to the virtual host monster (or something like it) even > with the WSGI publisher; there's nothing equivalent in the WSGI world > (unless you could repoze.vhm, which is essentially just the virtual host > monster, and probably doesn't need to live in middleware; no one uses it > except people who use repoze.zope2). I'm expecting us to use repoze.vhm. But I've left the VHM in the code, so it's easy to install one if you still need it. For some time I expect Plone to install a VHM as part of its installation process. > I don't have any skin in this game, but FTR, Mike Bayer isn't feeling > all that confident about Beaker's sessioning component (or so he has > told me). Beaker was originally made as a caching component, and had > sessioning jammed into it quite late; nobody is really maintaining the > sessioning component of it now. Well, if I can choose between modern unmaintained code from Mike Bayer and stone-age unmaintained code from Zope, it's still an easy choice ;-) And looking at the basics of what Beaker does here, it's still much more useful and of better quality than what we have in Zope 2. If there's any other non-framework-specific session machinery out there, we could use that as well. But I think most other stuff is tied into Django. 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 )
