Software: Apache/2.0.54 (Unix) mod_perl/1.99_09 Perl/v5.8.0 mod_ssl/2.0.54 OpenSSL/0.9.7l DAV/2 FrontPage/5.0.2.2635 PHP/4.4.0 mod_gzip/2.0.26.1a 

uname -a: Linux snow.he.net 4.4.276-v2-mono-1 #1 SMP Wed Jul 21 11:21:17 PDT 2021 i686 

uid=99(nobody) gid=98(nobody) groups=98(nobody) 

Safe-mode: OFF (not secure)

/usr/doc/python-2.2.3/html/lib/   drwxr-xr-x
Free 318.34 GB of 458.09 GB (69.49%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     node125.html (4.29 KB)      -rw-r--r--

Python Library Reference

Previous: 5.2.2 Which Docstrings Are Up: 5.2 doctest Next: 5.2.4 What About Exceptions?

---

5.2.3 What's the Execution Context?

By default, each time testmod finds a docstring to test, it uses a copy of M's globals, so that running tests on a module doesn't change the module's real globals, and so that one test in M can't leave behind crumbs that accidentally allow another test to work. This means examples can freely use any names defined at top-level in M, and names defined earlier in the docstring being run.

You can force use of your own dict as the execution context by passing globs=your_dict to testmod() instead. Presumably this would be a copy of M.__dict__ merged with the globals from other imported modules.

---

Python Library Reference

Previous: 5.2.2 Which Docstrings Are Up: 5.2 doctest Next: 5.2.4 What About Exceptions?

---

Release 2.2.3, documentation updated on 30 May 2003.