Using setuptools

[Ivan Glushkov]

On 6/23/08, David Wolever <wolever at cs.toronto.edu> wrote:
> It turns out that making everything work with setuptools is very, very easy.
>
>  All it took was moving setup.py.in to setup.py, changing the import from
> 'distutils' to 'setuptools', and one or two other little things (which you
> can see if you `diff setup.py{,.in}`)
>
>  I'm having some trouble getting the patch for this to apply properly, so
> I've attached the new setup.py, and these complex instructions:
>  0) Save setup.py in the ditrack root
>  1) Remove setup.py.in and make-dist.py
>
>  I don't know how familiar you are with setuptools (please ignore this if
> you are), but basically there are three important commands:
>  setup.py install (install the package)
>  setup.py develop (install the package in develop mode, where all the
> system-wide scripts (eg, $PATH/dt-create, $PYTHON_PATH/DITrack) are small
> stubs which point to the real scripts in your development directory)
>  setup.py sdist (should do exactly the same thing as the make-dist.py)
>
>  David

Hello, David.

I've tried to use setuptools on my machine at work and it fails:

$ python setup.py install
Traceback (most recent call last):
  File "setup.py", line 3, in ?
    from setuptools import setup, find_packages
ImportError: No module named setuptools

I suppose the same situation might take place anywhere else, so i
propose not to use this module.
And thanks for the refactoring of our setup.py script! :)