On 11/16/05, felix <[EMAIL PROTECTED]> wrote:
>
> and note that the PYTHON_PATH should specify the *parent* directory of
> your project.
>
> I just tried it again with DJANGO_SETTINGS_MODULE **not** exported and
> passing in django-admin.py --settings=myproject.settings
>
> that does not work,
and note that the PYTHON_PATH should specify the *parent* directory of
your project.
I just tried it again with DJANGO_SETTINGS_MODULE **not** exported and
passing in django-admin.py --settings=myproject.settings
that does not work, you have to set/export DJANGO_SETTINGS_MODULE
thanks
On Thu, 10 Nov 2005 12:16:47 -0500 Waylan Limberg wrote:
>
> On 11/10/05, James Bennett <[EMAIL PROTECTED]> wrote:
> >
> > On 11/10/05, felix <[EMAIL PROTECTED]> wrote:
> > > do this:
> > > export DJANGO_SETTINGS_MODULE=myproject.settings
> >
> > Yeah, that's mentioned in the documentation.
On 11/10/05, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> I still don't have it working for me, and I did the export
> DJANGO_SETTINGS_MODULE=myproject.settings thing. Whats the best way to
> see what your PYTHONPATH is set to and change it? Maybe something is
> wrong there. (I'm on Debian with
On 11/10/05, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 11/10/05, felix <[EMAIL PROTECTED]> wrote:
> > do this:
> > export DJANGO_SETTINGS_MODULE=myproject.settings
>
> Yeah, that's mentioned in the documentation. Perhaps what was
> happening was that you'd changed a .bash_profile or .bashrc
On 11/10/05, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 11/10/05, felix <[EMAIL PROTECTED]> wrote:
> > do this:
> > export DJANGO_SETTINGS_MODULE=myproject.settings
>
> Yeah, that's mentioned in the documentation. Perhaps what was
> happening was that you'd changed a .bash_profile or .bashrc
On 11/10/05, felix <[EMAIL PROTECTED]> wrote:
> do this:
> export DJANGO_SETTINGS_MODULE=myproject.settings
Yeah, that's mentioned in the documentation. Perhaps what was
happening was that you'd changed a .bash_profile or .bashrc file to
set your DJANGO_SETTINGS_MODULE and PYTHONPATH, and then
ok mine is working now.
do this:
export DJANGO_SETTINGS_MODULE=myproject.settings
and thereafter all the django-admin.py commands work correctly.
> On 11/7/05, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> > On 11/7/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> > > Django isn't finding your settings.py file. It's falling back to
> > > "postgresql" because that's the default fallback (according to the
> > > file
On 11/7/05, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> On 11/7/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> >
> > Django isn't finding your settings.py file. It's falling back to
> > "postgresql" because that's the default fallback (according to the
> > file
I am using FCGI on my host and I find that I am often required to
"pkill python" in order to make certain types of changes actually show
up. Annoying, but not a problem for my users. Just a thought...
On 11/7/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 11/6/05, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> > I'v gone through the first toturial before on another box no problem,
> > but on this machine I can't seem to get it to work. After setting the
> > database conection info in
On 11/6/05, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> I'v gone through the first toturial before on another box no problem,
> but on this machine I can't seem to get it to work. After setting the
> database conection info in myproject/settings.py I try to run
> 'django-admin.py init
I got this problem too. when i use postgresql.
but I solved it . when I drop old db and
create new db set owner=postgres , tablespace= pg_default and public .
maybe you are the same problem. holp to help you.
Waylan Limberg wrote:
> I'v gone through the first toturial before on another box no
You might try executing python with the -v option
El lun, 07-11-2005 a las 15:21 +0800, limodou escribió:
> > I just noticed that the line breaks (in the comments) on the first two
> > lines were actual line breaks, not just wrapping text. I fixed that,
> > but still no go. The last two lines
> I just noticed that the line breaks (in the comments) on the first two
> lines were actual line breaks, not just wrapping text. I fixed that,
> but still no go. The last two lines are definitely wrapping text.
>
> It's still telling me the DATABASE_ENGINE is set to 'postgresql'
>
maybe there
> DATABASE_ENGINE = 'mysql' # 'postgresql', 'mysql', 'sqlite3' or
> 'ado_mssql'.
> DATABASE_NAME = 'djangodb' # Or path to database file if
> using sqlite3.
> DATABASE_USER = 'username' # Not used with sqlite3.
> DATABASE_PASSWORD = 'pass' # Not used with sqlite3.
On 11/7/05, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
>
> On Monday 07 Nov 2005 11:40 am, Waylan Limberg wrote:
> > and there is definitely only one 'myproject' directory on the system
> > and only one setting.py file in that dir.
>
> could you paste the database part of your settings.py file
On 11/7/05, limodou <[EMAIL PROTECTED]> wrote:
>
> 2005/11/7, Waylan Limberg <[EMAIL PROTECTED]>:
> >
> > I'v gone through the first toturial before on another box no problem,
> > but on this machine I can't seem to get it to work. After setting the
> > database conection info in
On Monday 07 Nov 2005 11:40 am, Waylan Limberg wrote:
> and there is definitely only one 'myproject' directory on the system
> and only one setting.py file in that dir.
could you paste the database part of your settings.py file somewhere?
--
regards
kg
http://www.livejournal.com/users/lawgon
2005/11/7, Waylan Limberg <[EMAIL PROTECTED]>:
>
> I'v gone through the first toturial before on another box no problem,
> but on this machine I can't seem to get it to work. After setting the
> database conection info in myproject/settings.py I try to run
> 'django-admin.py init
I'v gone through the first toturial before on another box no problem,
but on this machine I can't seem to get it to work. After setting the
database conection info in myproject/settings.py I try to run
'django-admin.py init --settings=myproject.settings'. I get the
following error:
Error: The
22 matches
Mail list logo
