setup.py's change breaks clonesatchmo.py starting from 0.9.2

Issue #1418 resolved
Former user created an issue

I downloaded 0.9.2 and installed all the dependencies and Satchmo itself. Every time I run clonesatchmo.py, I will see "Invalid skeleton directory. Path should be /path/to/satchmo/projects/skeleton". So I digged a little and think the the change in setup.py starting from 0.9.2 breaks the clone script. Starting from 0.9.2, setup.py renames skeleton to satchmo_skeleton but the clone script is still searching for the old path.

Comments (4)

  1. Hynek Cernoch
    • changed status to open

    The problem depend mainly on the installation method. (version 0.9.2 is not imporant. Nothing relevant to this problem changed in Satchmo since November 2009.)

    • The method Quick Start works good because it copies the complete repository tree without renaming.
    • The method Installation also works good because it uses the command python /home/user/src/satchmo-trunk/scripts/clonesatchmo.py (not clonesatchmo installed by setuptools on many possible unexpected locations)
    • With other installation methods (though it is not possible to find the skeleton on any path relative to the script) should be used clonesatchmo --skel=absolute/or/relative/path/to/skeleton or $HOME/relative/to/home and it also works, but tilda expansion can not be expected (~/relative/to/home). It is probably the reported problem.

    TODO: rewrite clonesatchno? Django django-admin.py startproject is not better.

  2. Log in to comment