I don't normally run Windows, so it will take a little timefor me to set up a Windows build environment. However, I'vemade a number of other improvements as a result of further testingon Linux, and I've uploaded the improved patch as doctest-fixes6.diff.When I apply this patch to a regular Python 2.7 installation onWindows (Windows 2000 running under VirtualBox on Linux), the testspass (as well as on my Linux box when applied against therelease27-maint SVN branch).Output from testing on Windows:C:\Python27\Lib\test>python test_doctest.pydoctest (doctest) ... 66 tests with zero failuresdoctest (test.test_doctest) ... 443 tests with zero failuresC:\Python27\Lib\test>pythonPython 2.7 (r27:82525, Jul  4 2010, 09:01:59) [MSC v.1500 32 bit (Intel)] on win32Type "help", "copyright", "credits" or "license" for more information.Hopefully the improved patch will test OK on your box as well. Ifnot, I'll work on testing it in a Windows build environment againstan SVN checkout.Improvements in doctest-fixes6.diff:- Uses with statements to guard all file reads (in earlier patches  writes were guarded but reads were not);- Saves and restores sys.path the same way as test_importhooks;- Checks for byte-compiled files in __pycache__ when deleting  temporary files (this was in the py3k patch already, but readingPEP 3147 it looks like this feature may be backported to 2.7 as  well);- Test setup/cleanup is now done in a TestFixture class, for clarity  and because it's easier that way to store the original sys.path  in the setup and restore it in the cleanup.