this was for me also a slight trick to learn. I got more from blog posts
than the docs
(and I love the django docs)
the trick is that your PYTHONPATH (and don't forget the python path of your
deployment server)
should point to the dir above your project dir and the dir above your apps
dir.
I
On Tue, 2009-01-13 at 08:53 -0800, dahpgjgamgan wrote:
[...]
> > People experienced in Python realise that import statements are
> > flexible, so what's written in the tutorial is only a guide. People
> > needing to follow every line of code in the tutorial and just learning
> > Python don't need
On Jan 13, 1:51 am, Malcolm Tredinnick
wrote:
> [...]
>
> Look, if you aren't going to be moving the applications around, the
> imports in the tutorial aren't horrible. It's the beginner's tutorial.
That's a big if, regarding that tutorial does stress decoupling
On Sun, 2009-01-11 at 16:53 -0800, Greg Aumann wrote:
[...]
> I am wondering why the tutorial teaches this bad practice when there
> is so much emphasis in Django on reusable apps.
When you could instead be wondering if it really is truly bad practice
or just alternative practice and a
On Jan 12, 5:41 am, dahpgjgamgan wrote:
> In the 4-part tutorial on Django's main site, there's a lot of advice
> on how to decouple apps and projects, but when I look at the import
> statements in most of the tutorial's files, it's always "from
> projectname.appname
5 matches
Mail list logo