ECTED])
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Hi!
I am currently developing a tool for reverse engineering
ZClasses into UML using ObjectDomain and JPython.
this tool connects directly to a Zope instance and queries
the ZClass entities, methods and inheritance relations by
calling a set of utility methods that I implemented as External
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
/exUserFold
er/exUserFolder.py?content-type=text%2Fplain&rev=1.91
Regards,
Sandor
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ian Beatty
> Sent: Wednesday, March 31, 2004 4:26 PM
> To: [EMAIL PROTECTED]
> Subject: [Zope-
gt; From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Erik A.Dahl
> Sent: Wednesday, April 07, 2004 5:40 PM
> To: [EMAIL PROTECTED]
> Subject: [Zope-dev] manage_permission from script
>
>
> I'm trying to use manage_permission from a script against the root
w', ['Owner'])
Sandor
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail
> In fact, Zope puts large files (the threshold is around 256K - 512K)
> into a temporary file before serving them, to free up application
> threads. It's a tremendous handicap.
I'm working on a product which serves files from the filesystem. The
data retrieval method
TECTED] On Behalf Of Andre Meyer
> Sent: Saturday, April 10, 2004 3:34 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [Zope-dev] Thread in ZODB
[...]
> I have a multi-threaded Python application that I want to
> link to Zope.
> Site Error
> An error was encountered w
ds,
Sandor
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
his trick only for exploring ZODB behavior. The application
doesn't do any nasty tricks.
Regards,
Sandor
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related li
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
> I'm surprised it works for you under OpenBSD. The HEAD is broken
"Works" meant it did not produce the same error on OpenBSD on the second
startup. I didn't go further.
> currently because database mounts don't work. See the thread
> started by
> http://
Something is not right with the Zope 2.x cvs head on cygwin. I used
yesterdays checkout of Zope and Python 2.3 maintenance branch. The same
combo works on OpenBSD.
Here's the story:
[EMAIL PROTECTED] /zope/cvszope/bin
$ /zope/python23/bin/python ./mkzopeinstance.py
Please choose a directo
I reported this a few month ago with a patch and was told that it'll be
applied 'soon':
http://collector.zope.org/Zope/1175
IMHO the xml-rpc error handling is a mess. You can't define your own
standard_error_message like method, sometimes it returns html code, sets
the status
> You appear to have an itch... and you know what open source
> says about itches ;-)
Then I will try to fix these issues, I just wasn't sure if anyone cares.
Regards,
Sandor
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.
> It is important that add-on products for Zope be released under the
> ZPL.
What is the reason for not using the verbatim 3-clause BSD license?
The 4th clause in ZPL 2.1 is redundant, IANAL, though.
The 5th is confusing. What's the situation with *BSD like ports where
the source code
On Wed, Jan 19, 2005 at 05:04:53PM +1100, Alan Milligan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Andreas Jung wrote:
>
> | There is zero need to relax this requirement. You only have to start
> | Zope as root
> I just explained you cannot start as roo
field4)
VALUES
(, , , )
(parameters should be integer values)
Can anybody tell me how I can call this method and pass parameters from my
DTML method?
With , Zope gives me following error message:
Zope has encountered an error while publishing this resource.
Error Type: Bad Request
Error Value: ['param1
t i want
to set the permissions only for a specific product, independend of the
instances location
thx in advance, bernd
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
Hi !
I have tried to find 'The Zope Developer's Guide' without lucky. Could you
give me a location to download it?
Thanks.
_
Accede al romance online. Busca y encuentra a tu media naranja entre los
perfiles que te
I have a zope-behind-an-apache configuration (OpenBSD 3.4, Zope2.7rc1,
python 2.3.3, apache 1.3x). Inside the zope root, there's a folder
called 'Instances', and inside this there's my custmo object (eLMS)
called 'a': /Instances/a. A beforetraverse hook is regist
ck on
Of course, the popped item is 'a', that's the one with the
beforetraversal hook, so if it's really put back on later, than the hook
will run again. I think this is the explanation, but the question
remains: how can I avoid the second call to the beforetraverse hook?
Regards
EMAIL PROTECTED]
> Subject: [Zope-dev] Product Access to Files
>
>
> Greetings.
>
> I'm developing a Python-based product that needs to serve up
> a variety of XML files out of the product's directory. That
> is, certain URLs handled by instances of a product-defined
Methods' permission set. When the 'Owner' role is managed, the
Permission
'Add Database Methods' is also added to the 'Manager' role. ('Owner' comes
after 'Manager' in the roles list).
Can someone explain why this is so? or what I am
AIL PROTECTED]>:
> bTurtle ZOpe wrote at 2004-11-30 16:37 +0100:
> > ...
> >Can someone explain why this is so? or what I am doing wrong.
>
> I did not understand what you are trying to achieve.
>
> Do you want to:
>
> * determine the protection of methods
Is there a zope product that will allow me to create an online test tool?
Thanks!
RT
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http
I have a Zope product that relies heavily on a ZCatalog to search for
objects within a folder matching certain criteria. The ZCatalog
frequently becomes corrupt, and on searching the catalog, the catalog
gives me key errors. I'm trying to figure out what causes the
corruption so I can
I'm getting a ZODB.POSException.ConflictError in the following code in a
Custom Zope Product, and I'm hoping someone can enlighten me on how to
fix it.
# nd is a folder with a sub-folder "Categories
# "NDCategory" is a custom Zope product I wrote that does not ha
. If you have
any insight nere, I'd appreciate it.
Best,
Brian
On Fri, 01 Sep 2006 09:40:24 +0100, "Chris Withers"
<[EMAIL PROTECTED]> said:
> [EMAIL PROTECTED] wrote:
> > I'm getting a ZODB.POSException.ConflictError in the following code in a
> > Custom Zop
e
object from multiple threads.
Is there a good article that you know of that I could find out more
about thread-safe programming in ZEO?
Best,
Brian
On Fri, 01 Sep 2006 09:27:41 +0200, "Andreas Jung" <[EMAIL PROTECTED]>
said:
>
>
> --On 1. September 2006 02:54:26 -04
Module Products.ZCatalog.Catalog, line 520, in getScoredResult
KeyError: -464571725
On Fri, 1 Sep 2006 19:11:12 +0200, "Dieter Maurer" <[EMAIL PROTECTED]>
said:
> [EMAIL PROTECTED] wrote at 2006-9-1 02:54 -0400:
> >I have a Zope product that relies heavily on a ZCatalog
ost last):
> >> ...
> >> - Physical Path: /nephron_links/news_dtml
> >> Module DocumentTemplate.DT_String, line 476, in __call__
> >> Module DocumentTemplate.DT_In, line 465, in renderwb
> >> Module DocumentTemplate.DT_In, line 747, in sort_sequence
&
ce, LLC
[EMAIL PROTECTED]
http://www.robocommerce.com
800-644-7626
_______
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-
In my custom Zope Product (in python), get_transaction().commit() halts
execution (without throwing an exception).
Is this the proper behavior?
If it is, then how do you commit what you've done so far without halting
execution?
And, if not, what would cause it to halt execution?
Thank y
DALE, INC. 2007
33 East Minor Street, Emmaus, PA 18098, Attn: Customer Service
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
ng this failure? What I can do to go further?
It is possible you are having an issue with the way the splitter
is used on the search term input side. Several of us have found
bugs in that area. We've fixed the ones we've found, but there
may be more .
Run zope in debug mode ("the
d', 'or', ('test', '...'
'of')), 'or', 'searching')
I'm least sure of those parens around test...of.
Maybe this will at least give you a clue to enable you to figure
out what the code *really* does .
--RDM
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
I recently released 'zopectl', a python script that acts as a configurable
front end to the z2.py script, implementing the defacto standard unix process
control commands: zopectl start, zopectl stop, zopectl restart. I wrote
it to simplify management of a server that runs several zope
rs most likely to be confused are the
ones least likely to be using scripts at the os level.
--RDM
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http:
innable' project?
All that said, I applaud the "management quick fixes". Thanks, guys.
--RDM
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
other object data is pulled from an SQL
database. I don't mind storing the Images in the ZODB, but I'm having
a hard time finguring out how I would implement that. Pointers or
alternate design suggestions welcome.
--RDM
___
Zope-Dev maillist
hat correspondence ever
breaks, it'll be a sign that its time to promote the images to
their own specialist...
I think I'm slowly getting the hang of this. Now, if I can just manage
to finish reading Coad...
--RDM
___
Zope-Dev maillis
would be the right
decision. It gives you and others using your code the
maximum flexability.
Unfortunately I don't have much input on your question about
real-life scalability...the most I've done is stored 6 small objects
in a hierarchy of zope folders, indexed b
BTree module that comes with zope, each in their own way.
(Note that that module has some issues with DB activity on writes,
which I believe someone is eventually going to fix...)
> Hmm. John Eikenberry mentioned a slowdown with about 50,000
> objects on partial-match searches, bu
tree
EMarket installed in the instance products folder.
RedHat Linux 5.2 (I think, how do you tell on a linux system?)
python from RPMs, zope 2.3.0 from source install (wo_pcgi).
I upgraded an existing site by simply changing my zopectl (see my product)
PYTHONHOME setting to the 2.3.0 tree, shu
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
produces a blank, no matter
what the value of somevar. I could swear this works in other versions
of zope, but it seems like an awfully fundamental bug to have slipped
through the 2.3.0 release process. Can anyone tell me what stupid
thing I'm doing wrong?
On Wed, 14 Feb 2001, Sin Hang Kin wrote:
> When starting Zope2.3 from the freebsd box, the kernel says : file: table is
> full.
>
> The kern.maxfiles is set to 1064, does zope really need that many? what
> number should I need to make zope happy?
I noticed this problem with Zop
Summary of messages to the zope-tests list.
Period Mon Oct 13 11:00:00 2008 UTC to Tue Oct 14 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Unknown
---
Subject: UNKNOWN : Zope-2.11 Python-2.4.4 : Linux
From: Zope Tests
Date: Mon Oct 13 20:56:33 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Tue Oct 14 11:00:00 2008 UTC to Wed Oct 15 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Tue Oct 14 20:54:23 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Wed Oct 15 11:00:00 2008 UTC to Thu Oct 16 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Wed Oct 15 20:54:55 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Thu Oct 16 11:00:00 2008 UTC to Fri Oct 17 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Thu Oct 16 20:50:58 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Fri Oct 17 11:00:00 2008 UTC to Sat Oct 18 11:00:00 2008 UTC.
There were 4 messages: 4 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Fri Oct 17 20:47:41 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Sat Oct 18 11:00:00 2008 UTC to Sun Oct 19 11:00:00 2008 UTC.
There were 4 messages: 4 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Sat Oct 18 20:48:16 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Sun Oct 19 11:00:00 2008 UTC to Mon Oct 20 11:00:00 2008 UTC.
There were 4 messages: 4 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Sun Oct 19 20:46:48 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Mon Oct 20 11:00:00 2008 UTC to Tue Oct 21 11:00:00 2008 UTC.
There were 4 messages: 4 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Mon Oct 20 20:46:45 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Tue Oct 21 11:00:00 2008 UTC to Wed Oct 22 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Tue Oct 21 20:56:11 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Wed Oct 22 11:00:00 2008 UTC to Thu Oct 23 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Wed Oct 22 20:57:29 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Thu Oct 23 11:00:00 2008 UTC to Fri Oct 24 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Thu Oct 23 20:55:28 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Fri Oct 24 11:00:00 2008 UTC to Sat Oct 25 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Fri Oct 24 20:56:52 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Sat Oct 25 12:00:00 2008 UTC to Sun Oct 26 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Sat Oct 25 20:59:16 EDT 2008
Summary of messages to the zope-tests list.
Period Sun Oct 26 12:00:00 2008 UTC to Mon Oct 27 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3, errors=4) : Zope-trunk Python-2.4.4 : Linux
From: Zope Tests
Date: Sun Oct 26 22:03
Summary of messages to the zope-tests list.
Period Mon Oct 27 12:00:00 2008 UTC to Tue Oct 28 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.4 : Linux
From: Zope Tests
Date: Mon Oct 27 22:12:19 EDT
Summary of messages to the zope-tests list.
Period Tue Oct 28 12:00:00 2008 UTC to Wed Oct 29 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Unknown
---
Subject: UNKNOWN : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Wed Oct 29 04:24:18 EDT 2008
URL: http
Summary of messages to the zope-tests list.
Period Wed Oct 29 12:00:00 2008 UTC to Thu Oct 30 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux
From: Zope Tests
Date: Thu Oct 30 03:18:23 EDT
Summary of messages to the zope-tests list.
Period Thu Oct 30 12:00:00 2008 UTC to Fri Oct 31 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Thu Oct 30 22:12:28 EDT
Summary of messages to the zope-tests list.
Period Fri Oct 31 12:00:00 2008 UTC to Sat Nov 1 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Fri Oct 31 22:06:48 EDT
Summary of messages to the zope-tests list.
Period Sat Nov 1 12:00:00 2008 UTC to Sun Nov 2 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sat Nov 1 22:07:21 EDT
Summary of messages to the zope-tests list.
Period Sun Nov 2 12:00:00 2008 UTC to Mon Nov 3 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sun Nov 2 21:13:34 EST
Summary of messages to the zope-tests list.
Period Mon Nov 3 12:00:00 2008 UTC to Tue Nov 4 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Mon Nov 3 21:10:28 EST
Summary of messages to the zope-tests list.
Period Tue Nov 4 12:00:00 2008 UTC to Wed Nov 5 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Tue Nov 4 21:08:38 EST
Summary of messages to the zope-tests list.
Period Wed Nov 5 12:00:00 2008 UTC to Thu Nov 6 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Wed Nov 5 20:39:55 EST
Summary of messages to the zope-tests list.
Period Thu Nov 6 12:00:00 2008 UTC to Fri Nov 7 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Thu Nov 6 20:41:36 EST
Summary of messages to the zope-tests list.
Period Fri Nov 7 12:00:00 2008 UTC to Sat Nov 8 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Fri Nov 7 20:40:54 EST
Summary of messages to the zope-tests list.
Period Sat Nov 8 12:00:00 2008 UTC to Sun Nov 9 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sat Nov 8 20:36:49 EST
Summary of messages to the zope-tests list.
Period Sun Nov 9 12:00:00 2008 UTC to Mon Nov 10 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Unknown
---
Subject: UNKNOWN : Zope-2.8 Python-2.3.7 : Linux
From: Zope Tests
Date: Sun Nov 9 19:32:25 EST 2008
URL: http
Summary of messages to the zope-tests list.
Period Mon Nov 10 12:00:00 2008 UTC to Tue Nov 11 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Unknown
---
Subject: UNKNOWN : Zope-2.9 Python-2.4.5 : Linux
From: Zope Tests
Date: Mon Nov 10 19:50:47 EST 2008
URL: http
Summary of messages to the zope-tests list.
Period Tue Nov 11 12:00:00 2008 UTC to Wed Nov 12 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Tue Nov 11 20:34:55 EST
Summary of messages to the zope-tests list.
Period Wed Nov 12 12:00:00 2008 UTC to Thu Nov 13 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Wed Nov 12 20:39:40 EST
Summary of messages to the zope-tests list.
Period Thu Nov 13 12:00:00 2008 UTC to Fri Nov 14 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Thu Nov 13 20:38:27 EST
Summary of messages to the zope-tests list.
Period Fri Nov 14 12:00:00 2008 UTC to Sat Nov 15 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Fri Nov 14 20:37:42 EST
Summary of messages to the zope-tests list.
Period Sat Nov 15 12:00:00 2008 UTC to Sun Nov 16 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sat Nov 15 20:36:57 EST
Summary of messages to the zope-tests list.
Period Sun Nov 16 12:00:00 2008 UTC to Mon Nov 17 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sun Nov 16 20:38:04 EST
Summary of messages to the zope-tests list.
Period Mon Nov 17 12:00:00 2008 UTC to Tue Nov 18 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Mon Nov 17 20:38:19 EST
Summary of messages to the zope-tests list.
Period Tue Nov 18 12:00:00 2008 UTC to Wed Nov 19 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Tue Nov 18 20:36:54 EST
Summary of messages to the zope-tests list.
Period Wed Nov 19 12:00:00 2008 UTC to Thu Nov 20 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Wed Nov 19 20:38:44 EST
Summary of messages to the zope-tests list.
Period Thu Nov 20 12:00:00 2008 UTC to Fri Nov 21 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Thu Nov 20 20:37:17 EST
Summary of messages to the zope-tests list.
Period Fri Nov 21 12:00:00 2008 UTC to Sat Nov 22 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Fri Nov 21 20:39:49 EST
Summary of messages to the zope-tests list.
Period Sat Nov 22 12:00:00 2008 UTC to Sun Nov 23 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sat Nov 22 20:39:31 EST
Summary of messages to the zope-tests list.
Period Sun Nov 23 12:00:00 2008 UTC to Mon Nov 24 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sun Nov 23 20:37:20 EST
Summary of messages to the zope-tests list.
Period Mon Nov 24 12:00:00 2008 UTC to Tue Nov 25 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Mon Nov 24 20:37:41 EST
Summary of messages to the zope-tests list.
Period Tue Nov 25 12:00:00 2008 UTC to Wed Nov 26 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Tue Nov 25 20:36:44 EST
Summary of messages to the zope-tests list.
Period Wed Nov 26 12:00:00 2008 UTC to Thu Nov 27 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Wed Nov 26 20:39:12 EST
Summary of messages to the zope-tests list.
Period Thu Nov 27 12:00:00 2008 UTC to Fri Nov 28 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Thu Nov 27 20:39:40 EST
Summary of messages to the zope-tests list.
Period Fri Nov 28 12:00:00 2008 UTC to Sat Nov 29 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Fri Nov 28 20:38:21 EST
Summary of messages to the zope-tests list.
Period Sat Nov 29 12:00:00 2008 UTC to Sun Nov 30 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sat Nov 29 20:38:43 EST
Summary of messages to the zope-tests list.
Period Sun Nov 30 12:00:00 2008 UTC to Mon Dec 1 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Sun Nov 30 20:40:28 EST
Summary of messages to the zope-tests list.
Period Wed Dec 3 12:00:00 2008 UTC to Thu Dec 4 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Wed Dec 3 20:26:53 EST
Summary of messages to the zope-tests list.
Period Thu Dec 4 12:00:00 2008 UTC to Fri Dec 5 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Test failures
-
Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux
From: Zope Tests
Date: Thu Dec 4 20:28:38 EST
Summary of messages to the zope-tests list.
Period Fri Dec 5 12:00:00 2008 UTC to Sat Dec 6 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Tests.
Test failures
-
Subject: FAILED (failures=7) : Zope-2.11 Python-2.4.5 : Linux
From: Zope Tests
Date: Fri Dec 5 20:36:57 EST
1 - 100 of 2595 matches
Mail list logo
