Martijn Faassen wrote:
>>> Yes, but Zope 2 included *less* than Zope 3 in the most recent
>>> release, and I'd like *all* packages that are in a Zope 3 release to
>>> be available in a Zope 2 release. I.e. Five doesn't want packages
>>> that aren't in a Zope 3 release, but not less either.
>>
>> I'
Martijn Faassen wrote at 2006-1-19 19:37 +0100:
> ...
>I'm talking about a Zope 2 release including (most of) what's in a Zope
>3 release, so that Five developers can work on exposing *that* in Zope 2
>too (which can then be part of the next Zope 2 release as we integrate
>the newer Five in it).
Summary of messages to the zope-tests list.
Period Thu Jan 19 12:01:01 2006 UTC to Fri Jan 20 12:01:01 2006 UTC.
There were 8 messages: 8 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Thu Jan 19 21:03:09 EST 2
Chris Withers wrote:
...
On a side note, I see python now includes doctest.py, why are we still
maintaining our own copy in zope.testing?
doctest has been in Python for a long time, far longer than we've been using it.
Now that we use it aggressively and are aggressively contributing to it, we
--On 20. Januar 2006 10:03:03 + Chris Withers <[EMAIL PROTECTED]>
wrote:
set' set.
A cool :-) Where's the code that checks if this header is present so I
can take a look?
ZPublisher/HTTPResponse.py (where else :-))
Oh :-S
I was expecting a different patch... so this only affects c
Andreas Jung wrote:
--On 19. Januar 2006 18:37:35 + Chris Withers
<[EMAIL PROTECTED]> wrote:
Andreas Jung wrote:
Ah, okay, and how would I indicate in my PythonScript return that I'm
returning something different to what is specified in
zpublisher_default_encoding?
By setting the con