Not a PATH issue, but a PYTHONPATH issue.
Run "python manage.py shell" and try to import 'messages.'
I suspect it's not where you think it is, or its location is not on your
PYTHONPATH.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To pos
Ya, it is probably a path issue. It is set as this by the way -->
['',
'/usr/lib64/python2.4/site-packages/MySQL_python-1.2.3c1-py2.4-linux-x86_64.egg',
'/usr/lib64/python24.zip', '/usr/lib64/python2.4',
'/usr/lib64/python2.4/plat-linux2', '/usr/lib64/python2.4/lib-tk',
'/usr/lib64/python2.4/lib-d
Also can I assume, regarding the above question above, that "messages" is
the last thing Django is processing since it is at the
bottom of the list in installed apps? I.e. If I fix the messages error it
might work?
INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
Check your PYTHONPATH. Perhaps it's not set right on the CentOS machine.
The Linux distro shouldn't make a difference, nor should the presence of
Cpanel or MySQL.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send ema
Hey Gang, I have a Django project built on a Debian server at home using http://djangobb.org";>DjangoBB.
It is working on the Debain OS but I am having huge problems on the Centos
server. This seams to be the farthest I can go with it. -->
#-->python manage.py syncdb
Error: N
it is an optin when that is shown in the command prompt along with
sqlite 3 ad the others. Thank you for clearing that up tho I will look
at sqlite 3
On Jun 13, 10:37 pm, Russell Keith-Magee
wrote:
> On Mon, Jun 14, 2010 at 10:22 AM, JRMAbock wrote:
> > well ive actually tried setting it to djan
On Mon, Jun 14, 2010 at 10:22 AM, JRMAbock wrote:
> well ive actually tried setting it to django.contrib.backends.dummy
> and it says the same thing.
Why did you try to set it to dummy? The comment in the settings file says:
# Add 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracl
and also, in the code the error message shows up for many different
erros that are told to display the improperly configured message
On Jun 13, 10:22 pm, JRMAbock wrote:
> well ive actually tried setting it to django.contrib.backends.dummy
> and it says the same thing.
>
> On Jun 13, 9:22 pm, raj
well ive actually tried setting it to django.contrib.backends.dummy
and it says the same thing.
On Jun 13, 9:22 pm, raj wrote:
> The problem is obvious, right? Which comment says you to leave the
> ENGINE as blank? set it to the db you want, say, sqlite3.
>
> Rajeesh.
--
You received this messa
The problem is obvious, right? Which comment says you to leave the
ENGINE as blank? set it to the db you want, say, sqlite3.
Rajeesh.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googl
when I try to set up my database using the dummy it always gives me an
error saying:
django.core.exceptions.improperlyconfigured: you havent set the
database ENGINE setting yet.
I have followed the tutorial correctley and also left the ENGINE area
blank as the comment said in order to tel the syn
Hi Selena,
To avoid this problem and make your app relocable, you should not use
hard coded paths.
Here's what I use on my projects:
from os import path
rel = lambda *x: path.join(path.abspath(path.dirname(__file__)), *x)
DATABASE_NAME = rel('dev.db')
MEDIA_ROOT = rel('media')
TEMPLATE_DIRS = (
hello everyone
i apologize for being so quick on asking for help, before i double
checked my paths and local settings - which i thought i did but
i have just realized that i had the old computer's name SSAVIC in the
database_name path - and that was the only reason this was not
working! thank
sure, here it is:
# Django settings for mysite project.
DEBUG = True
TEMPLATE_DEBUG = DEBUG
ADMINS = ('selena', 'idealnig...@gmail.com'
# ('Your Name', 'your_em...@domain.com'),
)
MANAGERS = ADMINS
DATABASE_ENGINE = 'sqlite3' # 'postgresql_psycopg2',
'postgresql', 'mysql', 'sqli
2009/10/18 selena
>
> Hello
> hey michael
> I have been experiencing this problem since I installed my brand new
> Ubuntu Karmic with python in version 2.6 The project I am working on
> was working under python2.5 in my old Gentoo and still works (at least
> the python manage.py syncdb command do
Hello
hey michael
I have been experiencing this problem since I installed my brand new
Ubuntu Karmic with python in version 2.6 The project I am working on
was working under python2.5 in my old Gentoo and still works (at least
the python manage.py syncdb command does) on a server which is also
run
You might want to check this out as a more up to date intro:
http://docs.djangoproject.com/en/dev/intro/tutorial01/#intro-tutorial01
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to thi
On Mon, Sep 14, 2009 at 1:38 PM, Randy Barlow wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> about2flip declared:
> > File "E:\djproj\ifriends\..\ifriends\People\models.py", line 8
> > def_str_(self):
> > ^
> > SyntaxError: invalid syntax
>
> Looks like you
On Mon, Sep 14, 2009 at 1:38 PM, Joshua Russo wrote:
> On Mon, Sep 14, 2009 at 1:27 PM, about2flip wrote:
>
>>
>> Hi:
>>
>> I am using learn django in 24 hours and I am following this example on
>> models.
>>
>> from django.db import models
>>
>> class Person(models.Model):
>>name = model
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
about2flip declared:
> File "E:\djproj\ifriends\..\ifriends\People\models.py", line 8
> def_str_(self):
> ^
> SyntaxError: invalid syntax
Looks like you are missing a space between def and __str__(self).
Should be:
def __str_
On Mon, Sep 14, 2009 at 1:27 PM, about2flip wrote:
>
> Hi:
>
> I am using learn django in 24 hours and I am following this example on
> models.
>
> from django.db import models
>
> class Person(models.Model):
>name = models.CharField('name', maxlength=200)
>email = models.EmailFie
On Sep 14, 3:27 pm, about2flip wrote:
> Hi:
>
> I am using learn django in 24 hours and I am following this example on
> models.
> File "E:\djproj\ifriends\..\ifriends\People\models.py", line 8
> def_str_(self):
> ^
> SyntaxError: invalid syntax
>
> E:\djproj\ifriends>
>
Hi:
I am using learn django in 24 hours and I am following this example on
models.
from django.db import models
class Person(models.Model):
name = models.CharField('name', maxlength=200)
email = models.EmailField('Email', blank=True)
headshots = models.ImageField(upload_
it works now. thanks Kai.
On Apr 29, 3:54 pm, Kai Kuehne wrote:
> No TOFU please.
>
> On Thu, Apr 30, 2009 at 12:49 AM, David wrote:
> > sorry i can not find a database that table
> > 'auth_permission' belongs to. any more hints what i should do?
>
> Did you FLUSH PRIVILEGES?
--~--~-~-
No TOFU please.
On Thu, Apr 30, 2009 at 12:49 AM, David wrote:
> sorry i can not find a database that table
> 'auth_permission' belongs to. any more hints what i should do?
Did you FLUSH PRIVILEGES?
--~--~-~--~~~---~--~~
You received this message because you are
sorry i can not find a database that table
'auth_permission' belongs to. any more hints what i should do?
thanks so much.
On Apr 29, 3:35 pm, David wrote:
> i see. i should grant priviliges on the database that table
> 'auth_permission' belongs to. let me do it.
>
> thanks.
>
> On Apr 29, 3:3
i see. i should grant priviliges on the database that table
'auth_permission' belongs to. let me do it.
thanks.
On Apr 29, 3:32 pm, David wrote:
> mysql> show grants;
> +--
> +
> | Gra
mysql> show grants;
+--
+
| Grants for
da...@localhost
|
+--
+
| GRANT USAGE ON *
Hi,
On Thu, Apr 30, 2009 at 12:17 AM, David wrote:
> [error message]
> anybody knows how to fix it?
Grant CREATE permission for your user on that database.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django u
Hi,
i followed django tutorial part 1 to learn django, however i met
following error when i used "python manage.py syncdb".
da...@django:~/mysite$ python manage.py syncdb
Creating table auth_permission
Traceback (most recent call last):
File "manage.py", line 11, in
execute_manager(settin
On 9/20/07, johnny <[EMAIL PROTECTED]> wrote:
>
> this error is due to auto incremented primary key. you can't have
> empty fixture file.
The test suite doesn't currently check serialization of AutoFields.
However, this would be a valuable test to add. Please open a ticket
for this issue; if you
this error is due to auto incremented primary key. you can't have
empty fixture file.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegr
class Category(models.Model):
id = models.AutoField(primary_key=True)
parent_id = models.IntegerField()
name = models.CharField(maxlength=200)
Problem installing fixture 'c:\mysite\apps\category\fixtures
\initial_data.yaml': 'NoneType' object has no attribute 'anchor'
What is the iss
Kenneth Gonsalves wrote:
> On 08-Aug-06, at 7:37 PM, abe wrote:
>
> >
> > I'm sometimes creating extra models, sometimes deleting an old model,
> > and then run syncdb to update the database.
>
> if you are deleting old model, syncdb wont do it for you
>
I know, but the complaint is about an cur
On 08-Aug-06, at 7:37 PM, abe wrote:
>
> I'm sometimes creating extra models, sometimes deleting an old model,
> and then run syncdb to update the database.
if you are deleting old model, syncdb wont do it for you
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
Seth Buntin wrote:
> Are you trying to insert initial data into you db when running this
> script?
not sure exactly what yuo mean by initial data.
I'm sometimes creating extra models, sometimes deleting an old model,
and then run syncdb to update the database.
Eiso
--~--~-~--~~--
if I apply syncdb for one of my apps
./manage.py syncdb xxapp
I get the traceback below that ends with
[...]
_mysql_exceptions.IntegrityError: (1062, "Duplicate entry
'17-add_status' for key 2")
I can't find an obvious error in the database.
does anyone know what could be wrong.?
abe
Trace
Are you trying to insert initial data into you db when running this
script?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To
38 matches
Mail list logo
