Add open issues

Author: zooba

peps/pep-0773.rst

@@ -1655,7 +1655,36 @@ match its requirement, but this is not part of the initial proposal.
 Open Issues
 ===========
 
-TODO: Raise open issues
+Generate packages for old versions
+----------------------------------
+
+At present, we can install versions of Python back to 3.5 from the NuGet feed.
+These are identical to the traditional installer releases of the same versions,
+but do not include Tkinter, IDLE, documentation, or the test suite. However, it
+is very little work (and no additional storage space) to use them for older
+releases.
+
+New binaries releases will generate new packages, even for already released
+versions (currently 3.12 and 3.13). So these will exist. The open issue is
+whether we go back through old releases and generate full PyManager packages for
+them all, and how far back to go. This is merely repackaging, and does not
+require rebuilding or modifying the release.
+
+
+Include test suite in PyManager packages
+----------------------------------------
+
+The test suite consumes the majority of the size of our current distribution,
+but is not intended to be used by most of our users. By omitting it from the
+standard PyManager package, all downloads become smaller and faster, at the cost
+of some users having to obtain the test suite in another way (such as building
+from source).
+
+It seems obviously preferable to have some way to access the exact test suite
+intended for a particular build. So the question is whether to include it by
+default (there are no optional components anymore), to publish it independently
+(for manual download as a ZIP file), or to publish a second feed of packages
+that include both the runtime and the test suite.
 
 
 Footnotes