Yesterday I was fixing a bug in zc.zservertracelog and noticed an
unrelated failing test:
GET /test-req4/?
is logged as a request for /test-req4/ without the ?. AFAICS this is
because of an 18-month change to zope.server.http.httprequestparser.
Does anybody care? (I don't). I thought I'd
On Mon, Jan 09, 2012 at 06:26:58PM -0500, Jim Fulton wrote:
I'm trying to untangle zope.app-based applications from zope.server
and am trying to figure out a sane way to get an access log.
zope.app.wsgi sets the wsgi.logging_info WSGI environment variable
with a user label to display in
On Mon, Jan 9, 2012 at 6:26 PM, Jim Fulton j...@zope.com wrote:
I'm trying to untangle zope.app-based applications from zope.server
and am trying to figure out a sane way to get an access log.
zope.app.wsgi sets the wsgi.logging_info WSGI environment variable
with a user label to display in
On Jan 10, 2012, at 10:17 AM, Jim Fulton wrote:
BTW, zope.app.wsgi isn't in the ZTK. :)
It's not in ztk-versions.cfg, but it is in zopeapp-versions.cfg.
That's still part of ZTK package.
___
Zope-Dev maillist - Zope-Dev@zope.org
Hi,
I created a patch for a package zope.intid that almost completely
solves the problem with the zope.keyreference.interfaces.NotYet
exception.
I implemented a deferred indexing of objects added to the container
which is not connected to the ZODB.
As soon as the container is added to the ZODB -
Committed and released as 3.14.0.
Jim
On Mon, Jan 9, 2012 at 6:26 PM, Jim Fulton j...@zope.com wrote:
I'm trying to untangle zope.app-based applications from zope.server
and am trying to figure out a sane way to get an access log.
zope.app.wsgi sets the wsgi.logging_info WSGI environment
This is the summary for test reports received on the
zope-tests list between 2012-01-09 00:00:00 UTC and 2012-01-10 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:
