message, it shows the 'normal' python path, site packages installed,
> etc. For example, I have jinja on my main installation, but not in the
> virtual environment. Yet, jinja shows up in this message as one of the site
> packages; similarly with the other python packages. Is th
I understand the importance of doing projects in virtual environments, but
I am hitting one snag.
When I have an error in django, and I get the generated webpage with an
error message, it shows the 'normal' python path, site packages installed,
etc. For example, I have jinja
On Mon, Mar 25, 2013 at 12:56 PM, Carsten Fuchs wrote:
>> !!! PONTIFICATION ALERT !!!
>> Don't do that.
>
> Uhh, about the first word, I didn't find it in any dictionary.
> Is this somehow related to pope Franziskus? ;-)
>
>From http://www.thefreedictionary.com/pontificate:
To express opinio
Hi Bill,
thank you very much for your clear and detailed reply!
All problems resolved.
Am 22.03.2013 20:52, schrieb Bill Freeman:
!!! PONTIFICATION ALERT !!!
Don't do that.
Uhh, about the first word, I didn't find it in any dictionary.
Is this somehow related to pope Franziskus? ;-)
So put
!!! PONTIFICATION ALERT !!!
Don't do that.
I believe that it has always been a goal of project structure that the
directories on the python path be either in the default python places
(/something/something/lib/python2.X/site-packages/ unless you're using a
Debian provided pytho
erns began with 'Zeiterfassung. ...'
However, with the new project layout, it seems that the correct way to
make it work is *contrary* to the description in the
IntegrationWithDjango article:
Is it right that the python path should now include the project root
directory?
On Thu, Dec 1, 2011 at 5:59 AM, Nikhil Verma wrote:
>
> Hi all,
>
> I want to add my django project directory path to PYTHONPATH. I am a newbie
> in ubuntu 11.10
> Please tell me step by step. When i do
import sys
sys.path.append(''project_directory path")
> It does append but not permanen
Do you have pip installed? If so, you can just create a setup.py
script [1] and from inside your project directory run:
pip install -e ./
I assume setuptools (easy_install) can do the same, but I'm not 100%
clear on the command.
[1] http://docs.python.org/distutils/setupscript.html
On Dec 1,
On Thursday, 1 December 2011 10:59:15 UTC, Nikhil Verma wrote:
>
>
> Hi all,
>
> I want to add my django project directory path to PYTHONPATH. I am a
> newbie in ubuntu 11.10
> Please tell me step by step. When i do
> >>>import sys
> >>>sys.path.append(''project_directory path")
> It does append
Hi all,
I want to add my django project directory path to PYTHONPATH. I am a newbie
in ubuntu 11.10
Please tell me step by step. When i do
>>>import sys
>>>sys.path.append(''project_directory path")
It does append but not permanently. I want it like whenever i do sys.path
it should show me Project
I figured out the first problem listed above. It wasn't related to
file permissions, but I want to document it here since if I hit it
someone else is likely to hit it too.
The problem was because I was writing application import statements
incorrectly. For example, I was saying:
from phone
On Wed, Sep 30, 2009 at 12:47 PM, W.P. McNeill wrote:
>
> Because this appears to be a problem with load paths, I inserted code
> at the top of phonemechart/urls.py just above the import statements to
> write out the system path.
>
> import sys
>
> f = open('/tmp/pypath', 'w')
> f.write("Path is:
uot; wrote:
> I have written a set of Django apps that works on my development
> machine but fails when I deploy it to Apache. The issue appears to be
> with the Python path that the Apache process is using, but none of the
> things I have tried have worked. I'm looking for sugge
I have written a set of Django apps that works on my development
machine but fails when I deploy it to Apache. The issue appears to be
with the Python path that the Apache process is using, but none of the
things I have tried have worked. I'm looking for suggestions as to
what I am doing
egory)
---
and then ran:
[EMAIL PROTECTED]:~/django_projects/mysite$ python manage.py syncdb
rather than..
[EMAIL PROTECTED]:~/django_projects$ python manage.py syncdb
still a bit confused though as I thought that by exporting my python
path i
/var/lib/python-support/python2.5',
'/usr/lib/python2.5/site-packages/gtk-2.0',
'/var/lib/python-support/python2.5/gtk-2.0']
On Dec 9, 12:02 pm, mangamonk <[EMAIL PROTECTED]> wrote:
> I'm working through 'practical django projects'
> on page 46, in
I'm working through 'practical django projects'
on page 46, in order to develop stanalone application, I need to add
my django 'project' to the python path. therefore..
export PYTHONPATH=/home/mark/django_projects/:$PYTHONPATH
then a little later in the tutorial after
> > The runserver stuff is a bit too magic. It puts 'root' on sys.path but
> > only long enough to import 'mysite' package root.
um, i have never experienced this behavior.
plug: http://www.wtflab.com/tech/2008/jul/01/developed-directory-structure/
--~--~-~--~~~---
ectories of all the modules you are going to
> > import in your application."
>
> > If I have a typical Django project structure:
>
> > root
> > - mysite
> > -- myapp1
> > -- myapp2
>
> > I should put root on the Python PATH, right?
>
> Yes
al Django project structure:
>
> root
> - mysite
> -- myapp1
> -- myapp2
>
> I should put root on the Python PATH, right?
Yes and if you don't always use 'mysite.' package prefix in url rules
and just say 'myapp1.', 'myapp2.' etc, then you must also
Hi,
The documentation says "The value you use for PythonPath should
include the parent directories of all the modules you are going to
import in your application."
If I have a typical Django project structure:
root
- mysite
-- myapp1
-- myapp2
I should put root on the Python PATH, r
21 matches
Mail list logo
