Mailman 3 August 2001 - Distutils-SIG

Sample setup.py for Numeric Python
by Greg Ward 29 Apr '18

29 Apr '18

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 29 Apr '18

29 Apr '18

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 29 Apr '18

29 Apr '18

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 29 Apr '18

29 Apr '18

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 29 Apr '18

29 Apr '18

3 2

bdist_inno again
by Bernhard Herzog 11 Sep '01

11 Sep '01

Hi all, a bdist_inno command to generate an installer with Inno Setup has been discussed previously but I don't know whether anybody has done anything about it. Has anything changed in this regard? Has anybody started to write it? I'll start writing it myself, otherwise. I don't know how general it will be, though. All I really need at the moment is an implementation that's good enough for my needs. Bernhard -- Intevation GmbH http://intevation.de/ Sketch http://sketch.sourceforge.net/ MapIt! http://mapit.de/

3 4

Re: [XML-SIG] Problem installing PyXMLv0.6.6
by Fred L. Drake, Jr. 06 Sep '01

06 Sep '01

In a message to the XML-SIG, Thomas Heller writes: > From: "Göran Rolfsson" <Goran.Rolfsson(a)reachin.se> > > Hi! I first tried the exe-version ( I have NT), but it wants me to select > > the Python installation to use, without showing me any to choose among, and > > without the possibility to specify a path. And yes, I have Python installed > > on my machine (actually in several versions). > > Göran, > > the exe-version is probably built with distutils bdist_wininst command. > This looks in the registry under > HKEY_LOCAL_MACHINE\Software\Python\PythonCore\x.y\InstallPath > to find the location where Pythin is installed. (x.y is the required > version 2.0, 2.1, whatever). > This registry key is created by the installer when you install Python > itself. If you compiled it from source, it will not be present. Would it make sense to enhance the search strategy a bit? I'll propose the following strawman: 1. Start with what it already does. 2. Search the PATH for "python.exe" 3. Ask the user to specify exactly where is should go. I don't know how much work this would be, but it might help people that do build from source, or who use an alternate installer that doesn't upt things in the registry (PythonWare, for instance). -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation

2 5

first cut at fortran support for distutils
by eric jones 31 Aug '01

31 Aug '01

Travis Oliphant and I have hacked together Fortran support for distutils in the course of putting together scipy (www.scipy.org). I won't pretend its pretty, but it does seem to do the job on Linux and W2000/W98 using the mingw32 version of gcc/g77. We're also working on Sun and Irix. Basically, the static_clib has been modified to build static libraries of the fortran code that are then linked with the extension module interface (written in C). We'd like to work toward this becoming a standard part of distutils. Are others interested in this? Also, opinions on how to best pursue its inclusion are welcomed. If your interested, please grab the source version of scipy from the site and take a look at fortran_support.py, build_flib.py, build_clib_new.py, and setup.py. thanks, eric

3 2

generate MANIFEST from CVS
by Bernhard Herzog 28 Aug '01

28 Aug '01

Hi all, over the last few weeks, I've been using distutils for the first time on a real and non-trivial project and so far it works fine. I am currently tweaking the MANIFEST.in file to include all the files that have to be distributed and no others. This turns out to be quite time-consuming because there are quite a few files with that aren't included by default. It seems to me that for a project managed by CVS there's a much more convenient way to get at the list of files. Normally, all files controlled by CVS should be distributed. In most cases, that will be enough, but there may some generated files that should be included anyway, such as perhaps swigged wrappers so that he user doesn't have to install SWIG to compile a package. Getting the list of files under CVS control is quite simple, you just extract them from the CVS/Entries files and recurse into subdirectories which are under CVS control. I'm not sure yet how to integrate this with distutils properly. At the moment I think having a cvs command in MANIFEST.in would be best. That way you could add or remove files from the list of CVS controlled files. The one problem I see with that is that when you unpack a source distribution its impossible to generate the list of CVS controlled files again, so another setup.py sdist command won't include all the files. This is easy to work round though, as you can simply distribute a MANIFEST.cvs file containing the CVS filenames which would have to be included in the MANIFEST somehow. The cvs command could do this, too: if run in a directory checked out from CVS, i.e. if CVS/Entries exists, generate the list of CVS-controlled files, write them into MANIFEST.cvs and include them in MANIFEST. If not run in a CVS directory, MANIFEST.cvs must exist and the files listed there are included in MANIFEST. In both cases MANIFEST.cvs will have to be in MANIFEST, too. Thoughts? Bernhard -- Intevation GmbH http://intevation.de/ Sketch http://sketch.sourceforge.net/ MapIt! http://mapit.de/

2 2

RE: [Distutils] Swig for Windows
by Moore, Paul 24 Aug '01

24 Aug '01

From: Thomas Heller [mailto:thomas.heller@ion-tof.com] > Distutils probably works with SWIG1.1, which has the > -dnone flag. It seems you can still download this one > (maybe only the source distro). [...] > IIRC, you have to set a SWIG_LIB environment variable, > but it should be somewhere in the docs. Thanks to Thomas, and all who replied. I found sources for SWIG 1.1, and built them from scratch. They work fine for me. By the way, I made a minor modification to the sources so that rather than looking in a hard-coded location, followed by the SWIG_LIB environment variable, it looks for the libraries relative to the location of the executable, and then in SWIG_LIB. This makes it easier to package up and move around... I assume a similar thing could be done for the new version, as well... Paul.

1 0

syntax errors in Python source files
by Jeremy Hylton 23 Aug '01

23 Aug '01

I just tried to build and install a distutils package using Python 1.5.2. The package uses some features added after 1.5.2 and a few files have SyntaxErrors as a result. I did a "setup.py build" and didn't get any complaints, but I did get errors when I tried the install. Does setup.py build generate .pyc files? It seems like it must not, or I should have seen errors when I did the build. If it doesn't, it seems like it should; otherwise you'll fail to catch SyntaxErrors until install time. Jeremy

1 0

Swig for Windows
by Moore, Paul 23 Aug '01

23 Aug '01

Hi, Where can I get a working version of swig (suitable for use with Python distutils) for Windows? The downloads from the web site don't work out of the box - distutils uses a -dnone argument, which they don't support, and they don't seem to find the python.swg file when run by hand - I get errors >swig -python example.i Generating wrappers for Python SWIG : Fatal error. Unable to locate python.swg. (Possible installation problem) This is just downloading and extracting to a new directory which I put into my PATH (not how I'd like to do it, but the simplest guess in the absence of any obvious installation instructions :-() Thanks, Paul

2 1

build_scripts and #!/usr/bin/env
by Andrew Kuchling 16 Aug '01

16 Aug '01

The build_scripts command changes the #! line of Python scripts to match the Python installation being used to run the setup.py script. Currently it only fixes lines of the form #!/a/b/c/python, but leaves '#!/usr/bin/env python' alone. It used to also change #!/usr/bin/env lines, but I changed that behaviour because I think it's wrong and leaves you with no way at all to install a script that uses /usr/bin/env . A bug caused by this is at http://sourceforge.net/tracker/index.php?func=detail&aid=409430&group_id=54… I think this is a silly use case, where you want pydoc to use a different Python from the default interpreter you get by running 'python', but will bow to the SIG's opinion. So, fix /usr/bin/env lines or not? --amk

1 0

Headers files
by Sophie Coon 15 Aug '01

15 Aug '01

Hi , I am pretty new with distutils and I am using it for creating source distibution of my packages. I don't understand why distutils doesn't include automatically headers files needed for extension modules ? Thanks for any feed back. Sophie -- ############################################################ Sophie COON The Scripps Research Institute Research Programmer III Molecular Graphics Laboratory 10550 North Torrey Pines Road Phone: (858) 784-9556 La Jolla, CA 92037 Fax : (858) 784-2860 ############################################################

3 2

Re: [Distutils] behavior when failing to build an extension?
by Just van Rossum 09 Aug '01

09 Aug '01

Bernhard Herzog wrote: > Yes, distutils stops with a message along the lines of > error: command 'gcc' failed with exit status 1 > > That's also what e.g. make does by default, unless you run it with the > -k flag. Ok, thanks, then there's not much for me to do, except perhaps at some point make the error message nicer: it now crashes with a nasty traceback... Btw. does really nobody have any advice on my ranlib question of a couple of days ago? Just

2 2

behavior when failing to build an extension?
by Just van Rossum 09 Aug '01

09 Aug '01

What's the intended behavior if an extension fails to build? Should it print an error message and continue, or should it stop? (On the Mac distutils currently stops, which is kindof a nuisance, so I'm tempted to "fix" it...) Just

2 3

configuration
by Robin Becker 07 Aug '01

07 Aug '01

Just v.R has been having some problems compiling a particular library that needed libart. libart has a configuration script that should properly be invoked before building the library. Are there any plans to ease the invocation of such scripts or alternatively how to I determine in python things like endianness in size, short size long size etc etc. For all I know Darwin might run on both big and little endian machines so it's wrong to rely simply on the platform for this sort of thing. -- Robin Becker

2 1

unixcompile.py, Darwin (MacOSX), ranlib?
by Just van Rossum 07 Aug '01

07 Aug '01

I've noticed that when building a static library as part of a setup.py, I have to do ranlib build/temp.<platformname>/*.a and then run "python setup.py build" again before it works. <platformname> is "darwin-1.3.7-Power Macintosh-2.1". Can anyone suggest a patch to unixcompiler.py so that ranlib is invoked under Darwin? I've seen the comment "Not many Unices required ranlib anymore", so apparently Darwin is one of these... Just

1 0

Intermediat library and sdist problem
by Sophie Coon 07 Aug '01

07 Aug '01

Hi, I am trying to write a setup.py to create a source distribution for a wrapped library. The trick is that I need to build an intermediate library and the sdist command doesn't seem to like it. Here is the setup.py that I wrote. ========================================================================================= import os, sys, string from distutils.sysconfig import get_python_inc from distutils.core import setup, Extension # key is python version : value is the correspondent python directory name versionPath = {'2.0':'python2.0', '1.5.2':'python1.5', '2.1':'python2.1'} # Where the source file for the amber library are. libamberSrcs = ['./src/binpos.c', './src/conjgrad.c', './src/memutil.c', './src/prm.c', './src/sff.c', './src/rand2.c'] # Here could be replace by sys.prefix and sys.exec_prefix. # That will be for the distribution purpose. version = string.split(sys.version)[0] depInclude = sys.exec_prefix + '/include/%s/'%versionPath[version] numInclude = sys.prefix+'/include/%s/Numeric/'%versionPath[version] shareInclude = sys.prefix+'/include/%s/'%versionPath[version] setup( name = 'amber', version = '94', description = 'Simple Force Field (SFF) package from Amber', author = "Tom Mackle, David Case", packages = [''], libraries = [('libamber', {'sources':libamberSrcs, 'include_dirs':['./src/',depInclude, numInclude, shareInclude ], 'macros':[]}, ),], ext_modules = [Extension('sffCmodule', ['sffCmodule.c',], include_dirs = ['./src/',depInclude, numInclude,shareInclude,], libraries=['libamber']) ]) ========================================================================================================================= python2.0 setup.py sdist gives me the following error message: Traceback (innermost last): File "setup.py", line 44, in ? libraries=['libamber']) File "/tsri/python/share/lib/python1.5/site-packages/distutils/core.py", line 138, in setup dist.run_commands() File "/tsri/python/share/lib/python1.5/site-packages/distutils/dist.py", line 829, in run_commands self.run_command(cmd) File "/tsri/python/share/lib/python1.5/site-packages/distutils/dist.py", line 849, in run_command cmd_obj.run() File "/tsri/python/share/lib/python1.5/site-packages/distutils/command/sdist.py", line 143, in run self.get_file_list() File "/tsri/python/share/lib/python1.5/site-packages/distutils/command/sdist.py", line 242, in get_file_list self.add_defaults() File "/tsri/python/share/lib/python1.5/site-packages/distutils/command/sdist.py", line 319, in add_defaults self.filelist.extend(build_clib.get_source_files()) File "/tsri/python/share/lib/python1.5/site-packages/distutils/cmd.py", line 107, in __getattr__ raise AttributeError, attr AttributeError: get_source_files I can very successfully run the following command: python2.0 setup.py bdist python2.0 setup.py build In the last case I have a working package that I can import from a python interpreter. I am pretty sure that the sdist command doesn't work because the intermediate library has not benn build yet when trying to do the tar ball. Did I make a mistake in the setup.py? if not is there a way around that problem? Thanks for any suggestions ! Sophie -- ############################################################ Sophie COON The Scripps Research Institute Research Programmer III Molecular Graphics Laboratory 10550 North Torrey Pines Road Phone: (858) 784-9556 La Jolla, CA 92037 Fax : (858) 784-2860 ############################################################

2 1