|
125 | 125 | project links in. |
126 | 126 |
|
127 | 127 |
|
128 | | -_bsddb |
129 | | - To use the version of bsddb that Python is built with by default, invoke |
130 | | - (in the dist directory) |
131 | | - |
132 | | - svn export http://svn.python.org/projects/external/db-4.4.20 |
133 | | - |
134 | | - Then open db-4.4.20\build_win32\Berkeley_DB.dsw and build the "db_static" |
135 | | - project for "Release" mode. |
136 | | - |
137 | | - Alternatively, if you want to start with the original sources, |
138 | | - go to Sleepycat's download page: |
139 | | - http://www.sleepycat.com/downloads/releasehistorybdb.html |
140 | | - |
141 | | - and download version 4.4.20. |
142 | | - |
143 | | - With or without strong cryptography? You can choose either with or |
144 | | - without strong cryptography, as per the instructions below. By |
145 | | - default, Python is built and distributed WITHOUT strong crypto. |
146 | | - |
147 | | - Unpack the sources; if you downloaded the non-crypto version, rename |
148 | | - the directory from db-4.4.20.NC to db-4.4.20. |
149 | | - |
150 | | - Now apply any patches that apply to your version. |
151 | | - |
152 | | - To run extensive tests, pass "-u bsddb" to regrtest.py. test_bsddb3.py |
153 | | - is then enabled. Running in verbose mode may be helpful. |
154 | | - |
155 | | - XXX The test_bsddb3 tests don't always pass, on Windows (according to |
156 | | - XXX me) or on Linux (according to Barry). (I had much better luck |
157 | | - XXX on Win2K than on Win98SE.) The common failure mode across platforms |
158 | | - XXX is |
159 | | - XXX DBAgainError: (11, 'Resource temporarily unavailable -- unable |
160 | | - XXX to join the environment') |
161 | | - XXX |
162 | | - XXX and it appears timing-dependent. On Win2K I also saw this once: |
163 | | - XXX |
164 | | - XXX test02_SimpleLocks (bsddb.test.test_thread.HashSimpleThreaded) ... |
165 | | - XXX Exception in thread reader 1: |
166 | | - XXX Traceback (most recent call last): |
167 | | - XXX File "C:\Code\python\lib\threading.py", line 411, in __bootstrap |
168 | | - XXX self.run() |
169 | | - XXX File "C:\Code\python\lib\threading.py", line 399, in run |
170 | | - XXX apply(self.__target, self.__args, self.__kwargs) |
171 | | - XXX File "C:\Code\python\lib\bsddb\test\test_thread.py", line 268, in |
172 | | - XXX readerThread |
173 | | - XXX rec = c.next() |
174 | | - XXX DBLockDeadlockError: (-30996, 'DB_LOCK_DEADLOCK: Locker killed |
175 | | - XXX to resolve a deadlock') |
176 | | - XXX |
177 | | - XXX I'm told that DBLockDeadlockError is expected at times. It |
178 | | - XXX doesn't cause a test to fail when it happens (exceptions in |
179 | | - XXX threads are invisible to unittest). |
180 | | - |
181 | | - |
182 | 128 | _sqlite3 |
183 | 129 | Python wrapper for SQLite library. |
184 | 130 |
|
|
0 commit comments