--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
On 14/05/2004, at 10:06 AM, Chris McDonough wrote:
I am tempted to check the following into the 2.7 branch and HEAD:
- "error occurs in same transaction as main request" patch
to Publish.py. See
http://www.plope.com/Members/chrism/
publishpy_errorinmaintrainsaction.patch/file_view
for the patc
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 Sa
I've fixed this bug (and several others) and checked the result into the
Zope 2.7 branch. You can get it at
http://cvs.zope.org/*checkout*/Zope/lib/python/Products/Transience/Transience.py?rev=1.32.12.3
HTH,
- C
On Fri, 2004-05-14 at 15:42, Chris McDonough wrote:
> I figured out what this is;
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 li
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 using the "default" configuration (which means
Zope.configure never got called). I assume it works during normal
startup, just not dur
I figured out what this is; it's a genuine bug, sorry. Until I get it
fixed, please comment out these lines of Transience.py to make things
OK:
if self._limit and len(self) >= self._limit:
LOG('Transience', WARNING,
('Transient object container %s
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
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 be
