Mailman 3 June 2001 - 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

Re: Distutils-SIG digest, Vol 1 #542 - 1 msg
by Dean Goodmanson June 29, 2001

June 29, 2001

>From: distutils-sig-request(a)python.org >Reply-To: distutils-sig(a)python.org >To: distutils-sig(a)python.org >Subject: Distutils-SIG digest, Vol 1 #542 - 1 msg >Date: Fri, 29 Jun 2001 12:01:03 -0400 > >Send Distutils-SIG mailing list submissions to > distutils-sig(a)python.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/distutils-sig >or, via email, send a message with subject or body 'help' to > distutils-sig-request(a)python.org > >You can reach the person managing the list at > distutils-sig-admin(a)python.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Distutils-SIG digest..." > > >Today's Topics: > > 1. Trouble installing on a VPS (a shared web hosting setup) (tracy s. >ruggles) > >--__--__-- > >Message: 1 >Date: Thu, 28 Jun 2001 18:05:38 -0500 >From: "tracy s. ruggles" <trace(a)reinventnow.com> >To: <distutils-sig(a)python.org> >Subject: [Distutils] Trouble installing on a VPS (a shared web hosting >setup) > >Hi, > >I've been troubling myself with trying to install MySQLdb on my VPS (a >shared web hosting setup). > >I have my own copy of Python running out of my /usr/local directory. > >I have had to edit Lib/distutils/sysconfig.py to have it return the >appropriate include and library directories. It assumes a certain >structure >of directories from the root directory. But, my root directory is actually >/usr/home/ol0401 > >Anyway, here's what I get when I try to run the MySQLdb setup.py script: > >.. > > ol0401.vwh.net% python setup.py build > running build > running build_py > not copying CompatMysqldb.py (output up-to-date) > not copying _mysql_exceptions.py (output up-to-date) > not copying MySQLdb/__init__.py (output up-to-date) > not copying MySQLdb/converters.py (output up-to-date) > not copying MySQLdb/connections.py (output up-to-date) > not copying MySQLdb/cursors.py (output up-to-date) > not copying MySQLdb/sets.py (output up-to-date) > not copying MySQLdb/times.py (output up-to-date) > not copying MySQLdb/constants/__init__.py (output up-to-date) > not copying MySQLdb/constants/CR.py (output up-to-date) > not copying MySQLdb/constants/FIELD_TYPE.py (output up-to-date) > not copying MySQLdb/constants/ER.py (output up-to-date) > not copying MySQLdb/constants/FLAG.py (output up-to-date) > not copying MySQLdb/constants/REFRESH.py (output up-to-date) > not copying MySQLdb/constants/CLIENT.py (output up-to-date) > running build_ext > building '_mysql' extension > skipping _mysql.c (build/temp.solaris-2.6-sun4u-2.1/_mysql.o >up-to-date) > gcc -shared build/temp.solaris-2.6-sun4u-2.1/_mysql.o >/usr/home/ol0401/usr/local/mysql-3.23.38/lib/mysql/libmysqlclient.a >-L/usr/home/ol0401/usr/local/mysql-3.23.38/lib/mysql >-R/usr/home/ol0401/usr/local/mysql-3.23.38/lib/mysql -lmysqlclient -lz -o >build/lib.solaris-2.6-sun4u-2.1/_mysql.so > /usr/local/sparc-sun-solaris2.6/bin/ld: cannot open -lz: No such file >or >directory > collect2: ld returned 1 exit status > error: command 'gcc' failed with exit status 1 > ol0401.vwh.net% > >.. > >As you can see, it successfully builds many of the files, but chokes when >it >starts to build the _mysql extension. > >I've verified that all of the files listed in that last "gcc" command >actually exist, except for the _mysql.so file. > >I'm totally unfamiliar with gcc and building in general. Does anyone know >what's going on here? > >And, also, is there a way to get the distutils package to work when it's >being run in an environment where the user is in a shared web hosting >environment? > >Thanks, >Tracy > > >-- >Tracy S. Ruggles :: trace(a)reinventnow.com :: 512/858.2280 > >"RHUBARB. / Rhubarb is susan not susan not seat in bunch toys not wild and >laughable not in little places not in neglect and vegetable not in fold >coal >age not please." -- Gertrude Stein > > > > > >--__--__-- > >_______________________________________________ >Distutils-SIG maillist - Distutils-SIG(a)python.org >http://mail.python.org/mailman/listinfo/distutils-sig > > >End of Distutils-SIG Digest _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com

1 0

Trouble installing on a VPS (a shared web hosting setup)
by tracy s. ruggles June 28, 2001

June 28, 2001

Hi, I've been troubling myself with trying to install MySQLdb on my VPS (a shared web hosting setup). I have my own copy of Python running out of my /usr/local directory. I have had to edit Lib/distutils/sysconfig.py to have it return the appropriate include and library directories. It assumes a certain structure of directories from the root directory. But, my root directory is actually /usr/home/ol0401 Anyway, here's what I get when I try to run the MySQLdb setup.py script: .. ol0401.vwh.net% python setup.py build running build running build_py not copying CompatMysqldb.py (output up-to-date) not copying _mysql_exceptions.py (output up-to-date) not copying MySQLdb/__init__.py (output up-to-date) not copying MySQLdb/converters.py (output up-to-date) not copying MySQLdb/connections.py (output up-to-date) not copying MySQLdb/cursors.py (output up-to-date) not copying MySQLdb/sets.py (output up-to-date) not copying MySQLdb/times.py (output up-to-date) not copying MySQLdb/constants/__init__.py (output up-to-date) not copying MySQLdb/constants/CR.py (output up-to-date) not copying MySQLdb/constants/FIELD_TYPE.py (output up-to-date) not copying MySQLdb/constants/ER.py (output up-to-date) not copying MySQLdb/constants/FLAG.py (output up-to-date) not copying MySQLdb/constants/REFRESH.py (output up-to-date) not copying MySQLdb/constants/CLIENT.py (output up-to-date) running build_ext building '_mysql' extension skipping _mysql.c (build/temp.solaris-2.6-sun4u-2.1/_mysql.o up-to-date) gcc -shared build/temp.solaris-2.6-sun4u-2.1/_mysql.o /usr/home/ol0401/usr/local/mysql-3.23.38/lib/mysql/libmysqlclient.a -L/usr/home/ol0401/usr/local/mysql-3.23.38/lib/mysql -R/usr/home/ol0401/usr/local/mysql-3.23.38/lib/mysql -lmysqlclient -lz -o build/lib.solaris-2.6-sun4u-2.1/_mysql.so /usr/local/sparc-sun-solaris2.6/bin/ld: cannot open -lz: No such file or directory collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 ol0401.vwh.net% .. As you can see, it successfully builds many of the files, but chokes when it starts to build the _mysql extension. I've verified that all of the files listed in that last "gcc" command actually exist, except for the _mysql.so file. I'm totally unfamiliar with gcc and building in general. Does anyone know what's going on here? And, also, is there a way to get the distutils package to work when it's being run in an environment where the user is in a shared web hosting environment? Thanks, Tracy -- Tracy S. Ruggles :: trace(a)reinventnow.com :: 512/858.2280 "RHUBARB. / Rhubarb is susan not susan not seat in bunch toys not wild and laughable not in little places not in neglect and vegetable not in fold coal age not please." -- Gertrude Stein

1 0

libtool support
by Juergen Hermann June 26, 2001

June 26, 2001

Hi! Did anyone invest any work into libtool support, i.e. linking of libtool (.la) libraries? Would there be interest in such a thing? Ciao, Jürgen -- Jürgen Hermann, Developer (jhe(a)webde-ag.de) WEB.DE AG, http://webde-ag.de/

1 0

a couple of distutils questions
by Toby Sargeant June 26, 2001

June 26, 2001

This is my first use of the distutils package, so I accept that I might have gone about things the wrong way. Initially for my freetype 2 extension module, I used autoconf to build a Setup.in file for building the module. I decided to switch to using distutils recently, and in doing so wanted to still be able to provide the --freetype-path and --with-pil-headers options to deal with different install locations for freetype and PIL. After a lot of poking around and many false starts, it seemed that there wasn't a good way to handle command line arguments that didn't involve extensive poking around in internal distutils objects. Eventually I gave up and just used the following code: handle={ '--freetype-path=' : optFreetypePath, '--with-pil-headers=' : optPilHeaders } arg=1 while arg<len(sys.argv): for k,v in handle.items(): if sys.argv[arg][:len(k)]==k: if v is not None: v(sys.argv[arg][len(k):]) del sys.argv[arg] break else: arg=arg+1 which seems like a rather large hack to me. What's the preferred distutils approach? Additionally, I noticed that the Extension object takes a runtime_library_path option, but the unixcompiler object spits out a -R/my/path option, which gcc doesn't like. Using extra_link_args seems like a sure way to tie yourself down to one compiler, though, so I'm not sure what I can do in this case. Toby. -- [ Toby Sargeant : Inpharmatica : Developer : t.sargeant(a)inpharmatica.co.uk ] [ http://www.inpharmatica.co.uk : 020 7074 4600 fax 020 7631 4844 ]

1 0

'Other' languages (than C)
by John J. Lee June 22, 2001

June 22, 2001

Has it been decided where the best place is in distutils to put support for non-C languages (FORTRAN is my particular wish)? John

1 0