Re: [ZODB-Dev] strange testConnection error

Tim Peters wrote: [John Belmonte] Here is the mod_python thread I started on the issue: http://www.modpython.org/pipermail/mod_python/2005-March/017663.html I haven't made any headway on this-- seems like I have a lot more digging to do. It is complex. Note that creating a new interp

Re: [ZODB-Dev] strange testConnection error

I wrote: The consensus on the mod_python mailing list is that this is a bug in Python 2.4 (which was backported to 2.3.5). See . The other possibility is that both JEP and mod_python are doing somethin

[ZODB-Dev] issue with new package layout

I'm trying to update my experimental ZODB Debian package to 3.4.0a1. The new change of having version numbers hard-coded in file paths within the source package (e.g. Dependencies/BTrees-ZODB3-3.4.0a1) is very troubling. This means that any patch to the upstream source I try to maintain will s

Re: [ZODB-Dev] issue with new package layout

Jim Fulton wrote: Tim Peters wrote: [John Belmonte] I'm trying to update my experimental ZODB Debian package to 3.4.0a1. The new change of having version numbers hard-coded in file paths within the source package (e.g. Dependencies/BTrees-ZODB3-3.4.0a1) is very troubling. Not really new:

[ZODB-Dev] setup.py --clean issue

In 3.4a1 I noticed that setup.py --clean is leaving some derived files behind: $ python setup.py clean --all running clean 'build/lib.linux-i686-2.4' does not exist -- can't clean it 'build/bdist.linux-i686' does not exist -- can't clean it 'build/scripts-2.4' does not exist -- can't clean it $ fi

[ZODB-Dev] python restricted mode subthreads bug

I'm wondering if someone on the list able to pull some python-dev strings would be kind enough to raise the priority of Python bug 1163563. This is the one causing ZEO not to work with mod_python in Python 2.3.5 and later. http://sourceforge.net/tracker/?func=detail&aid=1163563&group_id=5470&atid

[ZODB-Dev] zdctl.py --umask bug

One year later, this is still a bug. As I'm the one that added the umask option in the first place, can I ask that you trust me and apply the one line fix? http://www.zope.org/Collectors/Zope/1323 --John ___ For more information about ZODB, see the Z

[ZODB-Dev] world gone wrong after write conflict

Hello, I'm attempting to dust off my old high-write ZODB/ZEO app, and am having a hard time tracking down a problem. Something goes very wrong in the case where I catch a write conflict, abort the transaction, and attempt a retry. Frequently it appears as if the abort did not restore the objects

[ZODB-Dev] "unghostified object not in cache"

Just reporting that I got this spurious error with Python 2.4, mod_python 3.2.10, and ZODB 3.6. I don't see what I could be doing wrong at the app level to cause it. SystemError: object at 0x2aaab031dc00 with type BTrees._OOBTree.OOBucket not in the cache despite that we just unghostified i