Re: [cclib-devel] cclib debs

[Karol L. <kar...@kn...>]

On Monday 04 June 2007 13:17, Noel O'Boyle wrote:
> > > > 4. A testing issue has occured to me while testing the packages. It
> > > > should be possible to run the test suite we have from the Python
> > > > interpreter. I think that adding this is a good idea for the next
> > > > release, together with an option in setup.py to install the test
> > > > scripts and data files. What are you poinions on this?
> > >
> > > Well, I think you should see how this is done for other packages
> > > first. The general recommendation is that "python setup.py test"
> > > should run the tests. But I think you are suggesting something beyond
> > > this.
> >
> > Sure, "python setup.py test" is the standard. I was thinking of something
> > like numpy.test(), which runs the NumPy test suite for the installed
> > package. What are your feelings about something like this? For cclib,
> > that means copying the data files during installation
>
> Sure, go for it - we can probably standardise the tests a bit more
> too. I'm not sure what you mean regarding the data files. They are
> currently installed by default, right?
I don't think so, at least not with my machine:
langner@slim:~$ ls -l apps/python/lib/python2.5/site-packages/cclib
total 24K
drwxr-xr-x 2 langner langner 4.0K 2007-06-05 15:22 bridge
-rw-r--r-- 1 langner langner  247 2007-05-20 01:03 __init__.py
-rw-r--r-- 1 langner langner  479 2007-06-05 15:22 __init__.pyc
drwxr-xr-x 2 langner langner 4.0K 2007-06-05 15:22 method
drwxr-xr-x 2 langner langner 4.0K 2007-06-05 15:22 parser
drwxr-xr-x 2 langner langner 4.0K 2007-06-05 15:22 progress

Did you mean for them to be installed?

> > > I'd actually be more
> > > interested in getting a Python egg together for
> > > ez_setup.py/setuptools. I don't know what the current situation is
> > > with eggs and Debian though.
> >
> > Well, if you have setuptools installed and put this in setup.py:
> > try:
> >     from setuptools import setup
> > except ImportError:
> >     from distutils.core import setup
> > and run "python setup.py bdist_egg", you get ann egg that should be ready
> > to go (I'm attaching it).
>
> OK, so that was easy! Go ahead and commit it, but please make sure
> that our regular distributions are unchanged by this.

OK, I haven't changed any keywords to the call to setup() for now. You can 
build the egg now, though. 

-- 
written by Karol Langner
Tue Jun  5 15:37:20 CEST 2007