Thanks to all for the examples and insight! Very helpful.
Matt
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/sITNuGB_k54J.
To post to this group, send
On Tue, Sep 11, 2012 at 4:56 PM, Matthew Woodward wrote:
> Any thoughts/pointers/admonitions/etc. are greatly appreciated.
what i typically do:
commonly, i have several projects running, each one involves more than
just one django project. maybe two django projects, more
On 09/12/12 09:56, Cal Leeming [Simplicity Media Ltd] wrote:
> Be aware, the below structure works perfectly for us
It might help if you include what your $PYTHONPATH is set to, so one
knows which directories are expected to be available for importing.
-tkc
--
You received this message
Be aware, the below structure works perfectly for us because of trial and
error from years of development, it suits the particular style/nature of
our projects, and it has been made standardized across the board. I
wouldn't recommend using the above, instead, I would recommend looking
around for
Hi all -- semi-new to Django but learning fast and enjoyed meeting a lot of
folks at DjangoCon last week! I have some basic project setup and
terminology questions I'm hoping to get some thoughts on.
Basically I'm curious as to the convention about creating a project using
virtualenv and then
5 matches
Mail list logo