Mailman 3 September 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

Jython support?
by R Datta Sept. 30, 2001

Sept. 30, 2001

Sorry if this has been covered in the past. I'm new to this sig. I DID search the archives, and didn't come up with anything of help. Is there distutil support for jython? i tried to install it, but of course setup.py wouldn't run because distutils module wasnt there :) Chicken n egg. If indeed there is no support for jython, how do jython developers install python modules? Thanks Raj Datta Professional Services Direct : 408-530-4932 CrossAccess Corp Cell : 408-316-5473 2900 Gordon Ave #100 Fax : 408-735-0328 Santa Clara CA 95051 Email : rdatta(a)crossaccess.com

2 2

RE: Function discussions...
by Michel Sanner Sept. 27, 2001

Sept. 27, 2001

> Date: Thu, 27 Sep 2001 13:09:14 -0500 > From: Tarn Weisner Burton <twburton(a)mailaps.org> > Subject: RE: Function discussions... > To: Michel Sanner <sanner(a)scripps.edu> > Cc: "Mike C. Fletcher" <mcfletch(a)users.sourceforge.net> > MIME-version: 1.0 > X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > Content-transfer-encoding: 7BIT > Importance: Normal > X-Priority: 3 (Normal) > X-MSMail-priority: Normal > > | here is the end of the output: > | > | creating build/temp.irix64-6.5-2.1 > | cc -O -OPT:Olimit=0 -DGLX_PLATFORM -DNUMERIC > | -I/tsri/python/share/include/python2.1 -I/usr/include > | -I/usr/local/include > | -I/usr/X11/include -I/tsri/python/share/include/python2.1/Numeric > | -I/tsri/python/share/include/python2.1/Numeric_17 > | -I/tsri/python/share/include/python2.1/Numeric_18 -Isrc/gle/src > | -I/usr/include > | -I/usr/local/include -I/usr/X11/include > | -I/tsri/python/share/include/python2.1/Numeric > | -I/tsri/python/share/include/python2.1/Numeric_17 > | -I/tsri/python/share/include/python2.1/Numeric_18 -Isrc/gle/src -c > | src/interface_util/interface_util.c -o > | build/temp.irix64-6.5-2.1/interface_util.o > | > | cc-1005 cc: ERROR File = > | /tsri/python/share/include/python2.1/Python.h, Line = > | 24 > | The source file "config.h" is unavailable. > | > | #include "config.h" > | ^ > | > | 1 catastrophic error detected in the compilation of > | "src/interface_util/interface_util.c". > | Compilation terminated. > | error: command 'cc' failed with exit status 2 > > I'm not sure if there is anything I can do to fix this. You might try > making sure that you have the most recent version of distutils. Aside from > that it should work since others have installed on Irix 6.5 successfully. > Maybe something in the python installation is munged up. The include > directories selected for the python system are done by distutils and not by > the PyOpenGL setup directly.... > I updated our Distutils from 1.0.2.pre to 1.0.2 and still get the same error. This sounds like a bug in Distutils to me. It seems that it automatically adds sys.prefix+'/include/python'+sys.version[:3] to the include directories, which works fine as long as your Python interpreter is installed under sys.prefix in which case config.h is really in sys.prefix+'/include/python'+sys.version[:3]. But I believe that it still is legal to install Python specifying sys.exec_prefix, in which case config.h is found in sys.exec_prefix+'/include/python'+sys.version[:3] I checked with Sophie Coon (who has used Disutils previousely to build extensions here) and she confirmed that she had to add this directory explicitly using the setup.py file. For PyOpenGL, we tried to add: depInclude = sys.exec_prefix + '/include/python' + sys.version[:3] and: libraries = [('interface_util', {'sources':['src/interface_util/interface_util.c','src/interface_util/platform.c '], 'include_dirs' : [depInclude]}), but the directory still does not show up on the compilation line :( -Michel

1 0

Bug in build_ext
by M.-A. Lemburg Sept. 23, 2001

Sept. 23, 2001

The build_ext command (and probably others too) don't clean up the build_temp directory before invoking the compiler. This causes the compiler to use object files it finds in the temp location for subsequent builds of other subpackages which is most probably not intended. Should I fix this bug in CVS by having the build_ext command clean up the temporary tree before invoking the compiler ? -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Consulting & Company: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/

1 1

mac osx support?
by Pete Shinners Sept. 13, 2001

Sept. 13, 2001

i've been trying to walk one of my users through compiling on max osx. it seems many things are wrong (or at least unframiliar) on osx. our first problem was needing a bunch of customish compile flags like "-framework". but we've got that all worked out. we've realized that distutils is adding no linking flags for the python libraries. no -L for its location, and no -l to actually link it. well that is strange, so we thought we'd force some flags to the link command, but that brought us to our next problem.. where are the shared libraries? we found something at /usr/local/lib/python2.1/python.so, but that won't exactly work with the compile, since "-lpython" looks for "libpython.so" (or is that not the case?) the user also found some files in /usr/local/lib/config like another "python.so" and a " libpython2.1.a". somethings funny. this osx user has compiled and installed his own version of python. these were his configure options... "--with-dyld --with-suffix=.x" any sort of help on this would be much appreciated, we're both entirely stumped. we have seen some problems like this on some mailing lists, but the only solutions we've been able to find are to link the extensions statically into python. i don't think that's really an option for us. :[

1 0

RE: [Distutils] Help - Does wininst ignore MANIFEST?
by Patrick K. O'Brien Sept. 12, 2001

Sept. 12, 2001

Here is the setup.py that is finally working for me, at least on Windows, including being able to create a windows installer version as well. Thanks Robin and Andy. #!/usr/bin/env python """Setup file for the distribution of PyCrust. PyCrust is a pure Python distribution. Thanks to Andy Todd, who created the original setup.py for PyCrust.""" __author__ = "Patrick K. O'Brien <pobrien(a)orbtech.com>" __cvsid__ = "$Id: setup.py,v 1.1 2001/09/12 16:16:32 pobrien Exp $" __date__ = "September 11, 2001" __version__ = "$Revision: 1.1 $"[11:-2] from distutils.core import setup import version import glob setup(name="PyCrust", version=str(version.VERSION), description="PyCrust - The Flakiest Python Shell", author="Patrick K. O'Brien", author_email="pobrien(a)orbtech.com", url="http://sourceforge.net/projects/pycrust/", packages=["PyCrust"], package_dir={"PyCrust": "."}, long_description=""" PyCrust is an interactive Python environment written in Python. PyCrust components can run standalone or be integrated into other development environments and/or other Python applications. PyCrust comes with an interactive Python shell (PyShell), an interactive namespace/object tree control (PyFilling) and an integrated, split-window combination of the two (PyCrust). """, data_files=[("PyCrust", ["PyCrust.ico",]), ("PyCrust/Data", glob.glob("Data/*.py")), ("PyCrust/Demos", glob.glob("Demos/*.py")), ("PyCrust/Docs", glob.glob("Docs/*.txt")), ], ) --- Patrick K. O'Brien Orbtech (http://www.orbtech.com) "I am, therefore I think." -----Original Message----- From: Andy Todd [mailto:andy47@crosswinds.net] Sent: Wednesday, September 12, 2001 5:46 PM To: pobrien(a)orbtech.com Subject: Re: [Distutils] Help - Does wininst ignore MANIFEST? I've got to agree with you there Patrick. The distutils setup for PythonCard is driving me nuts at the moment.

1 0