Well, it's not a solution you'd use in a larger team environment, because it
causes confusion, but if you're just trying to put off the renaming issue
(which really isn't that hard - what's wrong with that solution?), you can
just create a symbolic link to the directory on your PYTHONPATH instead of
putting the actual folder there.
For example, I have a structure like:
/com/
myproj1/
app1/
app2/
app3/
pythonpath/
app3 --> ../app3
app2 --> ../app2
app1 --> ../app1
myproj1 --> ../myproj1
Now, /com/pythonpath is in my python path, so I can import anything
underneath that directory. If I decide to rename myproj1 to myproj1a, then
I'd just point the "myproj1" symlink at "myproj1a" instead. Like this:
pythonpath/
myproj1 --> ../myproj1a
So Django will still look for, and find, myproj1, but it'll point at your
renamed directory.
Hope this helps. Like I say, it's better form to just do the right thing up
front and do the renaming, but this can help in the interim.
brian
2009/9/10 Filip Gruszczyński <[email protected]>
>
> > Your choice. I prefer the first method. Changing the imports isn't
> > terribly difficult (global find and replace) for the few times the
> > project folder gets renamed.
>
> Unless of course, you are using distributed source control and want to
> have seperate repo for every larger feature. Then it gets quite messy
> ;-)
>
> So, these are the only two ways?
>
> --
> Filip Gruszczyński
>
> >
>
--
Brian K. Jones
Python Magazine http://www.pythonmagazine.com
My Blog http://www.protocolostomy.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
