Tres Seaver wrote:
Now, how in gdb do I find out what it was that was trying to be imported?
(should any sort of import cause a core dump?!)
http://wiki.python.org/moin/DebuggingWithGdb
Things you learn, thanks for that :-)
Okay, another interesting data point; this appears to be related to
Summary of messages to the zope-tests list.
Period Fri Aug 27 12:00:00 2010 UTC to Sat Aug 28 12:00:00 2010 UTC.
There were 43 messages: 6 from Zope Tests, 2 from buildbot at
enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at
winbot.zope.org, 8 from ccomb at free.fr, 10 from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Glick wrote:
Log message for revision 115948:
AccessControl has changes
Changed:
U Zope/trunk/buildout.cfg
-=-
Modified: Zope/trunk/buildout.cfg
===
---
Hi.
I've recently stumbled on some at least to me unexpected behavior with
zope.keyreference. For a persistent object it generates a unique key
using:
hash((database_name, oid))
where hash is Python's built-in hash function.
Reading the documentation I assumed that a keyreference for the same
On Sat, Aug 28, 2010 at 6:12 PM, Tres Seaver tsea...@palladion.com wrote:
Modified: Zope/trunk/buildout.cfg
===
--- Zope/trunk/buildout.cfg 2010-08-25 17:16:57 UTC (rev 115947)
+++ Zope/trunk/buildout.cfg 2010-08-25 17:18:10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
This approach was my idea. I wanted to give more people a chance to
review and comment on the new feature in AccessControl, before
actually releasing it. But we need to fix the buildbots to be able to
deal with this setup
On Sat, Aug 28, 2010 at 7:17 PM, Tres Seaver tsea...@palladion.com wrote:
The breakage might be in mr.developer, expecting a svn 1.6-only feature?
I think it only requires Subversion 1.5 and not 1.6, which shouldn't
be a problem. 1.4 is from the stone-age :)
Hanno
On Sat, Aug 28, 2010 at 12:17 PM, Hanno Schlichting ha...@hannosch.eu wrote:
Hi.
I've recently stumbled on some at least to me unexpected behavior with
zope.keyreference.
Specifically, zope.keyreference.persistent, I assume.
For a persistent object it generates a unique key
using:
Hi.
On Sat, Aug 28, 2010 at 8:47 PM, Jim Fulton j...@zope.com wrote:
On Sat, Aug 28, 2010 at 12:17 PM, Hanno Schlichting ha...@hannosch.eu wrote:
I've recently stumbled on some at least to me unexpected behavior with
zope.keyreference.
Specifically, zope.keyreference.persistent, I assume.
On Sat, Aug 28, 2010 at 3:12 PM, Hanno Schlichting ha...@hannosch.eu wrote:
Hi.
On Sat, Aug 28, 2010 at 8:47 PM, Jim Fulton j...@zope.com wrote:
On Sat, Aug 28, 2010 at 12:17 PM, Hanno Schlichting ha...@hannosch.eu
wrote:
I've recently stumbled on some at least to me unexpected behavior
10 matches
Mail list logo