Kevin Teague wrote:
I'm looking into why buildout would leave the pythonpath incomplete
and think it is just a buildout.cfg problem. The same site structure worked
in a non-buildout form.
Yes, this sounds like a simple library path problem. Did you provide a
setup.py for your cottagematic_com app so that Buildout could find it?
No.
Did you declare a dependency on cottagematic_com in the package list
for your buildout config?
No.
Neither of those are mentioned in any Django docs. Can a Django
project dir be considered a separate app and packaged as such?
Is that compatible with django?
It can be difficult to get Django set-up with Buildout, since the
Django tutorial doesn't follow Python packaging conventions yet.
Is django on a roadmap to do that?
In a
pinch, you could try just exporting your packages location onto
PYTHONPATH, e.g.:
export PYTHONPATH=/home/john/WEBprojects/cottagematic_bld/
(or where ever your python source tree lives)
It can't hurt much to try that...
There are some buildout django examples on the web, but very specific and
no explanation of buildout. I'll look into generating a setup.py and ask
on the django user list about that.
John
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
