- 01 Apr, 2003 9 commits
-
-
Jeremy Hylton authored
-
Jeremy Hylton authored
details.
-
Jeremy Hylton authored
The cache is intended to keep weak references to objects. An object should be deallocated when the only references to it are in the cache. If an object is unghostified and added to the list of live objects, the list should have a borrowed reference. Otherwise, the cache will keep the object alive after all other references have disappeared.
-
Jeremy Hylton authored
time. Instead use std PyDict_GetItem() and incref only when necessary.
-
Jeremy Hylton authored
The cache decrefed it in percachedel.
-
Jeremy Hylton authored
PyDict_DelItem() will undo the other INCREF.
-
Jeremy Hylton authored
-
Jeremy Hylton authored
Decref its reference to the cache. In a debug build, account for the two bogus additions to _Py_RefTotal. Also, reindent initcPickleCache().
-
Barry Warsaw authored
-
- 31 Mar, 2003 2 commits
-
-
Jeremy Hylton authored
-
Jeremy Hylton authored
Remove object_from_oid() which appeared to be mis-used about half the time. Instead use std PyDict_GetItem() and incref only when necessary. Make sure an object's reference to its cache is decref'd when the object is deallocated. This change seems to eliminate leaking pickle caches. Remaining mystery: Why do objects stay in the cache even when there are no references to them?
-
- 26 Mar, 2003 1 commit
-
-
Fred Drake authored
-
- 25 Mar, 2003 2 commits
-
-
Fred Drake authored
-
Fred Drake authored
release.
-
- 24 Mar, 2003 7 commits
-
-
Fred Drake authored
-
Fred Drake authored
-
Fred Drake authored
descriptions.
-
Fred Drake authored
and are of questionable value. "constructor" is also generally unsafe; applications that need it can provide their own version of this if necessary.
-
Fred Drake authored
- simplify document structure at one point
-
Fred Drake authored
-
Fred Drake authored
- fixed datatype of the values for "handler" attributes - removed/commented out all mentions of schema component extension; that's really not complete and should probably be thought through again - moved docs for legacy API out; these should not be generally documented - misc. small fixes
-
- 21 Mar, 2003 1 commit
-
-
Fred Drake authored
-
- 20 Mar, 2003 1 commit
-
-
Jeremy Hylton authored
The manager should raise an exception in its prepare() method rather than returning a boolean to indicate failure. Rationale: The txn manager can't raise a reasonable exception, because it doesn't know what the data manager couldn't prepare.
-
- 17 Mar, 2003 10 commits
-
-
Fred Drake authored
It may be reasonable to change this more, but the benefits aren't clear. (These changes will be used from the new-install-branch.)
-
Fred Drake authored
make it easier to re-locate an instance.
-
Fred Drake authored
-
Jeremy Hylton authored
-
Jeremy Hylton authored
-
Jeremy Hylton authored
Don't ever stop after the first object. It leaves all the other objects in the version unmodified.
-
Jeremy Hylton authored
-
Jeremy Hylton authored
Fix edge case in pack() -- backpointer to object created in version.
-
Jeremy Hylton authored
-
Jeremy Hylton authored
-
- 16 Mar, 2003 1 commit
-
-
Tim Peters authored
pair) from the bucket into the set-iteration struct twice. I don't believe this had any visible effect, it was simply pointless and wasted a little time (discovered by eyeball).
-
- 13 Mar, 2003 1 commit
-
-
Albertas Agejevas authored
Other than fixes of nonconforming whitespace, just a couple of $Id$ docstrings has been added.
-
- 10 Mar, 2003 2 commits
-
-
Jeremy Hylton authored
-
Jeremy Hylton authored
-
- 07 Mar, 2003 3 commits
-
-
Jeremy Hylton authored
It's not clear what the right answer is here. The implementation aborts any remaining resource managers and hopes for the best, which isn't very satisfying. Perhaps the hosed feature should come back. Add some comments about the issues involved. Revise the tests to cover the current behavior.
-
Jeremy Hylton authored
-
Jeremy Hylton authored
XXX Should the manager duplicate these checks?
-