Andreas Jung wrote:
My recommendation:
1 yr deprecation period as it is now
1 yr + X maintenance period for older branches.
+1
Note that this should also extend to the Zope 3 releases. Zope 3.2 is
part of Zope 2.9 and will hence be used for quite some time. Yet,
bugfixes aren't even
Dieter Maurer wrote:
* cutting down the amount of code duplication and duplicated frameworks.
We've had two ZPT implementations, now we have to maintain only one. We
had our own logging framework, now we can simply use Python's, etc.
The second logging framework (zLOG) was a tiny wrapper
Florent Guillaume wrote:
Florent Guillaume wrote:
So here's a proposal: how about having the following order:
- __bobo_traverse__
- unacquired attribute
- zope 3 views
- acquired attributes
Attached is the current diff I'm working with (for Zope 2.10).
Hey, cool. You know, the real
Chris Withers wrote:
Tres Seaver wrote:
Unit test coverate for custom products is actually quite good. The
problems are nearly always to do with third party products, many of
which have been in useful stable mode since long before either
deprectaions or ubiquitous unit testing were part of
On 18 Jun 2006, at 12:37, Philipp von Weitershausen wrote:
Florent Guillaume wrote:
Florent Guillaume wrote:
So here's a proposal: how about having the following order:
- __bobo_traverse__
- unacquired attribute
- zope 3 views
- acquired attributes
Attached is the current diff I'm working
On 6/18/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
The remaining important question is: if a *default* view is specified
using the zope 3 mechanism, should we always treat it as a zope 3 view,
and refuse to lookup an attribute with that name?
Yep. browser:defaultView should only
On 18 Jun 2006, at 20:15, Lennart Regebro wrote:
If you want to have non-views as browser default, we still need to use
__browser_default__, then.
The option is to allow attributes, and specify the browserdefault with
@@ to force it to be a view.
But that wouldn't be compatible with what
On 6/18/06, Florent Guillaume [EMAIL PROTECTED] wrote:
On 18 Jun 2006, at 20:15, Lennart Regebro wrote:
If you want to have non-views as browser default, we still need to use
__browser_default__, then.
The option is to allow attributes, and specify the browserdefault with
@@ to force it to
On 6/18/06, Paul Winkler [EMAIL PROTECTED] wrote:
+1, I'd like some way to easily know when a release is no longer
maintained. i.e., what's the X in the above formula.
Well, it's 2 versions, so far. I.e, current release and last release.
Unless we decide to change that now.
--
Lennart
On Sun, Jun 18, 2006 at 08:30:58PM +0200, Lennart Regebro wrote:
On 6/18/06, Paul Winkler [EMAIL PROTECTED] wrote:
+1, I'd like some way to easily know when a release is no longer
maintained. i.e., what's the X in the above formula.
Well, it's 2 versions, so far. I.e, current release and
Lennart Regebro wrote:
On 6/18/06, Paul Winkler [EMAIL PROTECTED] wrote:
+1, I'd like some way to easily know when a release is no longer
maintained. i.e., what's the X in the above formula.
Well, it's 2 versions, so far. I.e, current release and last release.
Unless we decide to change that
--On 18. Juni 2006 14:36:06 -0400 Christian Theune [EMAIL PROTECTED] wrote:
However, Zope 2.8 is still available for stable download ... so we
currently have 7 branches to watch out for.
Yes, but in most cases a fix only affects only Zope 2 or Zope 3. So
we are back to 3.
-aj
--
ZOPYX
Andreas Jung wrote:
--On 18. Juni 2006 14:36:06 -0400 Christian Theune [EMAIL PROTECTED] wrote:
However, Zope 2.8 is still available for stable download ... so we
currently have 7 branches to watch out for.
Yes, but in most cases a fix only affects only Zope 2 or Zope 3. So
we are back to
--On 18. Juni 2006 14:35:48 -0400 Paul Winkler [EMAIL PROTECTED] wrote:
On Sun, Jun 18, 2006 at 08:30:58PM +0200, Lennart Regebro wrote:
On 6/18/06, Paul Winkler [EMAIL PROTECTED] wrote:
+1, I'd like some way to easily know when a release is no longer
maintained. i.e., what's the X in the
--On 18. Juni 2006 14:46:27 -0400 Christian Theune [EMAIL PROTECTED] wrote:
Andreas Jung wrote:
--On 18. Juni 2006 14:36:06 -0400 Christian Theune [EMAIL PROTECTED] wrote:
However, Zope 2.8 is still available for stable download ... so we
currently have 7 branches to watch out for.
Yes,
Philipp von Weitershausen wrote at 2006-6-18 12:28 +0200:
...
Its configuration was documented in the Zope schema file.
Its single API method was self explaining...
Not everybody is as smart as you are, Dieter.
Thank you :-)
And certainly not everyone
would get the idea of reading code or
Lennart Regebro wrote:
On 6/18/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
The remaining important question is: if a *default* view is specified
using the zope 3 mechanism, should we always treat it as a zope 3 view,
and refuse to lookup an attribute with that name?
Yep.
Aloha,
I have a python script, getCatalogItems(), which returns a (possibly
empty) list resulting from a catalog query. The lone parameter is the
sort index; the rest of the query is taken from the request. Anyhow...
If nothing was found, I don't want to display an empty table of results.
Aloha,
I'm currently doing a custom small business site that might also want to
be in French further down the road.
I've never used the internationalization aspects of zope yet...so a few
basic questions:
Can additional language support be added in later, or is it necessary to
build it
John Schinnerer wrote:
Aloha,
I have a python script, getCatalogItems(), which returns a (possibly
empty) list resulting from a catalog query. The lone parameter is the
sort index; the rest of the query is taken from the request. Anyhow...
If nothing was found, I don't want to display an
Aloha,
Thanks, I understand...though it's a bit annoying that it looks and acts
just like a list but isn't...
Just using items does work. I figured it would work for True when not
empty...I wasn't so sure what it would return when empty, as sometimes
the test seems to be on 'exists' rather
Dieter,
I tried the whole gdb threads debugging thing, with the following (nil)
results. Any other ideas? A lot of the instructions online seem to be
Linux-centric, so I'm at a loss as how to proceed:
(gdb) info threads
* 7 LWP 100099 0x2820e544 in pthread_mutexattr_init () from
This time, when it locked, I thought to try a backtrace.
(gdb) info threads
* 7 LWP 100098 0x2820e544 in pthread_mutexattr_init () from
/usr/lib/libpthread.so.2
6 Thread 0x8111000 (sleeping) 0x2820df0f in pthread_mutexattr_init ()
from /usr/lib/libpthread.so.2
5 Thread 0xa1e1a00 (LWP
23 matches
Mail list logo
