Mailman 3 December 2000 - 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

installer does not see current Pythons
by Rene Liebscher 03 Jan '01

03 Jan '01

Any ideas how to solve this, or needs this for some users a special distribution as zip-file. > Support Request #110549, was updated on 2000-Dec-22 17:22 > You can respond by visiting: > http://sourceforge.net/support/?func=detailsupport&support_id=110549&group_… > > Category: None > Status: Open > Priority: 5 > Summary: installer does not see current Pythons > > By: fredy > Date: 2000-Dec-22 17:22 > > Message: > Logged In: YES > user_id=20580 > Browser: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0) > > I downloaded PyOpenGL-1.5.6b1.win32-py1.5.2.exe and > executed it on my Windows NT 4.0 machine. When the > installer displays the "select python installation to > use" screen it fails to list anything and I am > blocked, even though I have both Python 1.5.2 and 1.6 > installed, along with whatever Python comes with Zope > 2.2. What can I do now to install PyOpenGL? > Kind regards Rene Liebscher

1 1

Bdist_notsodumb
by Paul Prescod 20 Dec '00

20 Dec '00

I've got this idea and I'd like to have it either shot-down or verified. The idea is that instead of supporting more and more binary dist packaging mechanisms, we would distribute Python extensions as a zipfile. (I choose zip because Python has a standard zipfile module but I don't think it has a tar module) In the root directory of the zipfile would be an "install.py". That would install the module in the Python distribution that it is launched from. Installing the module would consist of unzipping and running "install.py". Because install.py would always be in the same place, the downloading and installing of Python extensions could be automated. The procedure would be identical on all platforms. The majority of the infrastructure used by the install scripts could live in Python itself. In summary, why wouldn't we define a binary structure for Python extensions rather than worrying about the vagaries of each platform's package mechanism? Paul Prescod

1 0

Including documentation into a Windows installer
by Martin v. Loewis 20 Dec '00

20 Dec '00

I'm trying to get a number of files into the binary package which are considered as documentation. For RPMs, I simply do [bdist_rpm] doc_files = ANNOUNCE,CREDITS,LICENCE,README,README.dom,README.pyexpat,README.sgmlop,doc,demo,test Even though some of these names are actually directories, the RPM building process uses the source distribution to determine which files to include. Specifically, these names get listed as %doc directives, which are then installed into /usr/doc/<package>. Since there is no dedicated documentation directory on Windows, I'd like to put these files into a directory xmldoc next to the _xmlplus directory which is the Python package. I managed to compute the list of file names and directories myself using the FileList class. How can I get a set of files into the Windows installer, while preserving the directory structure? Any help appreciated, Martin

3 3

error adding library dirs on commandline
by Pete Shinners 19 Dec '00

19 Dec '00

on running under windows here. whenever i try to add library directories to build_ext on the commandline i'm getting an error. File "c:\python\lib\distutils\command\build_ext.py", line 159, in finalize_options self.library_dirs.append(os.path.join(sys.exec_prefix, 'libs')) AttributeError: append it turns out that library_dirs is a string type. in build_ext.py line 143 it looks like the code is checking for strings in self.libraries. from my quick look it would solve the problem to also check library_dirs also. also, the commandline help for -L says to pass all library directories in a semicolon separated list. when i do this the self.library_dirs is still just a string containing my list with the semicolons. (it wouldn't seem like this gets split later on?) using multiple include paths with the semicolons does appear to work correctly. although i would probably prefer to allow multiple -I flags. (currently the 'last' -I flag overrides the previous) am i correct in guessing these commandline arguments aren't used too often? i'm thinking i'll just parse -I and -L arguments off of the commandline myself for now. although i'm also seeking better advice :]

1 0

Re: 4suite for Mac
by Mike Olson 19 Dec '00

19 Dec '00

Mike Olson wrote: I guess I need to go to sleep or something. I'll try this again. Sorry for the spam Mike > > Mike Olson wrote: > > So I go and send it to the wrong address. Now I will post this message > to distutils. > > Mike > > > > > Robert Hahn wrote: > > > > > > Hi, guys. > > > > Hi Robert, > > > > Thanks for the interest in 4Suite. However, I'd like to defer your > > question to python's distutils SIG. 4Suite uses distutils to build its > > C code, and install itself. I do try to follow the distutils list > > (though I sometimes fall behind), and I think I remember someone saying > > they did some work to get some things to compile on the Mac (thoug not > > 4Suite). I'm hoping they pop up and give you some help. Unfortuatly I > > haven't used a Mac since the Mac plus line so I won't be too much help. > > > > Mike > > > > > > > > I've been looking for a quick way to get XSLT processing for the Mac, > > > and thought that 4Suite might be the fastest way to go. I see, however, > > > that installation isn't straightforward for me. :/ > > > > > > If we assume that I can compile the bits written in C, then what, > > > theoretically, has to change in setup.py so that installation would be > > > flawless. > > > > > > Pls. note: I'm new at programming, but am willing to learn. I've > > > downloaded Apple's MPW kit (contains a free C compiler), but don't know > > > how to use it... yet. > > > > > > OTOH, if you know of some other XSLT software for the Mac that would > > > have a lower barrier to use, I would appreciate some leads... > > > > > > thx, > > > Robert Hahn > > > > -- > > Mike Olson Principal Consultant > > mike.olson(a)fourthought.com (303)583-9900 x 102 > > Fourthought, Inc. http://Fourthought.com > > Software-engineering, knowledge-management, XML, CORBA, Linux, Python > > -- > Mike Olson Principal Consultant > mike.olson(a)fourthought.com (303)583-9900 x 102 > Fourthought, Inc. http://Fourthought.com > Software-engineering, knowledge-management, XML, CORBA, Linux, Python -- Mike Olson Principal Consultant mike.olson(a)fourthought.com (303)583-9900 x 102 Fourthought, Inc. http://Fourthought.com Software-engineering, knowledge-management, XML, CORBA, Linux, Python

1 0