Removed XXX block about a test_bsddb3 failure that went away a long time ago.
diff --git a/PCbuild/readme.txt b/PCbuild/readme.txt
index 487bf3e..9aa28f2 100644
--- a/PCbuild/readme.txt
+++ b/PCbuild/readme.txt
@@ -238,17 +238,6 @@
XXX doesn't cause a test to fail when it happens (exceptions in
XXX threads are invisible to unittest).
- XXX 11-Apr-2004 tim
- XXX On WinXP Pro, I got one failure from test_bsddb3:
- XXX
- XXX ERROR: test04_n_flag (bsddb.test.test_compat.CompatibilityTestCase)
- XXX Traceback (most recent call last):
- XXX File "C:\Code\python\lib\bsddb\test\test_compat.py", line 86, in test04_n_flag
- XXX f = hashopen(self.filename, 'n')
- XXX File "C:\Code\python\lib\bsddb\__init__.py", line 293, in hashopen
- XXX d.open(file, db.DB_HASH, flags, mode)
- XXX DBInvalidArgError: (22, 'Invalid argument -- DB_TRUNCATE illegal with locking specified')
-
_ssl
Python wrapper for the secure sockets library.