Graham Dumpleton wrote:
> On Jan 8, 8:50 am, ryan k <[EMAIL PROTECTED]> wrote:
>> I used svn propset svn:external so my project (in transition to
>> another developer when I return to college) can easily use the most
>> recent version fo Django (and comment_utils, etc). How can I ensure
>> that t
On Jan 8, 8:50 am, ryan k <[EMAIL PROTECTED]> wrote:
> I used svn propset svn:external so my project (in transition to
> another developer when I return to college) can easily use the most
> recent version fo Django (and comment_utils, etc). How can I ensure
> that the project uses that django mod
Ok thank you for your responses. I would try this out but not at the
office now... what about __init__.py in the project's root directory?
Right now I am trying this all on the Django development server. So
let's say on my production server I have /home/ryan/projects/llcom/
trunk/lib (all svn:exte
On Jan 7, 4:42 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Putting that in settings.py is too late, since by the thing that reads
> settings.py is Django itself, so it's already been imported. You have to
> modify your Python import path *before* anything Django-related is
> imported.
He'
On Mon, 2008-01-07 at 13:50 -0800, ryan k wrote:
> I used svn propset svn:external so my project (in transition to
> another developer when I return to college) can easily use the most
> recent version fo Django (and comment_utils, etc). How can I ensure
> that the project uses that django module
I used svn propset svn:external so my project (in transition to
another developer when I return to college) can easily use the most
recent version fo Django (and comment_utils, etc). How can I ensure
that the project uses that django module instead of the one found
on /.../python2.X/site-packages
6 matches
Mail list logo
