On Tue, 2012-01-03 at 07:32 +, Martin Aspeli wrote:
On 3 January 2012 06:39, Chris McDonough chr...@plope.com wrote:
On Mon, 2012-01-02 at 10:39 +, Martin Aspeli wrote:
On 2 January 2012 08:50, Wichert Akkerman wich...@wiggy.net wrote:
On 01/01/2012 08:39 PM, Martin Aspeli wrote:
Op 1 jan 2012, om 20:39 heeft Martin Aspeli het volgende geschreven:
Hi,
Hello,
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
[...]
##
On Jan 3, 2012, at 09:34 , Sylvain Viollon wrote:
We use Paster as well in the stack, and use it to configure the Python
logging process, you can configure
there a logging to syslog, and after having a central syslog server. I think
it is more professional like this,
than using a tool in
On 01/03/2012 10:04 AM, Jens Vagelpohl wrote:
On Jan 3, 2012, at 09:34 , Sylvain Viollon wrote:
We use Paster as well in the stack, and use it to configure the Python
logging process, you can configure
there a logging to syslog, and after having a central syslog server. I think it
is more
On 3 January 2012 08:01, Chris McDonough chr...@plope.com wrote:
Am I right in thinking Pyramid no longer uses repoze.tm2 or a
middleware approach? What was the rationale for that design decision?
You're right, Pyramid scaffolding no longer supplies repoze.tm2 or any
other WSGI middleware
This is the summary for test reports received on the
zope-tests list between 2012-01-02 00:00:00 UTC and 2012-01-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:
