Allow me to confess that the following low-priority bug actually bit me: You can't have packages be an empty list. The build directory does not get created and the installer complains it can't copy the tree. Why might I be running distutils to install "nothing"? The CXX package consists of header files and some C and C++ source files; no python files or extension modules at the moment. I propose to put the source files (needed by a builder of a CXX extension) into PYTHON/etc/CXX. The include files get treated like Numeric's. I can obviously work around this but it is a generally nice idea that end cases work.
On 18 May 2000, Paul F. Dubois said:
You can't have packages be an empty list. The build directory does not get created and the installer complains it can't copy the tree.
Ahh, oops -- I've fixed this. Now "install" won't even run "install_lib" if there are no Python modules or extensions to build, *and* "install_lib" warns (rather than blows up) if the build directory doesn't exist. (Necessary in case some agent other than the "install" command runs "install_lib" -- eg. the user.) This will get into the next release or snapshot or whatever it turns out to be. Greg -- Greg Ward - Unix nerd gward@python.net http://starship.python.net/~gward/ I'm on a strict vegetarian diet -- I only eat vegetarians.
participants (2)
-
Greg Ward -
Paul F. Dubois