Hi,
I knew that sometimes ZServer stopps working with
the error OS-error Broken-Pipe in the log-file. And I knew that this is fixed in
Zope 2.5b with a change of asyncore.py
I need a working asyncore.py for my 2.4.3 Zope. Can
anybody sent me a working version ?
Regards,
Dirk Datzert
Hi,
Trying to test a URL in a unittest.py test using code as follows:
apply(Site.restrictedTraverse('/folder/cmfsite/skinmethod'),params)
Now, skinmethod uses the new Zope 2.5.0 sessioning:
session=context.REQUEST.SESSION
session.set('key','value')
but the BeforeTraversal hook doesn't
We at Torped are interested, and we *can't* host it, which seems to make us
unique in this. :-)
- Original Message -
From: Paul Everitt [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 07, 2002 1:45 PM
Subject: [ez] DISCUSS: Eurosprint in February
Howdy. Eurozope has
I thought it was time to catch up on the CST stuff which has made it
into the core, only to find that it's only *based on* Chris' CST stuff.
And I can't find a fishbowl project anywhere describing the rationale,
apis, whatever...
Is there a fishbowl for this? Or was session tracking
Your problem is that a REQUEST is not created without the
publisher. This is a particularly annoying and unsolved
problem when doing tests. Your options are to use import
Zope; Zope.test('/some/method/name') which has all sorts of
bad side effects, or to dummy up the environment as much as
CST was done via the fishbowl project at
http://dev.zope.org/Wikis/DevSite/Projects/CoreSessionTracking/FrontPage.
There is an explanation of the difference between the Zope
2.5 stuff and CST on the CurrentStatus page. Note that this
situation makes me want to cry as well.
There are supposed to
Broken pipe errors usually dont cause the system to stop
working. Are you sure that this is the cause of the system
crashing? It's almost certainly not, even though you may
see errors on the console and in the log.
On Tue, 8 Jan 2002 10:20:24 +0100
Dirk Datzert [EMAIL PROTECTED] wrote:
Chris McDonough wrote:
Your problem is that a REQUEST is not created without the
publisher. This is a particularly annoying and unsolved
problem when doing tests.
Is it solved in Zope 3?
Your options are to use import
Zope; Zope.test('/some/method/name') which has all sorts of
bad
Is it solved in Zope 3?
Zope3 is more modular, so probably. Though I dont think
it's a goal.
Never even knew that existed. Where's it documented? What
does it do? What are
the side effects?
Zoper.test as a side effect it commits a transaction.
It's documented in the dev guide as
I am interested to join that sprint.
Robert
- Original Message -
From: Lennart Regebro [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 08, 2002 12:20 PM
Subject: [Zope-dev] Re: [ez] DISCUSS: Eurosprint in February
We at Torped are interested, and we *can't* host it,
Casey Duncan wrote:
I am posting this here to get reactions here for something that we have been
discussing on zope-dev that pertains to the ZODB.
Dieter M. discovered that bobobase_modification_time (henceforth referred to
as b_m_t) is not always an accurate representation of an object's
On Tue, 2002-01-08 at 13:03, Chris McDonough wrote:
There are supposed to be docs for the sessioning stuff, and
there *are* API docs in the help system. However, the
narrative docs that went along with CST were not translated
for the Zope 2.5 stuff. The docs folks here dont seem to
think
I think that a much better approach, if modification time is important
to your application, is to store the application modification time in the
object as a data attribute.
It might be better to cause common Zope objects to do what Casey proposes
(maybe via SimpleItem) as opposed to making
It's important because session tracking is such a crucial feature for
people migrating from other web platforms - seeing detailed
documentation will make them so much more comfortable. it would also be
a crying shame not to make use of all the docs you already generated
along the way.
I
On Tuesday 08 January 2002 09:15 am, Jim Fulton allegedly wrote:
The basic problem is that b_m_t is a database modification time, not
an application-meaningful time. You pointed out that there are
application-meaningful times that are not captured by the database time.
In addition, there are
On Tuesday 08 January 2002 09:47 am, Chris McDonough allegedly wrote:
I think that a much better approach, if modification time is important
to your application, is to store the application modification time in the
object as a data attribute.
It might be better to cause common Zope
Lennart Regebro wrote:
Is there interest in such a sprint?
Yup, obviously the nearer to the UK the better :-)
cheers,
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
My ProductRegistry has references to products
which no longer exist in my Zope installation.
This causes a variety of problems in lots of
different places when other products try to get
more information about all the products in the
ProductRegistry (obviously).
1) How does this occur?
2) Is it
On Tuesday 08 January 2002 06:47 am, Chris McDonough wrote:
I think that a much better approach, if modification time is important
to your application, is to store the application modification time in the
object as a data attribute.
It might be better to cause common Zope objects to do
Oops. Wrong list, the discussion should be on the eurozope list...
My mistake.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
Clicking on Cache detail in the Debug Information
Control Panel, I get the following traceback:
Zope Error!
Zope has encountered an error while publishing this resource.
Error Type: AttributeError
Error Value: __module__
Traceback (innermost last):
File
John Ziniti wrote:
I used to have the Product TrackerBase installed
and have removed it. Now, however, attempts to
access the Advanced tab of ZSQL Methods is
broken because a chain of events attempt to get
info about a the non-existent Product:
I'm ready and eager to blame Z classes for everything :)
Yeah, me too, hatin' em right about now ...
% cd lib/python
% python2.1.1
import Zope
app = Zope.app()
app.fixupZClassDependencies(rebuild=1)
get_transaction().commit()
Hopefully that will do it for you.
Found that on
Chris McDonough writes:
The docs folks here dont seem to
think its important, so I may need to do this and put it in
the Dev Guide.
As always, the developers are industrious and the documentors
are lazy. As a result, source is usually far beyond the documentation ;-)
Dieter
John Ziniti writes:
I used to have the Product TrackerBase installed
and have removed it. Now, however, attempts to
access the Advanced tab of ZSQL Methods is
broken because a chain of events attempt to get
info about a the non-existent Product:
...
2) Is this schizophrenic state
On Tue, 2002-01-08 at 14:01, Evan Simpson wrote:
Michael R. Bernstein wrote:
[snip stuff about accessing a browser_id_manager's
meta_type from unrestricted code raising an
unauthorized exception]
Will this be fixed for 2.5 final?
That depends. We're currently waiting for
meta_type is an attribute, so you can't just do
security.declareProtected(ACCESS_CONTENTS_PERM, 'meta_type')
That's right.
The id attribute has the getId method, perhaps what's required is a
getMetaType method that can be suitably protected?
This would still be a pretty easy fix:
Dieter Maurer wrote:
John Ziniti writes:
I used to have the Product TrackerBase installed
and have removed it. Now, however, attempts to
access the Advanced tab of ZSQL Methods is
broken because a chain of events attempt to get
info about a the non-existent Product:
...
2) Is this
28 matches
Mail list logo
