python/nondist/peps pep-0262.txt,1.15,1.16
Update of /cvsroot/python/python/nondist/peps In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv22695 Modified Files: pep-0262.txt Log Message: Add section for open issues Index: pep-0262.txt =================================================================== RCS file: /cvsroot/python/python/nondist/peps/pep-0262.txt,v retrieving revision 1.15 retrieving revision 1.16 diff -C2 -d -r1.15 -r1.16 *** pep-0262.txt 8 Mar 2004 13:51:59 -0000 1.15 --- pep-0262.txt 8 Mar 2004 14:09:21 -0000 1.16 *************** *** 247,250 **** --- 247,281 ---- + 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
participants (1)
-
akuchling@users.sourceforge.net