Mailman 3 October 1999 - Distutils-SIG

Sample setup.py for Numeric Python
by Greg Ward April 29, 2018

April 29, 2018

Hi again -- [cc'd to Paul Dubois: you said you weren't following the distutils sig anymore, but this directly concerns NumPy and I'd like to get your input!] here's that sample setup.py for NumPy. See below for discussion (and questions!). ------------------------------------------------------------------------ #!/usr/bin/env python # Setup script example for building the Numeric extension to Python. # This does sucessfully compile all the .dlls. Nothing happens # with the .py files currently. # Move this file to the Numerical directory of the LLNL numpy # distribution and run as: # python numpysetup.py --verbose build_ext # # created 1999/08 Perry Stoll __rcsid__ = "$Id: numpysetup.py,v 1.1 1999/09/12 20:42:48 gward Exp $" from distutils.core import setup setup (name = "numerical", version = "0.01", description = "Numerical Extension to Python", url = "http://www.python.org/sigs/matrix-sig/", ext_modules = [ ( '_numpy', { 'sources' : [ 'Src/_numpymodule.c', 'Src/arrayobject.c', 'Src/ufuncobject.c' ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/numpy.def' } ), ( 'multiarray', { 'sources' : ['Src/multiarraymodule.c'], 'include_dirs' : ['./Include'], 'def_file': 'Src/multiarray.def' } ), ( 'umath', { 'sources': ['Src/umathmodule.c'], 'include_dirs' : ['./Include'], 'def_file' : 'Src/umath.def' } ), ( 'fftpack', { 'sources': ['Src/fftpackmodule.c', 'Src/fftpack.c'], 'include_dirs' : ['./Include'], 'def_file' : 'Src/fftpack.def' } ), ( 'lapack_lite', { 'sources' : [ 'Src/lapack_litemodule.c', 'Src/dlapack_lite.c', 'Src/zlapack_lite.c', 'Src/blas_lite.c', 'Src/f2c_lite.c' ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/lapack_lite.def' } ), ( 'ranlib', { 'sources': ['Src/ranlibmodule.c', 'Src/ranlib.c', 'Src/com.c', 'Src/linpack.c', ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/ranlib.def' } ), ] ) ------------------------------------------------------------------------ First, what d'you think? Too clunky and verbose? Too much information for each extension? I kind of think so, but I'm not sure how to reduce it elegantly. Right now, the internal data structures needed to compile a module are pretty obviously exposed: is this a good thing? Or should there be some more compact form for setup.py that will be expanded later into the full glory we see above? I've already made one small step towards reducing the amount of cruft by factoring 'include_dirs' out and supplying it directly as a parameter to 'setup()'. (But that needs code not in the CVS archive yet, so I've left the sample setup.py the same for now.) The next thing I'd like to do is get that damn "def_file" out of there. To support it in MSVCCompiler, there's already an ugly hack that unnecessarily affects both the UnixCCompiler and CCompiler classes, and I want to get rid of that. (I refer to passing the 'build_info' dictionary into the compiler classes, if you're familiar with the code -- that dictionary is part of the Distutils extension-building system, and should not propagate into the more general compiler classes.) But I don't want to give these weird "def file" things standing on the order of source files, object files, libraries, etc., because they seem to me to be a bizarre artifact of one particular compiler, rather than something present in a wide range of C/C++ compilers. Based on the NumPy model, it seems like there's a not-too-kludgy way to handle this problem. Namely: if building extension "foo": if file "foo.def" found in same directory as "foo.c" add "/def:foo.def" to MSVC command line this will of course require some platform-specific code in the build_ext command class, but I figured that was coming eventually, so why put it off? ;-) To make this hack work with NumPy, one change would be necessary: rename Src/numpy.def to Src/_numpy.def to match Src/_numpy.c, which implements the _numpy module. Would this be too much to ask of NumPy? (Paul?) What about other module distributions that support MSVC++ and thus ship with "def" files? Could they be made to accomodate this scheme? Thanks for your feedback -- Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

4 5

Can now compile simple extensions
by Greg Ward April 29, 2018

April 29, 2018

Hi all -- at long last, I found the time to hack in the ability to compile extension modules to the Distutils. Mainly, this meant adding a 'build_ext' command which uses a CCompiler instance for all its dirty work. I also had to add a few methods to CCompiler (and, of course, UnixCCompiler) to make this work. And I added a new module, 'spawn', which takes care of running sub-programs more efficiently and robustly (no shell involved) than os.system. That's needed, obviously, so we can run the compiler! If you're in the mood for grubbing over raw source code, then get the latest from CVS or download a current snapshot. See http://www.python.org/sigs/distutils-sig/implementation.html for a link to the code snapshot. I'm still waiting for more subclasses of CCompiler to appear. At the very least, we're going to need MSVCCompiler to build extensions on Windows. Any takers? Also, someone who knows the Mac, and how to run compilers programmatically there, will have to figure out how to write a Mac-specific concrete CCompiler subclass. The spawn module also needs a bit of work to be portable. I suspect that _win32_spawn() (the intended analog to my _posix_spawn()) will be easy to implement, if it even needs to go in a separate function at all. It looks from the Python Library documentation for 1.5.2 that the os.spawnv() function is all we need, but it's a bit hard to figure out just what's needed. Windows wizards, please take a look at the 'spawn()' function and see if you can make it work on Windows. As for actually compiling extensions: well, if you can figure out the build_ext command, go ahead and give it a whirl. It's a bit cryptic right now, since there's no documentation and no example setup.py. (I have a working example at home, but it's not available online.) If you feel up to it, though, see if you can read the code and figure out what's going on. I'm just hoping *I'll* be able to figure out what's going on when I get back from the O'Reilly conference next week... ;-) Enjoy -- Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

2 1

Two fixes (at last)
by Greg Ward April 29, 2018

April 29, 2018

Hi all -- at long last, I have fixed two problems that a couple people noticed a while ago: * I folded in Amos Latteier's NT patches almost verbatim -- just changed an `os.path.sep == "/"' to `os.name == "posix"' and added some comments bitching about the inadequacy of the current library installation model (I think this is Python's fault, but for now Distutils is slavishly aping the situation in Python 1.5.x) * I fixed the problem whereby running "setup.py install" without doing anything else caused a crash (because 'build' hadn't yet been run). Now, the 'install' command automatically runs 'build' before doing anything; to make this bearable, I added a 'have_run' dictionary to the Distribution class to keep track of which commands have been run. So now not only are command classes singletons, but their 'run' method can only be invoked once -- both restrictions enforced by Distribution. The code is checked into CVS, or you can download a snapshot at http://www.python.org/sigs/distutils-sig/distutils-19990607.tar.gz Hope someone (Amos?) can try the new version under NT. Any takers for Mac OS? BTW, all parties involved in the Great "Where Do We Install Stuff?" Debate should take a good, hard look at the 'set_final_options()' method of the Install class in distutils/install.py; this is where all the policy decisions about where to install files are made. Currently it apes the Python 1.5 situation as closely as I could figure it out. Obviously, this is subject to change -- I just don't know to *what* it will change! Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

2 1

Package versioning
by Timothy Docker April 29, 2018

April 29, 2018

Hi all, I've been aware that the distutils sig has been simmerring away, but until recently it has not been directly relevant to what I do. I like the look of the proposed api, but have one question. Will this support an installed system that has multiple versions of the same package installed simultaneously? If not, then this would seem to be a significant limitation, especially when dependencies between packages are considered. Assuming it does, then how will this be achieved? I am presently managing this with a messy arrangement of symlinks. A package is installed with its version number in it's name, and a separate directory is created for an application with links from the unversioned package name to the versioned one. Then I just set the pythonpath to this directory. A sample of what the directory looks like is shown below. I'm sure there is a better solution that this, and I'm not sure that this would work under windows anyway (does windows have symlinks?). So, has this SIG considered such versioning issues yet? Cheers, Tim -------------------------------------------------------------- Tim Docker timd(a)macquarie.com.au Quantative Applications Division Macquarie Bank -------------------------------------------------------------- qad16:qad $ ls -l lib/python/ total 110 drwxr-xr-x 2 mts mts 512 Nov 11 11:23 1.1 -r--r----- 1 root mts 45172 Sep 1 1998 cdrmodule_0_7_1.so drwxr-xr-x 2 mts mts 512 Sep 1 1998 chart_1_1 drwxr-xr-x 3 mts mts 512 Sep 1 1998 Fnorb_0_7_1 dr-xr-x--- 3 mts mts 512 Nov 11 11:21 Fnorb_0_8 drwxr-xr-x 3 mts mts 1536 Mar 3 12:45 mts_1_1 dr-xr-x--- 7 mts mts 512 Nov 11 11:22 OpenGL_1_5_1 dr-xr-x--- 2 mts mts 1024 Nov 11 11:23 PIL_0_3 drwxr-xr-x 3 mts mts 512 Sep 1 1998 Pmw_0_7 dr-xr-x--- 2 mts mts 512 Nov 11 11:21 v3d_1_1 qad16:qad $ ls -l lib/python/1.1 total 30 lrwxrwxrwx 1 root other 29 Apr 10 10:43 _glumodule.so -> ../OpenGL_1_5_1/_glumodule.so lrwxrwxrwx 1 root other 30 Apr 10 10:43 _glutmodule.so -> ../OpenGL_1_5_1/_glutmodule.so lrwxrwxrwx 1 root other 22 Apr 10 10:43 _imaging.so -> ../PIL_0_3/_imaging.so lrwxrwxrwx 1 root other 36 Apr 10 10:43 _opengl_nummodule.so -> ../OpenGL_1_5_1/_opengl_nummodule.so lrwxrwxrwx 1 root other 27 Apr 10 10:43 _tkinter.so -> ../OpenGL_1_5_1/_tkinter.so lrwxrwxrwx 1 mts mts 21 Apr 10 10:43 cdrmodule.so -> ../cdrmodule_0_7_1.so lrwxrwxrwx 1 mts mts 12 Apr 10 10:43 chart -> ../chart_1_1 lrwxrwxrwx 1 root other 12 Apr 10 10:43 Fnorb -> ../Fnorb_0_8 lrwxrwxrwx 1 mts mts 12 Apr 10 10:43 mts -> ../mts_1_1 lrwxrwxrwx 1 root other 15 Apr 10 10:43 OpenGL -> ../OpenGL_1_5_1 lrwxrwxrwx 1 root other 33 Apr 10 10:43 opengltrmodule.so -> ../OpenGL_1_5_1/opengltrmodule.so lrwxrwxrwx 1 root other 33 Apr 10 10:43 openglutil_num.so -> ../OpenGL_1_5_1/openglutil_num.so lrwxrwxrwx 1 root other 10 Apr 10 10:43 PIL -> ../PIL_0_3 lrwxrwxrwx 1 mts mts 10 Apr 10 10:43 Pmw -> ../Pmw_0_7 lrwxrwxrwx 1 root other 10 Apr 10 10:43 v3d -> ../v3d_1_1

3 2

[Distutils-sig] distutils charter and interscript
by John Skaller April 29, 2018

April 29, 2018

3 2

ANNOUNCE: Distutils 0.1.1
by Greg Ward Oct. 23, 1999

Oct. 23, 1999

Finally got around to fixing those Windows portability bugs. Also hacked on the "dist" command a bit, and did some interesting stuff with global options. Here's the change log: release 0.1.1: * fixed 'mkpath()' function so it should work under DOS/Windows * changes to how we link C code: - under Unix, object files precede -l options on link command line - libraries now can have a directory component, which forces the library to be searched for in only that directory * added --force and --quiet global options * made global options (--verbose, --dry-run, and now --force and --quiet too) valid at each command as well as for the whole distribution * 'dist' command now works on Unices other than Linux; generates tar, tar.Z, tar.gz, and ZIP files. Still Unix-dependent though. RTFS, or the CVS logs, for details. Oh yeah: download it from http://www.python.org/sigs/distutils-sig/ Enjoy! Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

1 0

patch to utils.py for Windows os.path.isdir glitch
by Fred Yankowski Oct. 23, 1999

Oct. 23, 1999

I was finally able to install the distutils 0.1 package on my Windows NT machine running Python 1.5.2, after getting around two problems: 1) I had a very old python.exe sitting in my PATH, which when run would report itself as Python version 1.5.2 but would cause sys.prefix and sys.exec_prefix to be empty because Python couldn't find the expected libraries relative to the python.exe location. I deleted that old python.exe and now sys.prefix and sys.exec_prefix are set correctly. Thanks to Mark Hammond for suggesting the fix. 2) Running 'python -v start.py install' would result in an exception in utils.py when os.mkdir() would be called on an existing directory. It seems that on Windows, os.path.isdir() does not accept trailing backslashes on a directory name. For example, os.path.isdir('c:\\progra~1') returns 1 on my machine, but os.path.isdir('c:\\progra~1\\') returns 0. I tweaked utils.py to account for that and now the installation seems to finish OK. I have attached the patch with my suggested change. -- Fred Yankowski fred(a)OntoSys.com tel: +1.630.879.1312 Principal Consultant www.OntoSys.com fax: +1.630.879.1370 OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA -- =================================================================== RCS file: RCS/util.py retrieving revision 1.1 retrieving revision 1.2 diff -c -r1.1 -r1.2 *** util.py 1999/10/22 18:32:41 1.1 --- util.py 1999/10/22 19:35:03 1.2 *************** *** 37,50 **** # the creation of the whole path? (quite easy to do the latter since # we're not using a recursive algorithm) if os.path.isdir (name): return if PATH_CREATED.get (name): return (head, tail) = os.path.split (name) - if not tail: # in case 'name' has trailing slash - (head, tail) = os.path.split (head) tails = [tail] # stack of lone dirs to create while head and tail and not os.path.isdir (head): --- 37,52 ---- # the creation of the whole path? (quite easy to do the latter since # we're not using a recursive algorithm) + (head, tail) = os.path.split (name) + if not tail: # in case 'name' has trailing slash + name = head + if os.path.isdir (name): return if PATH_CREATED.get (name): return (head, tail) = os.path.split (name) tails = [tail] # stack of lone dirs to create while head and tail and not os.path.isdir (head):

2 1

Installing applications
by Paul F. Dubois Oct. 8, 1999

Oct. 8, 1999

I know that I don't read a lot of what goes on in our manuals, newsgroups and sigs, so if this problem has a known answer I would appreciate a pointer. Distutils solves the "install a package" problem. Now, how do we solve the "make it an application" problem? Here is what I mean. I have a Python package with a driver routine inside. I need some way of starting up Python with that script as the input. So I end up writing something like this example from the Pyfort package, file pyfort: #!/usr/bin/env python import Pyfort.driver import sys Pyfort.driver.run(sys.argv[1:]) The first problem for me is that this chooses the python on the path, not necessarily the python into which I have installed this package. In our environment we have multiple Pythons since we version our software package. So if someone runs "pyfort" all is well, but if they do /usr/local/cdat/experimental/bin/pyfort <args> but their path finds /usr/local/cdat/public/bin/python, the import Pyfort.driver gets the "public" rather than the "experimental" version. But if I hardwire the path into the first line, I can't tar it up and send it to somebody somewhere else. (Like to my customers, for example). Python has a -c option, but I can't expect the users to cram the above into a -c line. The second problem is that I had to write (and more seriously, install) this little file in the first place. Seems dumb when all I want is the effect of python /usr/local/cdat/experimental/lib/python1.5/site-packages/Pyfort/driver.py <args> We have another app where essentially we want to run python, import some stuff, and go to the prompt.

2 1

distutils installation fails in WinNT; sys.exec_prefix empty
by Fred Yankowski Oct. 6, 1999

Oct. 6, 1999

Greetings, I just downloaded Distutils-0.1.tar.gz (which might be better named Distutils-0.1.tgz to accommodate WinZip), expanded it, and tried installing it by running 'python -v setup.py install'. It ran OK for a while, then took an exception in _init_nt() in sysconfig.py, apparently because sys.exec_prefix (and sys.prefix, for that matter) are both set to '' on my system. I just installed Python 1.5.2 yesterday, on a WinNT 4.0 (SP 5) machine. Other than choosing a non-default installation path (different volume), I think I took all defaults when running the Python installer. -- Fred Yankowski <fcy(a)acm.org>

1 0

Oh yeah! one more feature
by Greg Ward Oct. 4, 1999

Oct. 4, 1999

Whoops, I totally forgot to mention the other potentially useful feature I added this weekend. Now, entries in the 'libraries' list can include a directory component, which will tell the compiler interface to instruct the C compiler to look only in that directory for that particular library. Umm, was that too opaque? Here's an example. Before this change, the example pil_setup.py included with the Distutils had this: ext_modules = \ [('_imaging', { 'sources': # ... # ... 'library_dirs': ['libImaging', '/usr/local/lib'], 'libraries': ['Imaging', 'jpeg', 'z', 'tcl8.0', 'tk8.0'] } This resulted (on Unix) in a link command like this: gcc -shared ... -LlibImaging -L/usr/local/lib \ -lImaging -ljpeg -lz -ltcl8.0 -ltk8.0 Now, we can specify that the "Imaging" library must come from the "libImaging" subdirectory, rather than being searched for all over the place. The current pil_setup.py has this: ext_modules = \ [('_imaging', { 'sources': # ... # ... 'library_dirs': ['/usr/local/lib'], 'libraries': ['libImaging/Imaging', 'jpeg', 'z', 'tcl8.0', 'tk8.0'] } Now the link command looks like this: gcc -shared ... -L/usr/local/lib \ libImaging/Imaging.a -ljpeg -lz -ltcl8.0 -ltk8.0 Note that this has the unpleasant consequence that the Distutils compiler class (UnixCCompiler, in this case) has to second-guess what the linker does to find a particular library. This isn't too hard for me using GCC, since GCC is fairly well documented in this regard. However I'm sure there are Unices where my rash assumptions (if "dir/foo" found in 'libraries' list, look for "dir/libfoo.so", then "dir/libfoo.a") will not hold. Of course, the directory can be absolute -- this shoots portability to hell, but should be welcome if you're using the Distutils as a private build tool and just want to be sure you're linking in *exactly* such-and-such version of a library. I know at least one person (hi Paul!) who will like this. And the implementation of this feature for MSVC is a wild guess on my part. Again, Windows people are kindly requested to take a look and see how close to reality my guess is. (See the 'gen_lib_options()' function in distutils.ccompiler, and then the 'find_library_file()' method in both distutils.unixccompiler and distutils.msvccompiler.) This code is all in yesterday's snapshot. Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

3 3