Things changed around a bit since I did this patch. I'm trying to get
a new one working but am having some issues with the 2.7 trunk in svn.
I think in general the startup sequence could use some clean up. I'm
working on mapping how it all works maybe that would help make it less
opaque.
Things changed around a bit since I did this patch. I'm trying to get
a new one working but am having some issues with the 2.7 trunk in svn.
I think in general the startup sequence could use some clean up. I'm
working on mapping how it all works maybe that would help make it less
opaque.
Ok,
I think I have a fix for this but we have a little semantics issue. I
thought that once the Zope config was set it could not be changed. In
the new ZOPE_CONFIG patch the environ variable only gets used as a last
resort in Zope.app() if no other configuration has been set. To do
this I
--On Samstag, 15. Mai 2004 1:59 Uhr +0200 Stefan H. Holek
[EMAIL PROTECTED] wrote:
Zope tests fail for me, unfortunately Andreas cannot reproduce this.
The ZOPE_CONFIG patch was responsible for other failures. I reverted the
change
and check for a better solution by next week.
-aj
--
Andreas
I think Fred might have some ideas about how to do the ZOPE_CONFIG
feature better if you can coax them out of him. ;-)
On Sat, 2004-05-15 at 03:56, Andreas Jung wrote:
--On Samstag, 15. Mai 2004 1:59 Uhr +0200 Stefan H. Holek
[EMAIL PROTECTED] wrote:
Zope tests fail for me, unfortunately
During the product registration the ZReST product is imported. on the
module level
it contains
default_output_encoding = getConfiguration().rest_output_encoding or
default_enc
I would inspect that at this point the configuration from zope.conf has
been read and
rest_output_encoding should
Sounds like its using the default configuration (which means
Zope.configure never got called). I assume it works during normal
startup, just not during unit tests?
On Fri, 2004-05-14 at 13:09, Andreas Jung wrote:
During the product registration the ZReST product is imported. on the
module
I've got no suggestions. Is it broken in the 2.7 branch at the moment?
On Fri, 2004-05-14 at 17:24, Andreas Jung wrote:
No, this happened during the standard Zope startup.
Andreas
--On Freitag, 14. Mai 2004 13:25 Uhr -0400 Chris McDonough
[EMAIL PROTECTED] wrote:
Sounds like its
I am under the impression that the ZOPE_CONFIG patch broke 2.7 branch.
Please see http://zope.org/Collectors/Zope/1233
Configuration is used very early, that's why I suggested to put the
logic into getConfiguration.
Zope tests fail for me, unfortunately Andreas cannot reproduce this.
Stefan
On
--On Samstag, 15. Mai 2004 1:59 Uhr +0200 Stefan H. Holek
[EMAIL PROTECTED] wrote:
I am under the impression that the ZOPE_CONFIG patch broke 2.7 branch.
Please see http://zope.org/Collectors/Zope/1233
Both problems are not related. I made the ZRest.py patch before the
ZOPE_CONFIG patch and
10 matches
Mail list logo
