On Thu, Jan 24, 2013 at 7:38 PM, Tomas Neme wrote:
> just to clarify:
>
Whoa, that really helps clarify the setup!!! Very helpful! Thank you Tomas!!!
Until we can convert to virtual envs, your suggested solution(s) and
fixes should make me sleep easier at night.
Have an
Hi Tomas! A million thanks for you help!
On Thu, Jan 24, 2013 at 7:34 PM, Tomas Neme wrote:
> really, it should be your SHORT term goal.
Without airing our dirty laundry, I can't argue with that. I will push
a little harder to get us to convert our projects to envs sooner
just to clarify:
somewhere else, not a subdir of any of your projects/
|
---FOOAPP/
|
---templates/
|
---fooapp/
|
--mytemplate.html
projectA/
|
--settings.py
|
--urls.py
|
--templates/
|
> > Use virtualenvs. That's basic for any serious python development
> > you'll want to do.
>
> Totally agree. Setting up virtualenv's are our long term goal.
really, it should be your SHORT term goal.
As for your problem, you can't expect to install FOOAPP in two
different directories on the
Hi Tomas! Thank you for your reply, I really appreciate it. :)
On Thu, Jan 24, 2013 at 6:12 PM, Tomas Neme wrote:
> Use virtualenvs. That's basic for any serious python development
> you'll want to do.
Totally agree. Setting up virtualenv's are our long term goal.
>
Use virtualenvs. That's basic for any serious python development
you'll want to do.
Besides that, you might add DjangoProjectA to sys.path on ProjectA
(and add DjangoProjectB to sys.path on ProjectB) in their respective
manage.py files.
On the other hand, why does pip install -e install it under
Noob alert! :D
I work on a server where we have multiple Django projects that all
share one Django installation.
Each project has it's own subdomain.
At this time, we aren't using virtual envs.
Situation:
1. I built a basic application (let's call it FOOAPP) inside of
DjangoProjectA; after
7 matches
Mail list logo