An error occurred fetching the project authors.
- 21 Aug, 2004 2 commits
-
-
Tim Peters authored
-
Tim Peters authored
automated test. There were so many oddities getting that test to pass, and so much consequent fiddling of other code, that I don't intend to merge this to the 3.3 branch. Also moved to current Python CVS doctest.py, because the test really needs the +ELLIPSIS option (tids vary across runs).
-
- 19 Aug, 2004 1 commit
-
-
Tim Peters authored
and extension fields from a transaction was fatally confused, usually reading them out of the object pickle by mistake. This caused several tools to display binary gibberish.
-
- 18 Aug, 2004 1 commit
-
-
Tim Peters authored
Forward port from Zope 2.7 branch. analyze_rec(): This produced spurious "len of unsized object" messages when a data record had a backpointer instead of a pickle. Repaired. analyze(), analyze_trans(): Simplified overly elaborate iteration code.
-
- 17 Aug, 2004 2 commits
-
-
Tim Peters authored
Forward port from Zope 2.7 branch. Many changes to fsrefs.py, based on problems I hit using it in real life.
-
Tim Peters authored
Forward port from Zope 2.7 branch. oid_repr(): Make it obvious which base is intended. The output was 3-way ambiguous.
-
- 13 Aug, 2004 1 commit
-
-
Tim Peters authored
Just changing what we're calling the next release.
-
- 12 Aug, 2004 2 commits
-
-
Tim Peters authored
Please don't do that: ZODB changes need to be done in the ZODB project. Checkins to Zope3 have no effect on ZODB in reality. This includes: r26945 | jim | 2004-08-06 18:30:44 -0400 (Fri, 06 Aug 2004) | 6 lines M /Zope3/trunk/src/persistent/tests/test_persistent.py Updated to work with the versions of doctest from Python with versions greater than or equal to 2.3.0 and less than 2.4.0.a2 and with versions greater than 2.4.0a2. r26482 | srichter | 2004-07-13 13:07:03 -0400 (Tue, 13 Jul 2004) | 2 lines M /Zope3/trunk/src/transaction/__init__.py M /Zope3/trunk/src/transaction/_transaction.py M /Zope3/trunk/src/transaction/tests/test_transaction.py Converted XXX to TODO. r25953 | sidnei | 2004-06-23 13:14:20 -0400 (Wed, 23 Jun 2004) | 1 line M /Zope3/trunk/src/ZODB/interfaces.py M /Zope3/trunk/src/transaction/_transaction.py Add missing sortKey method to ZopeDBTransactionManager and DataManagerAdapter, and also add it to the interface. r25273 | philikon | 2004-06-06 04:43:57 -0400 (Sun, 06 Jun 2004) | 4 lines Changed paths: M /Zope3/trunk/src/BTrees M /Zope3/trunk/src/ZODB M /Zope3/trunk/src/persistent Ignore .so files. This fix should probably be merged to the original ZODB tree.
-
Tim Peters authored
-
- 11 Aug, 2004 4 commits
-
-
Tim Peters authored
These are preliminary 3.3c1 release changes.
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
Reworked the way some of the ZEO tests use threads, so that unittest is more likely to notice the real cause of a failure (which usually occurs in a thread), and less likely to latch on to spurious problems resulting from the real failure. Detail: The TestThread class got the (unittest) test case as an argument, and remembered it. If the run() method saw the thread die with an exception, it called testcase.fail() with the formatted exception. But this can't work as apparently intended: unittest's fail() raises an AssertionError then, and the piece of unittest running the test expects to catch that exception and append the message to the result object's list of failures. But the piece of unittest running the test isn't on *this* thread's call stack! It's on the main thread's call stack. So unittest simply raised an exception that wasn't noticed by anything, and the thread died then, leaving a traceback somewhere in the middle of the output. unittest didn't know anything about that, and sometimes thought the test passed despite the thread failure. Alas, when a thread dies like this it's also got a decent chance of leaving things in a state where the test's final checking code can't succeed, but the checking code doesn't know the thread died either, and spurious unittest failures and errors could get reported then. Reworked things so that only the main thread ever tries to tell unittest that a test failed. A TestThread remembers an exception- death now, but doesn't report it until the main thread tries to join it. This way unittest knows the test failed; records and reports the true cause of failure; and, because tests generally join all their threads before doing their final checking, unittest stops the test before final checking if a thread death occurred, and so there's less chance of seeing reports of spurious errors and failures.
-
- 27 Jul, 2004 2 commits
-
-
Tim Peters authored
Repair type in pack() docstring.
-
Tim Peters authored
repozo improvement suggested by Toby Dickenson. Write backups to a temp file first; flush and fsync when done; only then rename; in case of a crash, no relevant damaged file will be left behind then. And on Windows, Python's os.fsync() is necessary to convince the OS to write anything to disk.
-
- 11 Jul, 2004 1 commit
-
-
Tim Peters authored
Repaired massive lies I introduced about whether fsrefs requires application code to be available. Noted that fsrefs also partly verifies the sanity of the .fs.index file.
-
- 10 Jul, 2004 1 commit
-
-
Tim Peters authored
Repaired a bug wherein spurious error msgs could be produced after reporting a problem with an unloadable object (discovered by eyeball, while staring at the code to figure out what it actually does). Vastly expanded the module docstring, with a slimmed-down version of the new fsrefs docs on the ZODB Wiki.
-
- 08 Jul, 2004 1 commit
-
-
Tim Peters authored
Zope3-dev Collector #139: Memory leak involving buckets and connections Connection objects were typically immortal because the threaded transaction manager kept them in ever-growing lists. Reworked the transaction manager internals to use a simple implementation of weak sets instead. This plugs all leaks in the test program attached to the collector report (which was leaking about 100KB/sec on my box).
-
- 02 Jul, 2004 1 commit
-
-
Tim Peters authored
Forward-porting from Zope 2.7. Merged from 3.3 branch, revision 26085. The checkFullTimeStamp() test was sensitive to unique mktime() behavior on FreeBSD. See: http://lists.freebsd.org/pipermail/freebsd-standards/2003-November/000268.html The purpose of this test is to exercise ZODB's TimeStamp object, so got rid of dependence on platform mktime() and time.timezone quirks -- TimeStamp works in GMT, so how mktime() treats tm_isdst should be irrelevant in all TimeStamp tests. Also added a comment about the highly non-obvious numeric characteristics of TimeStamp's treatment of seconds (round-tripping is surprisingly inaccurate, but for a real reason).
-
- 29 Jun, 2004 2 commits
-
-
Tim Peters authored
New interface IResourceManager intends to combine the best aspects of IDataManager and IDataManagerOriginal, and will become "the" interface. New interface ISavePoint captures (along with models in collaborations.txt) what should be a clean design for a savepoint/rollback facility that actually works.
-
Jim Fulton authored
Updated an old collaboration to reflect the change.
-
- 28 Jun, 2004 1 commit
-
-
Tim Peters authored
are in now (partly ZODB 3, partly ZODB 4, partly transitional). More is needed. Added new collaborations.txt, which spells out some dynamics of the system in a compact way. This is in a format Jim used for Zope 3, essentially a flat-text and less-formal representation of UML sequence diagrams.
-
- 25 Jun, 2004 1 commit
-
-
Tim Peters authored
No commit message
-
- 22 Jun, 2004 4 commits
-
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
and include that in the ZODB project. While we're at it, include zope.testing too, as zope.interface depends on that, and we had copied zope.testing.loggingsupport.py into ZODB earlier anyway (and delete that unique copy here now). This also merges some changes made to the ZODB copy in Zope3 back into ZODB.
-
- 21 Jun, 2004 2 commits
-
-
Tim Peters authored
Collector 1327: FileStorage init confused by time travel If the system clock moved back in time more than 30 days between a FileStorage close and (re)open, new txn ids could be smaller than txn ids already in the database. Plugged that hole.
-
Tim Peters authored
-
- 18 Jun, 2004 1 commit
-
-
Tim Peters authored
3.3 didn't have the bug, and this confirms it.
-
- 17 Jun, 2004 1 commit
-
-
Tim Peters authored
-
- 15 Jun, 2004 2 commits
-
-
Fred Drake authored
(identical to revision 25416 on the ZODB-3.3 branch, but svn would not merge the change)
-
Fred Drake authored
-
- 08 Jun, 2004 5 commits
-
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Fred Drake authored
(equivalent to revision 25293 on the ZODB 3.3 branch, but not a merge, since the files were added separately after the branch was made)
-
- 07 Jun, 2004 2 commits
-
-
Fred Drake authored
this was in Releases/ZODB3/ on cvs.zope.org
-
Tim Peters authored
-