There seems to be an error on the packaging that causes the skeleton
directory not to be copied over correctly.

I made that original change based on a suggestion that has since backfired
so I need to rethink how to make sure it gets consistently copied over.

The issue is that your satchmo/projects/skeleton directory can't be located.
If you copy it over to the same location as your Satchmo site package
install, it should pick it up and copy it over.

I'll try to work on a work around to make this a bit more robust.


On Tue, Nov 10, 2009 at 12:57 PM, Mark Ferguson <>wrote:

> Hi,
> This is day 1 for me with satchmo, so apologises if this is newbie
> finger trouble or something but I'm following the quickstart guide up
> to the point where I run:
> > python /usr/local/bin/
> Creating the Satchmo Application
> Traceback (most recent call last):
>  File "/usr/local/bin/", line 7, in <module>
>    execfile(__file__)
>  File "/root/satchmo/docs/src/satchmo/scripts/", line
> 108, in <module>
>    create_satchmo_site(opts.site_name)
>  File "/root/satchmo/docs/src/satchmo/scripts/", line
> 47, in create_satchmo_site
>    import satchmo_skeleton
> ImportError: No module named satchmo_skeleton
> and now I'm a but stuck. I've seen a couple of other posts about this
> but I can't work out if there is a solution to my problem, or if they
> are describing some other problem.
> Actually, I'm deviating from the quickstart as it says:
> python
> but that doesn't work either. I'm assuming that this is an error in
> the documentation but maybe this is root of my problem! Not got enough
> experience yet to determine if this is the case or not.
> Any pointers would be greatly appreciated.
> >

You received this message because you are subscribed to the Google Groups 
"Satchmo users" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to