Re: [Zope-dev] Zope 2 WSGI investigation
On 3 January 2012 06:39, Chris McDonough wrote: > On Mon, 2012-01-02 at 10:39 +, Martin Aspeli wrote: >> On 2 January 2012 08:50, Wichert Akkerman wrote: >> > On 01/01/2012 08:39 PM, Martin Aspeli wrote: >> >> >> >> Hi, >> >> >> >> There are three known WSGI implementations of the Zope 2 publisher. >> >> I've had a look at them and made some notes about what I think >> >> provides the best story: >> >> >> >> ## Zope 2.13 WSGIPublisher >> >> >> >> Pros: >> >> >> >> * Allows distributed transaction management with repoze.tm2 >> >> * Allows distributed retry with repoze.retry >> >> * Ships with Zope >> >> * Quite simple >> >> >> >> Cons: >> >> >> >> * Requires repoze.tm2 and repoze.rety >> > >> > >> > Why is that a con? I use repoze.tm2 and repoze.retry with all my pyramid >> > projects and they work beautifully. >> >> Only insofar as it means you have to have these in your WSGI pipeline >> or it won't work, so there are more places things can go wrong. >> >> You'll note that I also consider not supporting such things a con for >> infrae.wsgi. I wouldn't get too hung up on it, I was mainly just >> trying to bring out the differences. It'd be nice if it wasn't a hard >> requirement, though. > > FWIW, when I wrote repoze.tm2 I did not know that the transaction module > already supported retry, so at least repoze.rety should die in favor of > logic in something-like-repoze.tm2 that looks a little more like this: > > https://github.com/Pylons/pyramid_tm/blob/master/pyramid_tm/__init__.py#L49 > > (that's obviously not WSGI middleware, I'm just showing what the general > logic should look like) Am I right in thinking Pyramid no longer uses repoze.tm2 or a middleware approach? What was the rationale for that design decision? 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] Zope 2 WSGI investigation
On Mon, 2012-01-02 at 10:39 +, Martin Aspeli wrote: > On 2 January 2012 08:50, Wichert Akkerman wrote: > > On 01/01/2012 08:39 PM, Martin Aspeli wrote: > >> > >> Hi, > >> > >> There are three known WSGI implementations of the Zope 2 publisher. > >> I've had a look at them and made some notes about what I think > >> provides the best story: > >> > >> ## Zope 2.13 WSGIPublisher > >> > >> Pros: > >> > >> * Allows distributed transaction management with repoze.tm2 > >> * Allows distributed retry with repoze.retry > >> * Ships with Zope > >> * Quite simple > >> > >> Cons: > >> > >> * Requires repoze.tm2 and repoze.rety > > > > > > Why is that a con? I use repoze.tm2 and repoze.retry with all my pyramid > > projects and they work beautifully. > > Only insofar as it means you have to have these in your WSGI pipeline > or it won't work, so there are more places things can go wrong. > > You'll note that I also consider not supporting such things a con for > infrae.wsgi. I wouldn't get too hung up on it, I was mainly just > trying to bring out the differences. It'd be nice if it wasn't a hard > requirement, though. FWIW, when I wrote repoze.tm2 I did not know that the transaction module already supported retry, so at least repoze.rety should die in favor of logic in something-like-repoze.tm2 that looks a little more like this: https://github.com/Pylons/pyramid_tm/blob/master/pyramid_tm/__init__.py#L49 (that's obviously not WSGI middleware, I'm just showing what the general logic should look like) - C > > 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 ) > ___ 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 )
[Zope-dev] zope-tests - FAILED: 2, OK: 56
This is the summary for test reports received on the zope-tests list between 2012-01-01 00:00:00 UTC and 2012-01-02 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.5.5 64bit linux Bluebream / Python2.6.7 64bit linux Bluebream / Python2.7.2 64bit linux ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.7 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.7 Linux 64bit ZTK 1.1 / Python2.5.5 Linux 64bit ZTK 1.1 / Python2.6.7 Linux 64bit ZTK 1.1 / Python2.7.2 Linux 64bit ZTK 1.1dev / Python2.5.5 Linux 64bit ZTK 1.1dev / Python2.6.7 Linux 64bit ZTK 1.1dev / Python2.7.2 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-ubuntu64 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 [1]Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 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_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / zc.resourcelibrary_py_265_32 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_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -- [1]FAILED Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2012-January/055225.html [2]FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-January/055201.html ___ 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] Zope internals documentation
On 2 January 2012 12:33, Jens Vagelpohl wrote: > Hi Martin, > >> Sphinx on svn.zope.org works for me. :) > > I have created a simple buildout and put it in SVN: > > http://svn.zope.org/zope_secrets/ > > The output is shown at http://docs.zope.org/zope_secrets/ and linked from the > front page at http://docs.zope.org/. Every 6 hours, a cron job looks to see > if the SVN revision has changed and if it has then the output is regenerated. Thanks! 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] Zope internals documentation
Hi Martin, > Sphinx on svn.zope.org works for me. :) I have created a simple buildout and put it in SVN: http://svn.zope.org/zope_secrets/ The output is shown at http://docs.zope.org/zope_secrets/ and linked from the front page at http://docs.zope.org/. Every 6 hours, a cron job looks to see if the SVN revision has changed and if it has then the output is regenerated. jens ___ 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] Zope 2 WSGI investigation
On 2 January 2012 08:50, Wichert Akkerman wrote: > On 01/01/2012 08:39 PM, Martin Aspeli wrote: >> >> Hi, >> >> There are three known WSGI implementations of the Zope 2 publisher. >> I've had a look at them and made some notes about what I think >> provides the best story: >> >> ## Zope 2.13 WSGIPublisher >> >> Pros: >> >> * Allows distributed transaction management with repoze.tm2 >> * Allows distributed retry with repoze.retry >> * Ships with Zope >> * Quite simple >> >> Cons: >> >> * Requires repoze.tm2 and repoze.rety > > > Why is that a con? I use repoze.tm2 and repoze.retry with all my pyramid > projects and they work beautifully. Only insofar as it means you have to have these in your WSGI pipeline or it won't work, so there are more places things can go wrong. You'll note that I also consider not supporting such things a con for infrae.wsgi. I wouldn't get too hung up on it, I was mainly just trying to bring out the differences. It'd be nice if it wasn't a hard requirement, though. 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] Zope 2 WSGI investigation
On 01/01/2012 08:39 PM, Martin Aspeli wrote: Hi, There are three known WSGI implementations of the Zope 2 publisher. I've had a look at them and made some notes about what I think provides the best story: ## Zope 2.13 WSGIPublisher Pros: * Allows distributed transaction management with repoze.tm2 * Allows distributed retry with repoze.retry * Ships with Zope * Quite simple Cons: * Requires repoze.tm2 and repoze.rety Why is that a con? I use repoze.tm2 and repoze.retry with all my pyramid projects and they work beautifully. Wichert. ___ 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 )
