Mailman 3 May 2002 - 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

updated SF patch
by Jeremy Hylton 06 Jun '02

06 Jun '02

I've updated my patch "make setup.py less chatty by default." http://sourceforge.net/tracker/?func=detail&atid=305470&aid=504889&group_id… I've attached a new patch that uses a global log module. (The added file, log.py, is a separate attachment to this patch submission.) The patch is incomplete, as it removes the announce() method of several objects. I haven't bothered to replace all the calls to announce in the commands; that needs to be done before this patch can be accepted, but it's too tedious for today :-). The new approach is to eliminate all uses of verbose except one on the Distriubtion object that can be controlled by -v and -q arguments. The value of Distribution.verbose is used to set a logging threshold, stored in a global variable in the log module. All code that wants to print a message calls log.method(). The default verbosity is 1, which skips messages that say "skipping ...". It does print any activity actually performed, like calling a C compiler. I'm expect more thought needs to be put into the level that each message is logged at. Jeremy

5 13

Skipping compilation of some .py files on "install"?
by Barry A. Warsaw 01 Jun '02

01 Jun '02

The email package has two files to help it maintain compatibility with Python 2.1 and Python 2.2+. There's a _compat21.py and a _compat22.py that contains tricky bits that are different between the two Python versions. Other code that needs something out of these modules, first tries to import _compat22.py, wrapping this import so that if errors occur, it backs down to _compat21.py. The problem comes when I do "python2.1 setup.py install", which tries to bytecompile all the .py files. Naturally Python 2.1 won't be able to compile _compat22.py and indeed you get a SyntaxError. Is there a way -- in my setup.py -- that I can first detected which Python version I'm using (should be easy), and then skip byte compilation of _compat22.py when I find I'm using Python 2.1? Thanks, -Barry

2 2

customizing verbose and dry_run per command
by Jeremy Hylton 31 May '02

31 May '02

The Command class supports per-command customization of the verbose and dry_run options using a rather hairy __getattr__() trick. I was wondering if this feature is actually used by anyone. I can't find any examples of its use in the distutils package itself. I ask because I was looking at the previously discussed overhaul of how distutils produces output. I was hoping to remove the self.verbose attribute from the several classes that have it. The simplest way to remove it would disable this feature. Would that be a problem? Jeremy

1 0

Mingw32 section of 'Installing' manual
by Andrew Kuchling 30 May '02

30 May '02

There's a section on building extensions for Cygwin/MinGW32. http://www.python.org/dev/doc/devel/inst/tweak-flags.html#SECTION0006220000… Is all the material in this section still up-to-date and relevant? --amk

1 0

Documentation: MacOS comments needed
by Andrew Kuchling 24 May '02

24 May '02

In the "Installing Python Modules" document, most of the remaining XXX comments are all for the MacOS. I have no access to MacOS X at this point, so can someone please comment on these? 1) Excerpt: You can find out what your Python installation uses for \filevar{prefix} and \filevar{exec-prefix} by running Python in interactive mode and typing a few simple commands. Under \UNIX, just type \code{python} at the shell prompt. Under Windows, choose \menuselection{Start \sub Programs \sub Python 2.1 \sub Python (command line)}. Under Mac OS, \XXX{???}. 2) Does the section "Alternate installation: Mac OS 9" need changes for OS X? Should this section be kept in the docs for Python 2.3, or is MacOS 9 now irrelevant? 3) Excerpt: (And of course, on systems that don't have environment variables, such as Mac OS (\XXX{true?}), the configuration variables supplied by the Distutils are the only ones you can use.) --amk

1 0

Eros e soldi:guadagna con internet 0,08 euro a clic
by lolita 24 May '02

24 May '02

sono lolita, voglio presentarti il mio nuovo sito affiliazione gratuita con guadagni immediati: erotismo, chat,loghi e sonerie etc, etc, l'unico sito che paga cos� tanto 0,08 euro a clic ............................guarda bene la pg di affiliazione............................e buon divertimento. visita il sito: http://members.xoom.it/marym1976 http://members.xoom.it/marym1976 http://members.xoom.it/marym1976

1 0

Including non-Python files in site-packages/application directory
by Andy Todd 10 May '02

10 May '02

All, In the latest version of PythonCard we need to include a configuration file with the application code. What this means is that we would like to include a file called stc-styles.cfg in our package and when someone does an install it needs to end up in /usr/lib/python2.2/site-packages/PythonCard (or C:\Python\Lib\site-packages\PythonCard on Windows). I can get the file included in the MANIFEST and thus included in the zip and tar.gz files, but when I run "python setup.py install" the 'build' function only copies files with a .py extension. Is there any way to augment this? I'm open to any suggestions short of re-writing distutils ;-) Regards, Andy -- ---------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com

3 3

py_modules AND packages?
by Thomas Heller 08 May '02

08 May '02

Why is it not allowed to install py_modules AND packages in the same setup-script? I have a distribution where an extensions is installed in c:\python22\lib\site-packages\<ext.pyd>, and a package is installed in c:\python22\lib\site-packages\<packagename>. No problem so far. I want to hide the extension in a Python module, so that I can implement additional functionality in this module in Python, and convert it to C and move it into the extension later. Currently, this is not possible: error: build_py: supplying both 'packages' and 'py_modules' options is not allowed A tiny patch to build_py makes it possible (at the end of this mail), also it would be easy to write a custom build_py command which allows this. Would there be any harm, or is it simply that Greg did not think of this? Thomas *** \sf\python\dist\src\lib\distutils\command\build_py.py Thu Apr 04 23:17:31 2002 --- \python22\lib\distutils\command\build_py.py Wed May 08 18:44:39 2002 *************** *** 4,10 **** # created 1999/03/08, Greg Ward ! __revision__ = "$Id: build_py.py,v 1.37 2002/04/04 23:17:31 tim_one Exp $" import sys, string, os from types import * --- 4,10 ---- # created 1999/03/08, Greg Ward ! __revision__ = "$Id: build_py.py,v 1.34.6.1 2002/02/19 14:15:40 mwh Exp $" import sys, string, os from types import * *************** *** 96,110 **** if not self.py_modules and not self.packages: return - if self.py_modules and self.packages: - raise DistutilsOptionError, \ - "build_py: supplying both 'packages' and 'py_modules' " + \ - "options is not allowed" - # Now we're down to two cases: 'py_modules' only and 'packages' only. if self.py_modules: self.build_modules() ! else: self.build_packages() self.byte_compile(self.get_outputs(include_bytecode=0)) --- 96,105 ---- if not self.py_modules and not self.packages: return if self.py_modules: self.build_modules() ! if self.packages: self.build_packages() self.byte_compile(self.get_outputs(include_bytecode=0))

1 0

A distuilts question
by Fredrik Kant 08 May '02

08 May '02

My name is Fredrik Kant and have a question about distutils/bdist_wininst: a) Is it possible to let the use decide were to copy the files? <<Fredrik Kant.vcf>>

2 1

Documentation question
by Mark W. Alexander 06 May '02

06 May '02

Ok, I'm working on docs for bdist_pkgtool and bdist_sdux, but I'm completely TeX ignorant. I took the dist.tex file, cut out the RPM section and edited it for these packages. Now what? How do I test what the file actually produces, and how it fits in with the rest of the distutils docs? Next step, how do I submit the changes? (I assume as a patch to the doc file.) Pointers the whatever FM I'm looking for would be helpful. tia -- Mark W. Alexander slash(a)dotnetslash.net

2 1

Betreff
by Immer frischer Kaffee 06 May '02

06 May '02

1 0