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
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
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
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
Three cheers for distutils 0.1!
Unfortunately it fails to install itself on my NT box.
D:\TEMP\Distutils-0.1>python setup.py -v install
running install
running build
running build_py
not copying distutils\ccompiler.py (output up-to-date)
not copying distutils\core.py (output up-to-date)
not copying distutils\errors.py (output up-to-date)
not copying distutils\fancy_getopt.py (output up-to-date)
not copying distutils\msvccompiler.py (output up-to-date)
not copying distutils\spawn.py (output up-to-date)
not copying distutils\sysconfig.py (output up-to-date)
not copying distutils\text_file.py (output up-to-date)
not copying distutils\unixccompiler.py (output up-to-date)
not copying distutils\util.py (output up-to-date)
not copying distutils\version.py (output up-to-date)
not copying distutils\__init__.py (output up-to-date)
not copying distutils\command\build.py (output up-to-date)
not copying distutils\command\build_ext.py (output up-to-date)
not copying distutils\command\build_py.py (output up-to-date)
not copying distutils\command\dist.py (output up-to-date)
not copying distutils\command\install.py (output up-to-date)
not copying distutils\command\install_ext.py (output up-to-date)
not copying distutils\command\install_py.py (output up-to-date)
not copying distutils\command\__init__.py (output up-to-date)
running install_py
creating D:\Python1.5.2
Traceback (innermost last):
File "setup.py", line 22, in ?
packages = ['distutils', 'distutils.command'],
File "distutils\core.py", line 87, in setup
dist.run_commands ()
File "distutils\core.py", line 377, in run_commands
self.run_command (cmd)
File "distutils\core.py", line 426, in run_command
cmd_obj.run ()
File "distutils\command\install.py", line 287, in run
self.run_peer ('install_py')
File "distutils\core.py", line 710, in run_peer
self.distribution.run_command (command)
File "distutils\core.py", line 426, in run_command
cmd_obj.run ()
File "distutils\command\install_py.py", line 51, in run
outfiles = self.copy_tree (self.build_dir, self.install_dir)
File "distutils\core.py", line 773, in copy_tree
self.distribution.dry_run)
File "distutils\util.py", line 318, in copy_tree
mkpath (dst, verbose=verbose)
File "distutils\util.py", line 74, in mkpath
raise DistutilsFileError, "%s: %s" % (head, errstr)
distutils.errors.DistutilsFileError: D:\Python1.5.2: File exists
To fix this I changed line 317 of distutils/util.py to:
if not dry_run and not os.path.exists(os.path.normpath(dst)):
This checks to see if the destination directory already exists before
creating it. Note: I had to use normpath since for me dst was
'D:\\Python1.5.2\\' which os.path.exists claims doesn't exist, while
'D:\\Python1.5.2' does exist.
-Amos
Python Module Distribution Utilities
release 0.1
September 29, 1999
The Python Module Distribution Utilities, or Distutils for short, are a
collection of modules that aid in the development, distribution, and
installation of Python modules. (It is intended that ultimately the
Distutils will grow up into a system for distributing and installing
whole Python applications, but for now their scope is limited to module
distributions.)
The Distutils will be a standard part of Python 1.6. This release is
intended to provide a wider audience an early opportunity to try out the
system, improve its portability, shake out the bugs, make suggestions,
and so forth. Do not expect perfection: if you're trying out this
release, it should be because you want to help debug and develop, not
because you need a stable, working system immediately.
You can download the Distutils from the Distutils SIG home page:
http://www.python.org/sigs/distutils-sig/
Any feedback, comments, bug reports, success reports, etc. should be
reported to the Distutils SIG at
distutils-sig(a)python.org
If you're not yet a member of this mailing list, you can join at
http://www.python.org/mailman/listinfo/distutils-sig
Reports of minor bugs (patches are especially welcome!) can be sent
directly to me (Greg Ward) at gward(a)python.net. Anything that expects a
longer response than "Thanks for the bug report/fix!" should be directed
to the SIG.
Fred,
I'm all for a Python-only approach. As for avoiding YASP, oye, tell me about
it. We have sooo many for our build environment, it's just a mess. I just
wanted to make sure people didn't take away the message "there is no free
find replacment for Win32".
-Perry
-----Original Message-----
From: Fred L. Drake, Jr. <fdrake(a)acm.org>
To: Perry Stoll <pas(a)scansoft.com>
Cc: distutils-sig(a)python.org <distutils-sig(a)python.org>
Date: Tuesday, September 28, 1999 9:14 AM
Subject: Re: [Distutils] The "dist" command
>
>Perry Stoll writes:
> > Ignoring the fact that Greg was being facetious (I hope...). There is a
free
> > replacement for Win32 called, oddly enough, find. From the cygnus win32
GNU
> > utilties:
> > http://sourceware.cygnus.com/cygwin/
>
>Perry,
> Actually, I was already aware of that, and the MKS Toolkit as well
>(which includes a non-free version of find). However, these are both
>third-party addons, even if one is free. Since the use of find in
>this case is quite simple, I think implementing a "manifest" command
>in distutils would be worth the 15-20 lines of code it would take.
> I'd hate for us to recommend users to go install YASP ("yet another
>software package") just to be able to get a list of files and
>directories!
>
Greg wrote:
<braindump>
Possible modes of operation:
- require an explicit manifest that lists every single file (presumably
along with a way to auto-generate the manifest)
- require an explicit manifest, but allow it to have globs or filename
patterns of some kind (and also have auto-generation)
- allow an explict manifest, but automatically augment it at runtime
with the source files mentioned in 'packages', 'py_modules', and
'ext_modules' (and any other such things that might come along)
Since you can't possibly anticipate the preferences of every sicko out
there, I'd suggest a 2 phase approach. Use specifiers / filters to create
an explicit manifest. Let the programmer edit the manifest, then go on
to phase 2.
- Gordon
-----Original Message-----
From: Fred L. Drake, Jr. <fdrake(a)acm.org>
>Greg Ward writes:
> > explictly, you're welcome to do so! If you want automated help in doing
> > so, may I suggest the 'find(1)' command? >smirk<
>
> I don't think there's any equivalent for Windows without buying 3rd
>party addons (not an acceptable alternative
Fred,
Ignoring the fact that Greg was being facetious (I hope...). There is a free
replacement for Win32 called, oddly enough, find. From the cygnus win32 GNU
utilties:
http://sourceware.cygnus.com/cygwin/
Makes a unix-weenie feel right at home on win32.
-Perry
