homepage

The attached Latex file (librunpy.tex) contains the
documentation for PEP 338's proposed runpy module.
I haven't included a patch for lib.tex or
Makefile.deps, since those changes are fairly trivial
and I'm not too particular about where the module gets
slotted into the Library reference.

Logged In: YES 
user_id=1038590
Minor tweak to run_function_code to clarify the problem with
resolving names when the locals and globals dictionaries are
different.

Logged In: YES 
user_id=1038590
Updated to avoid trying to hide exec's quirks

Logged In: YES 
user_id=1038590
PEP 338 has been updated as of 18-Feb-2006. Those changes
are still to be incorporated into this documentation.

Logged In: YES 
user_id=1038590
Updated to match Feb 18 version of PEP.

Logged In: YES 
user_id=1038590
Kicking in Fred's direction to check my formatting isn't too
horrible and to decide where to include it in the Library
Reference table of contents.

Logged In: YES 
user_id=671362
amk has committed his PEP328 to whatsnew, so that should be 
helpful.
Following his style:
- use \programopt for "-m" option 
- use \pep{} for PEP links
- add seealso section
 
And as for your document,
- s/initialised/initialized
> where to include it in the Library Reference table of 
contents.
I'd like to give my vote to:
- imp
- zipimport
- *runpy*
- pkgutil
- modulefinder
-- george

Logged In: YES 
user_id=1038590
Incorporated George's suggestions, and placed immediately
after modulefinder in the Table of Contents.
Checked in as rev 43294.