Add section for open issues

pep-0262.txt

@@ -246,6 +246,37 @@ Deliverables
     patch.
 
 
+Open Issues
+
+    PJE suggests the installation database "be potentially present on
+    every directory in sys.path, with the contents merged in sys.path
+    order.  This would allow home-directory or other
+    alternate-location installs to work, and ease the process of a
+    distutils install command writing the file." Nice feature: it does
+    mean that package manager tools can take into account Python
+    packages that a user has privately installed.
+
+    AMK wonders: what does setup.py do if it's told to install
+    packages to a directory not on sys.path?  Does it write an
+    install-db directory to the directory it's told to write to, or
+    does it do nothing?
+
+    Should the package-database file itself be included in the files
+    list?  (PJE would think yes, but of course it can't contain its
+    own checksum.  AMK can't think of a use case where including the
+    DB file matters.)
+
+    PJE wonders about writing the package DB file
+    *first*, before installing any other files, so that failed partial
+    installations can both be backed out, and recognized as broken.
+    This PEP may have to specify some algorithm for recognizing this
+    situation.
+
+    Should we guarantee the format of installation databases remains
+    compatible across Python versions, or is it subject to arbitrary
+    change?  Probably we need to guarantee compatibility.
+
+    
 Rejected Suggestions
 
     Instead of using one text file per distribution, one large text