On 2/24/07, Andrew Straw <str...@as...> wrote: > Robert Kern wrote: > > IPython does something similar and possibly better. > > > > http://ipython.scipy.org/svn/ipython/ipython/trunk/setupext/install_data_ext.py > > > From a quick look at the code, it's hard to determine whether this new > distutils command (install_data_ext) can handle installation to a nested > directory structure. Can it? If it can, there's still the question of > whether we want to continue rolling our own solution or simply using > Python >= 2.4's standard "package_data". I think it does, but you should actually ask someone who knows about ipython :) I say 'I think' from reading setup.py, where this code is invoked: datafiles = [('data', docdirbase, docfiles), ('data', os.path.join(docdirbase, 'examples'), examfiles), ('data', os.path.join(docdirbase, 'manual'), manfiles), ('data', manpagebase, manpages), ('lib', 'IPython/UserConfig', cfgfiles)] [...] and then the setup() call contains: cmdclass = {'install_data': install_data_ext}, data_files = datafiles, So it certainly looks like it works fine for copying things like the example files and the html manual (which is nested, below doc/manual). This code was actually given to me years ago, by some kind soul who cringed at the horrid hacks I had in place to achieve the goal. It has never been modified and has served us well for years, so feel free to grab it if it happens to be useful to mpl. It's a tiny bit of code, so if it gets you out of a bind, I'd say just use it. It does work fine with python 2.3, if that's one of your goals. Cheers, f