zope.testrowser 3.4.1 generates non-backward-compatible tracebacks for
HTTP errors. 3.4.2 will be released soon(-ish) to fix this, in the mean
time please continue to use 3.4.0. Thanks.
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope
Hey,
Thanks for the write-up. This needs some thinking. I will bring this up
on the board, too.
As a general point: the foundation board is happy to appoint someone as
its official representative in this and back them up where needed, but I
think it's unlikely at this point we'll be having a
Benji York wrote:
zope.testrowser 3.4.1 generates non-backward-compatible tracebacks for
HTTP errors. 3.4.2 will be released soon(-ish) to fix this, in the mean
time please continue to use 3.4.0. Thanks.
I guess I'm to blame here since I released 3.4.1. In my defence, it
seems that the new
Hello Philipp,
Thursday, September 13, 2007, 1:34:02 PM, you wrote:
> Benji York wrote:
>> zope.testrowser 3.4.1 generates non-backward-compatible tracebacks for
>> HTTP errors. 3.4.2 will be released soon(-ish) to fix this, in the mean
>> time please continue to use 3.4.0. Thanks.
> I guess
Philipp von Weitershausen wrote:
Benji York wrote:
zope.testrowser 3.4.1 generates non-backward-compatible tracebacks for
HTTP errors. 3.4.2 will be released soon(-ish) to fix this, in the mean
time please continue to use 3.4.0. Thanks.
I guess I'm to blame here since I released 3.4.1.
No
Hi Martijn. Yes, it needs thinking and action since it will take months
to communicate, assess, and to pull this together in a cohesive way. I
see the need for a key board member to be accountable to the Foundation
for this effort. It is really a matter of oversight and to ensure this
gets done
Christian Theune wrote:
Let me propose a change:
1. We revert the change.
Any news on this?
--
http://worldcookery.com -- Professional Zope documentation and training
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman
On 13.09.2007, at 17:28, Philipp von Weitershausen wrote:
Christian Theune wrote:
Let me propose a change:
1. We revert the change.
Any news on this?
Yes. Over the last few days I pondered about how to do it without
xmlrpc layers. But there doesn't seem to be a way nice and easy way.
Hi
> Betreff: [Zope3-dev] Re: skin support for xmlrpc
>
>
> On 13.09.2007, at 17:28, Philipp von Weitershausen wrote:
>
> > Christian Theune wrote:
> >> Let me propose a change:
> >> 1. We revert the change.
> >
> > Any news on this?
>
> Yes. Over the last few days I pondered about how to do
Am Sonntag, den 08.07.2007, 11:31 -0400 schrieb Stephan Richter:
> On Sunday 08 July 2007 10:02, Christian Theune wrote:
> > Log message for revision 77624:
> > More work on bug 98287: Introduced an event to signal that an object
> > value is going to be assigned.
>
> Ahh, this is crazy! Why wou
On Sep 11, 2007, at 10:28 AM, David Pratt wrote:
I was hoping Jim might respond to this thread since I am certain
there is concern about what this means for the future of Zope. I am
hoping that core communities of python framework developers may
come together on what is in their best inter
On 13.09.2007, at 18:07, Roger Ineichen wrote:
Hi
Betreff: [Zope3-dev] Re: skin support for xmlrpc
On 13.09.2007, at 17:28, Philipp von Weitershausen wrote:
Christian Theune wrote:
Let me propose a change:
1. We revert the change.
Any news on this?
Yes. Over the last few days I ponde
On 9/14/07, Christian Zagrodnick <[EMAIL PROTECTED]> wrote:
> Before I'll revert the layer-support will be there in a third party
> package, probably using ++api++.
Better to be specific than general when it's for a specific type of
request; why not ++xmlrpc++?
Unless ++api++ is for more than XML
13 matches
Mail list logo
