Tim Peters wrote:
I'm the closest thing to a ZODB maintainer there is, and I won't object
;-) Go for it!
OK. Right now I have the problem of getting the tests to pass before I
start changing things. Doing just as README.txt says (python2.4 setup.py
build, then python2.4 test.py) earns me
[Margie Watkins CONT]
The issue http://www.zope.org/Collectors/Zope/1695 asks for a statement
from users who are affected by the missing modules.
Unfortunately, that's become out of sight, out of mind since then -- the
issue was opened 9 months ago, and to date you're the first to say you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Peters wrote:
So I tried that just now using ZODB trunk. It failed too, but with
different symptoms than you're describing:
$ python2.4 setup.py build
...
$ python2.4 test.py -v
Running tests from build/lib.linux-i686-2.4
Traceback (most
Tim Peters wrote:
Things I can't guess include which version of ZODB you're trying this
with, and exactly what the errors were. Copy+paste generally works a lot
better than English paraphrasing.
Sorry.
From the build/lib.foo part I guess you're running on Linux.
Right.
So I tried that
[Tim]
...
This worked (which is what I normally do): [build_ext -i]
[Thomas]
It did for me too. I guess the crucial difference was doing build_ext
instead of just build.
Yes.
Maybe someone with more distutils clue could say something about it; if
my guess is right, README.txt should be
[Tim]
...
BTW,
setup.py build
python test.py
should work too; it's a bug that it doesn't (and it worked fine within
the last few months), but I don't have time for it now.
Well, bug or not, the resident zpkgtools expert tells me he doesn't expect
that to work anymore, and that it
[Julien]
Well I'm not sure it works Tim. My comment was to be able to test the
build *before* installing the ZODB on the Python.
Right, and that's the way ZODB tests are normally run by everyone who works
on ZODB (they never _install_ ZODB to run tests).
I need to try that again but, if I
Paolo Linux wrote at 2005-11-17 10:23 +0100:
...
I suspect that in some cases we do not manage Conflict
Error (we retry for 3 times but then we give up...).
Could this be connected with POSKeyErrors?
It should not. Because giving up should mean you abort the
transaction and your transaction
Tim Peters wrote at 2005-11-18 10:02 -0500:
[Margie Watkins CONT]
The issue http://www.zope.org/Collectors/Zope/1695 asks for a statement
from users who are affected by the missing modules.
Unfortunately, that's become out of sight, out of mind since then -- the
issue was opened 9 months ago,
