Tres Seaver wrote:
I recently reworked Anthony Baxter's SQLSessions product for a
consulting customer
...snip...
What I would like to do is revisit the effort, using the new
PluginRegistry code released as part of the PluggableAuthService
release; I am, however, pretty well booked up for the
Dario Lopez-Ksten wrote:
Tres Seaver wrote:
I recently reworked Anthony Baxter's SQLSessions product for a
consulting customer
...snip...
What I would like to do is revisit the effort, using the new
PluginRegistry code released as part of the PluggableAuthService
release; I am, however,
Michael Dunstan wrote:
On 18/05/2004, at 10:03 PM, Andrea Patuzzo wrote:
Hi, dear developers:
We are now randomly getting this kind of error:
[...]
File
/usr/local/Zope270CVS/lib/python/Products/Transience/Transience.py,
line 341, in __setitem__
current_bucket = self._data[current_ts]
Tres Seaver wrote:
We should have a 'hasattr-geddon' and remove every trace of that
monstrosity from Zope and the CMF; likewise a 'bareexcept-geddon'
(there might be a few places which are smart enough to do 'except:', but
I doubt it).
Now its not a geddon by any means, but the code I
Gents,
In following to the discussions regarding the leakage zope.org and my site
suffer from, I've done some testing, and here's what I've found.
First of all, the leak does seem to occur when errors occur. Unlike what
Chris suggested, I still suffer from this leak even when I completely
I've looked at that issue many times during various bug days and it
sounded reasonable enough but it always seemed like slightly
higher-hanging fruit than other issues because it introduces new
features as well as fixes bugs.
Personally I prefer that someone who wants to introduce new features
[EMAIL PROTECTED] wrote:
Gents,
In following to the discussions regarding the leakage zope.org and my site
suffer from, I've done some testing, and here's what I've found.
First of all, the leak does seem to occur when errors occur. Unlike what
Chris suggested, I still suffer from this leak even
Jim Fulton wrote:
I've posted two proposals:
http://dev.zope.org/Zope3/TALESPathExpressionAdapters
Not much opinion. Though I fear that (adapter)object could lead to
this syntax in Python itself, which would be horrid ;) I agree that
adapter(object) is a bad direction. object*adapter looks
Casey Duncan wrote:
On Wed, 19 May 2004 16:00:43 -0400
Jim Fulton [EMAIL PROTECTED] wrote:
I've posted two proposals:
http://dev.zope.org/Zope3/TALESPathExpressionAdapters
I have to say I am not found of *,
I'm not attached to '*'. Feel free to suggest alternatives
(other than ':', '/', '|',
On Wed, 2004-05-19 at 16:29, Jamie Heilman wrote:
Chris McDonough wrote:
Personally I prefer that someone who wants to introduce new features
(even small ones, like API additions) into the core do it via their own
committer privileges and thus sign up to maintain it for the rest of
Yeah
Chris McDonough wrote:
I've looked at that issue many times during various bug days and it
sounded reasonable enough but it always seemed like slightly
higher-hanging fruit than other issues because it introduces new
features as well as fixes bugs.
Oh granted, it totally is. It just happens
Chris McDonough wrote:
I've looked at that issue many times during various bug days and it
sounded reasonable enough but it always seemed like slightly
higher-hanging fruit than other issues because it introduces new
features as well as fixes bugs.
Personally I prefer that someone who wants to
I've posted two proposals:
http://dev.zope.org/Zope3/TALESPathExpressionAdapters
Proposes a mechanism for easily using adapters in TALES expressions.
http://dev.zope.org/Zope3/ZPTVariableNamespaces
proposes a mechanism for qualifying names defined in TAL and used in
TALES expressions.
Comments
Jim Fulton wrote:
I've posted two proposals:
http://dev.zope.org/Zope3/TALESPathExpressionAdapters
Proposes a mechanism for easily using adapters in TALES expressions.
I'm not at all clear on how the proposed mechanism is superior to the
implementation of path segment prefixes that exists in
I'm trying to figure out how to mount my main storage read-only
with zope 2.7.0. I'm starting to suspect that it's impossible.
I tried a few things below
-
ATTEMPT #1.
I find this in the zope.conf examples:
# Directive: read-only-database
#
#
15 matches
Mail list logo
