Mailman 3 November 2000 - 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] distutil or setup problem?
by Berthold Höllmann Nov. 30, 2000

Nov. 30, 2000

"Thomas Heller" <thomas.heller(a)ion-tof.com> writes: > hoel(a)germanlloyd.org (Berthold Höllmann) writes: > > > > Ahh, I'm wrong. Distutils 1.0.1 do not work with Python 1.5.2 on Win32 > > because the 1.5.2 config.h for Win does *not* contain the neccesarry > > #pragma definitions for the library inclusion (at least in my copy). > > > This is from 1.5.2 config.h: > #ifdef MS_WIN32 > > #ifndef USE_DL_EXPORT > /* So nobody needs to specify the .lib in their Makefile any more */ > #ifdef _DEBUG > #pragma comment(lib,"python15_d.lib") > #else > #pragma comment(lib,"python15.lib") > #endif > #endif /* USE_DL_EXPORT */ > > So, it *should* work... > And it *does* work, just checked it out. > > > So I guess get_libraries in distutils/command/build_ext.py should be > > changed to something like > [snip] > > It has been debated on distutils-sig in the past whether build_ext > should special-case MSVCCompiler or not. Maybe we should remove this > special case completely. > Anyway, I would be interrested why it does not work for you. OK, my boss needed 1.5.2. He made a local install and copied the file to our file server, but only the executables, not the header files, so they are still from 1.5. Now I replaced them with the new ones and it all works better now. Thanks for your help. Greetings Berthold -- email: hoel(a)GermanLloyd.org ) tel. : +49 (40) 3 61 49 - 73 74 ( C[_] These opinions might be mine, but never those of my employer.

1 0

Re: [Distutils] distutil or setup problem?
by Berthold Höllmann Nov. 30, 2000

Nov. 30, 2000

hoel(a)germanlloyd.org (Berthold Höllmann) writes: > "Thomas Heller" <thomas.heller(a)ion-tof.com> writes: > > > As you can see from the comments, 'python15.lib' SHOULD be included by some > > pragma inside 'config.h', which is #included be 'Python.h'. > > May be there is something wrong with the include files? > > Or has this something to do with the fact (IIRC from your first posting), > > that your source code does not reside in some subdirectories? > > Thomas, > > Thanks for your help. It led me to the right direction. I was using > another library that which had anther config.h in it's include > directories, which prevented the python config.h to be used > correctly. After some fiddeling with include pathes, I now can > successfully compile my module. Ahh, I'm wrong. Distutils 1.0.1 do not work with Python 1.5.2 on Win32 because the 1.5.2 config.h for Win does *not* contain the neccesarry #pragma definitions for the library inclusion (at least in my copy). So I guess get_libraries in distutils/command/build_ext.py should be changed to something like def get_libraries (self, ext): """Return the list of libraries to link against when building a shared extension. On most platforms, this is just 'ext.libraries'; on Windows, we add the Python library (eg. python20.dll). """ # The python library is always needed on Windows. For MSVC, this # is redundant, since the library is mentioned in a pragma in # config.h that MSVC groks. The other Windows compilers all seem # to need it mentioned explicitly, though, so that's what we do. # Append '_d' to the python import library on debug builds. from distutils.msvccompiler import MSVCCompiler if sys.platform == "win32" and \ (not isinstance(self.compiler, MSVCCompiler) or sys.version[:5] == 1.5.2): template = "python%d%d" if self.debug: template = template + '_d' pythonlib = (template % (sys.hexversion >> 24, (sys.hexversion >> 16) & 0xff)) # don't extend ext.libraries, it may be shared with other # extensions, it is a reference to the original list return ext.libraries + [pythonlib] else: return ext.libraries to make building extension modules work with 1.5.2. Greetings Berthold -- email: hoel(a)GermanLloyd.org ) tel. : +49 (40) 3 61 49 - 73 74 ( C[_] These opinions might be mine, but never those of my employer.

2 1

distutils extensions
by Alexandre Fayolle Nov. 29, 2000

Nov. 29, 2000

[discussing distutils on xml-sig, since this is becoming distutil-specific, I swich lists. I'm not sure whether Martin von Loewis has subscribed to distutils-sig, though...] > > use doc_files in your setup.cfg file, or --doc_files filelist on the > > command line. > > Thanks, I will try that. 2 remarks: * I typo'ed, it's '--doc-files' (with a dash) * this option does not handle directories, which really is sad. The 4Suite team has overcome this by providing an extension. I'm looking at their code right now, and it looks as if their extension package was really interesting. Is there any chance that it could be incorporated to a future distutils release, or released as a 4Suite spinoff from the fourthought site? Alexandre Fayolle -- http://www.logilab.com Narval is the first software agent available as free software (GPL). LOGILAB, Paris (France).

1 1

PureMingw32CCompiler (cygwinccompiler.py addition)
by Ben Allfree Nov. 29, 2000

Nov. 29, 2000

Hello all, I just discovered the fantastic work done for abstract compilers. What great stuff! I downloaded the CVS snapshot today and added a PureMingw32CCompiler class to show the correct command line to build DLLs and import libraries for MinGW32 2.95.2-1 (the current beta). Maybe somebody could see how to better integrate the changes? Included in my attachment is the changed distutils/cygwinccompiler.py and some test programs. The test programs came from the MinGW32 instructions at: ftp://ftp.nanotech.wisc.edu/pub/khan/gnu-win32/mingw32/snapshots/gcc-2.95.2… For those that do not know, the current MinGW32 beta supports the `-shared' directive and an `--out-implib,libxxx.a' directive. DEF files are no longer needed when building DLLs from object files. As far as I know, we still have to use `dlltool' to build import libraries from DEF files when the DLL's object files are not available. But, I'm not even sure that's supposed to be a compiler function. Take care, Ben Allfree

1 0

problem with bdist_rpm --doc-files
by Alexandre Fayolle Nov. 28, 2000

Nov. 28, 2000

Hello, I could not find the answer in the archive (but them being non searchable makes this difficult...). I'm trying to build a rpm package using distutils 1.0.1 on a redahat 6.2 box (python 1.5.2). I have a script that should go in site-packages, a utility library called lib (maybe not the best choice, I've told the author), and some documentation in 3 directories (doc, dtd anx examples). My setup.py looks like: #!/usr/bin/env python from distutils.core import setup setup(name="pygantt", version= "0.6.0", description = "generates Gantt diagrams from XML specification", author = "Nicolas Chauvat", author_email="Nicolas.Chauvat(a)logilab.fr", url = "http://www.logilab.org/pygantt", #package_dir = {'':'.'}, #packages = ['lib'], py_modules = ['pygantt','lib.HTMLRenderer','lib.Task','lib.common'], ) and the setup.cfg file is: [bdist_rpm] doc_files = doc/TODO doc/index.html dtd/project.dtd examples/project.html examples/project.dtd packager = Alexandre Fayolle <alexandre.fayolle(a)logilab.fr> Now, when I run setup.py bdist_rpm, this is what I get: python setup.py bdist_rpm running bdist_rpm creating build creating build/bdist.linux-i686 creating build/bdist.linux-i686/rpm creating build/bdist.linux-i686/rpm/SOURCES creating build/bdist.linux-i686/rpm/SPECS creating build/bdist.linux-i686/rpm/BUILD creating build/bdist.linux-i686/rpm/RPMS creating build/bdist.linux-i686/rpm/SRPMS writing 'build/bdist.linux-i686/rpm/SPECS/pygantt.spec' running sdist warning: sdist: manifest template 'MANIFEST.in' does not exist (using default fi le list) warning: sdist: standard file not found: should have one of README, README.txt writing manifest file 'MANIFEST' creating pygantt-0.6.0 creating pygantt-0.6.0/lib making hard links in pygantt-0.6.0... hard linking pygantt.py -> pygantt-0.6.0 hard linking setup.cfg -> pygantt-0.6.0 hard linking setup.py -> pygantt-0.6.0 hard linking lib/HTMLRenderer.py -> pygantt-0.6.0/lib hard linking lib/Task.py -> pygantt-0.6.0/lib hard linking lib/__init__.py -> pygantt-0.6.0/lib hard linking lib/common.py -> pygantt-0.6.0/lib creating dist tar -cf dist/pygantt-0.6.0.tar pygantt-0.6.0 gzip -f9 dist/pygantt-0.6.0.tar removing 'pygantt-0.6.0' (and everything under it) copying dist/pygantt-0.6.0.tar.gz -> build/bdist.linux-i686/rpm/SOURCES building RPMs <I'll skip the things that go without problem> Processing files: pygantt-0.6.0-1 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.33791 + umask 022 + cd /home/alf/pygantt/build/bdist.linux-i686/rpm/BUILD + cd pygantt-0.6.0 + DOCDIR=/var/tmp/pygantt-buildroot/usr/doc/pygantt-0.6.0 + export DOCDIR + rm -rf /var/tmp/pygantt-buildroot/usr/doc/pygantt-0.6.0 + /bin/mkdir -p /var/tmp/pygantt-buildroot/usr/doc/pygantt-0.6.0 + cp -pr doc/TODO doc/index.html dtd/project.dtd examples/project.html examples/ project.dtd /var/tmp/pygantt-buildroot/usr/doc/pygantt-0.6.0 cp: doc/TODO: No such file or directory cp: doc/index.html: No such file or directory cp: dtd/project.dtd: No such file or directory cp: examples/project.html: No such file or directory cp: examples/project.dtd: No such file or directory Bad exit status from /var/tmp/rpm-tmp.33791 (%doc) <snip the end of the output> What am I missing? Is it forbidden to put subdirectories in --doc-files? Thanks for your support. Alexandre Fayolle -- http://www.logilab.com Narval is the first software agent available as free software (GPL). LOGILAB, Paris (France).

1 0