Commit 2f5e79ed authored by Jeremy Hylton's avatar Jeremy Hylton

Remove MUCH_RING_CHECKING option, which was disabled.

As the comment said:

    Not really necessary in production code... disable this before
    release, providing noone has been reporting and RuntimeErrors
    that it uses to report problems.
parent d59317da
This diff is collapsed.
......@@ -13,9 +13,9 @@
##############################################################################
"""Database connection support
$Id: Connection.py,v 1.77 2002/10/04 20:44:25 jeremy Exp $"""
$Id: Connection.py,v 1.78 2002/10/23 19:18:35 jeremy Exp $"""
from cPickleCache import PickleCache, MUCH_RING_CHECKING
from cPickleCache import PickleCache
from POSException import ConflictError, ReadConflictError
from ExtensionClass import Base
import ExportImport, TmpStore
......@@ -31,13 +31,6 @@ from types import StringType, ClassType
global_code_timestamp = 0
if MUCH_RING_CHECKING:
# To get rid of this warning, change the define inside
# cPickleCache.c and recompile.
LOG('ZODB',WARNING,
'Using cPickleCache with low performance (but extra debugging checks)')
del MUCH_RING_CHECKING
def updateCodeTimestamp():
'''
Called after changes are made to persistence-based classes.
......
This diff is collapsed.
This diff is collapsed.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment