1) Why is the --formats list comma-separated and the --include-dirs and --library-dirs lists not? They are separated by os.pathsep. Well, at least its documented :) 2) The os.pathsep separator is not documented in the help text:
python setup.py build_ext --help ... --library-dirs (-L) directories to search for external C libraries
This should be: ... --library-dirs (-L) colon-separated list of directories to search for external C libraries or whatever os.pathsep is on the current platform. 3) bdist_wininst does not seem to install data files and scripts. If you execute "strings" with the .exe, you will only see Python module files. And I did not found a file with the install log. The installer just copied the files in the Python dir. Bastian
3) bdist_wininst does not seem to install data files and scripts. If you execute "strings" with the .exe, you will only see Python module files. See separate post.
BTW: On which system did you create the installer?
And I did not found a file with the install log. The installer just copied the files in the Python dir. Why do you want this file?
There are hooks in the installer code to create such a file, but they are still unused. Thomas
3) bdist_wininst does not seem to install data files and scripts. If you execute "strings" with the .exe, you will only see Python module files. See separate post.
BTW: On which system did you create the installer? Debian Linux 2.2, Python 1.5.2
And I did not found a file with the install log. The installer just copied the files in the Python dir. Why do you want this file? When I did not found the data files I was curious what had been installed (and where).
Bastian
3) bdist_wininst does not seem to install data files and scripts. If you execute "strings" with the .exe, you will only see Python module files. See separate post.
BTW: On which system did you create the installer? Debian Linux 2.2, Python 1.5.2 The problem is that install, which is run inside bdist_wininst, creates an installation tree in the build directory, and uses the unix installation scheme for it, while bdist_wininst should force the NT installation scheme. On NT, data and scripts are subdirectories of lib, on unix, it is different.
Thomas
On 11 September 2000, Bastian Kleineidam said:
1) Why is the --formats list comma-separated and the --include-dirs and --library-dirs lists not? They are separated by os.pathsep. Well, at least its documented :)
Just because. No seriously: MS-DOS and Unix each have well-established conventions for lists of directories; semicolon is the separator under DOS, and colon under Unix. So we use the local convention. The formats list is just a list of strings, and I've always thought that comma is a perfectly good delimiter for lists of strings.
2) The os.pathsep separator is not documented in the help text:
python setup.py build_ext --help
Fixed, thanks. Greg
participants (3)
-
Bastian Kleineidam -
Greg Ward -
Thomas Heller