From 19a5b5b1fa6624e6f0f76ded92da2dace52ec288 Mon Sep 17 00:00:00 2001
From: Skip Montanaro <skip@pobox.com>
Date: Wed, 29 Jan 2003 22:49:04 +0000
Subject: [PATCH] Expand abstract slightly.  Reference patch containing
 beginnings of implementation.

---
 pep-0304.txt | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/pep-0304.txt b/pep-0304.txt
index 53a3e3160..103f4e015 100644
--- a/pep-0304.txt
+++ b/pep-0304.txt
@@ -20,7 +20,9 @@ the python-dev mailing list [2]_.  The introduction of an environment
 variable will allow people installing Python or Python-based
 third-party packages to control whether or not bytecode files should
 be generated at installation time, and if so, where they should be
-written.
+written.  It will also allow users to control whether or not bytecode
+files should be generated at application run-time, and if so, where
+they should be written.
 
 
 Proposal
@@ -273,6 +275,11 @@ not writable by the current user.
   Intermediate directories will be created as needed.
 
 
+Implementation
+==============
+
+See the patch on Sourceforge. [6]_
+
 References
 ==========
 
@@ -291,6 +298,9 @@ References
 .. [5] PEP 302, New Import Hooks, van Rossum and Moore
    (http://www.python.org/dev/peps/pep-0302.html)
 
+.. [6] patch 677103, PYTHONBYTECODEBASE patch (PEP 304), Montanaro
+   (http://www.python.org/sf/677103)
+
 
 Copyright
 =========