yes the sqlite package is installed. I installed the Django and the python,
and I test it to ensure it is there and it is.
On Mon, Jan 24, 2011 at 12:48 PM, Kimberly Harvey wrote:
> Karen,
>
> It worked after I used the mv command to move the settings.py
> settings.py.break and then did ano
Karen,
It worked after I used the mv command to move the settings.py
settings.py.break and then did another move where from settings.py.break to
settings.py, then I ran the server by using the manage.py syncdb. I do not
understand why that even worked ( I didn't want to use the settings.py.b
This might be a stupid question but did you install the sqlite package?
On Mon, Jan 24, 2011 at 9:39 AM, Kelly Nicholes wrote:
> I think I had this error too when I was cloning a repo from WebFaction
> to use on my local dev machine. I ended up having to replace
> WebFaction's manage.py with the
I think I had this error too when I was cloning a repo from WebFaction
to use on my local dev machine. I ended up having to replace
WebFaction's manage.py with the one from Django. Let me know if it
works for you! I wish I could explain why. Can't.
On Jan 23, 8:55 pm, Graham Dumpleton
wrote:
Thanks for the advice. Thanks for your help!
On Mon, Jan 24, 2011 at 12:10 AM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:
>
> our help
> On Monday, January 24, 2011 5:05:05 PM UTC+11, Kimberly wrote:
>>
>> LOL, I do have another thing I want to ask. I ran the server ( 0 errors)
>> but
On Monday, January 24, 2011 5:05:05 PM UTC+11, Kimberly wrote:
>
> LOL, I do have another thing I want to ask. I ran the server ( 0 errors)
> but when to the browser to check, http://127.0.0.1:8000/ and now it says
> it refused the connection. It said that the server may be busy or may have
>
LOL, I do have another thing I want to ask. I ran the server ( 0 errors) but
when to the browser to check, http://127.0.0.1:8000/ and now it says it
refused the connection. It said that the server may be busy or may have
network connection problem. It also said I may have an old version of the
pag
On Monday, January 24, 2011 4:39:47 PM UTC+11, Kimberly wrote:
>
> Screen:
>
> You just installed Django's auth system, which means you don't have any
> superusers defined.
>
> So it is working
>
> I do have a question... after I've used the move technique to move the
> settings.py settings
Screen:
You just installed Django's auth system, which means you don't have any
superusers defined.
So it is working
I do have a question... after I've used the move technique to move the
settings.py settings.py.broken which places all of the file of settings.py
inside the settings.py.broken
On Monday, January 24, 2011 4:25:52 PM UTC+11, Kimberly wrote:
>
> The directory I did it from was from my home directory. I've moved the
> files like you've indicated by using mv settings.py settings.py.broken.
>
> Should I go ahead and type in the command as python manage.py syncdb to see
> i
I ran the syncdb and it says it doesn't recognize the wiki module. Also,
when I moved the original file which was settings.py to settings.py.broken,
that means I have to change the formats in the manage,py and other files so
that it recognizes the settings.py.broken file, right?
On Sun, Jan 23, 20
The directory I did it from was from my home directory. I've moved the files
like you've indicated by using mv settings.py settings.py.broken.
Should I go ahead and type in the command as python manage.py syncdb to see
if it works?
On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton <
graham.dumpl
On Monday, January 24, 2011 4:10:15 PM UTC+11, Kimberly wrote:
>
>
> /home/username/wikicamp/wikicamp/settings.py --> THIS DOES NOT EXIST
>
> WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
> settings.py is there.
>
Earlier you said you got:
import settings
print set
/home/username/wikicamp/wikicamp/settings.py --> THIS DOES NOT EXIST
WHAT DOES EXIST: /home/username/wikicamp and inside that directory,
settings.py is there.
On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey wrote:
> Sorry about that, there is nothing showing for either echo $PYTHONPATH
>
Sorry about that, there is nothing showing for either echo $PYTHONPATH and
echo $DJANGO_SETTINGS_MODULE
I am currently reading your messages.
On Sun, Jan 23, 2011 at 10:55 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:
>
>
> On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wro
On Monday, January 24, 2011 3:44:59 PM UTC+11, Kimberly wrote:
>
> Please do the following and provide the output:
>
> pwd
>
> MY OUTPUT: /home/username/wikicamp
>
> Now run 'python' from the command line and do the following, providing the
> output to us:
>
> import settings
> print setti
I did not modified the manage.py file
On Sun, Jan 23, 2011 at 10:44 PM, Kimberly Harvey wrote:
> Please do the following and provide the output:
>
> pwd
>
> MY OUTPUT: /home/username/wikicamp
>
> Now run 'python' from the command line and do the following, providing the
> output to us:
>
>
Please do the following and provide the output:
pwd
MY OUTPUT: /home/username/wikicamp
Now run 'python' from the command line and do the following, providing the
output to us:
import settings
print settings.__file__
import wikicamp.settings
print wikicamp.settings.__file__
after imp
On Monday, January 24, 2011 3:18:45 PM UTC+11, Kimberly wrote:
>
> Traceback ( most recent call last):
> File "manage.py", line 11, in
> execute_manager(settings)
> File "/usr/lib/python2.5/site-
> packages/django/core/management/_init_.py", line 438, in execute manager
> Fi
The output was produced with the print __file__ and print 'DATABASES',
DATABASES at the end of the settings.py file.
On Sun, Jan 23, 2011 at 10:18 PM, Kimberly Harvey wrote:
> Traceback ( most recent call last):
> File "manage.py", line 11, in
> execute_manager(settings)
> File
Traceback ( most recent call last):
File "manage.py", line 11, in
execute_manager(settings)
File "/usr/lib/python2.5/site-
packages/django/core/management/_init_.py", line 438, in execute manager
File
"/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
37
Thank you for the advices. I've done some Python codes in the past and
recently. I already have a Python code that I will need to use to create a
Django website ( response to Steven).
(Response to Graham):
Traceback ( most recent call last):
File "manage.py", line 11, in
execute_mana
On Monday, January 24, 2011 2:55:16 PM UTC+11, Graham Dumpleton wrote:
>
> Are you saying that those two print statements you were told to add are not
> causing anything additional to be displayed on the screen when you run both
> runserver and syncdb?
>
> This is why I asked you to provide the
Just curious if you've done a python tutorial yet? It's hard to really
understand Django well unless you have at least some working knowledge of
python. You will most definitely struggle later on when things become more
complicated with your app. The framework is great for repetitive tasks but
Are you saying that those two print statements you were told to add are not
causing anything additional to be displayed on the screen when you run both
runserver and syncdb?
This is why I asked you to provide the output again. You may not understand
what we are looking for. Don't care about wha
I've provided the full errors in the post, it is there. ( same errors as
I've faced prior to adding the print __file__ and 'DATABASES', DATABASES) as
I'm encountering the same after I've copied and paste the print inside the
settings.py file at the end)
On Sun, Jan 23, 2011 at 9:40 PM, Graham Dump
That is two underscores, followed by 'file' followed by two underscores. Not
just a single underscore.
Please try and cut and paste out we give to use and vice versa. In other
words, provide complete output showing full errors and tracebacks. Such
information may be meaningful to use even if yo
it says that the _file_ is not defined.
On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:
>
>
> On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>>
>> Copy and Paste the following to replace your entire DATABASES tuple:
>>
>> DATABASES =
> That was already pointed out to them.
You're right, sorry my bad -- I just got to my computer and read the thread
rather than just using my phone.
> The lack of a comma should have resulted in a syntax error, which makes me
> believe, unless they modified the content before posting, that they
I am using pico editior and I've been saving the work by using the control
X.
On Sun, Jan 23, 2011 at 9:25 PM, Steven Elliott wrote:
> Also, what editor are you using? if its not an IDE-type thing remember to
> save your work in the editor. If you are coming from the Windows programming
> world
On Monday, January 24, 2011 2:19:09 PM UTC+11, Steven Elliott Jr wrote:
>
> Copy and Paste the following to replace your entire DATABASES tuple:
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3',
> 'NAME': 'database.db',
>
It is not working at all, still facing the same configuration problem
(ENGINE IS NOT SET).
On Sun, Jan 23, 2011 at 9:19 PM, Steven Elliott wrote:
> Copy and Paste the following to replace your entire DATABASES tuple:
>
> DATABASES = {
>'default': {
>'ENGINE': 'django.db.backends.sqli
Also, what editor are you using? if its not an IDE-type thing remember to save
your work in the editor. If you are coming from the Windows programming world
generally your programs will save when you build and run something in the IDE.
If you're using just an editor like Emacs, Vim, Gedit, Kate,
Copy and Paste the following to replace your entire DATABASES tuple:
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': 'database.db',
'USER': '',
'PASSWORD': '',
That doesn't work for me ( very very strange), that why I am very confused
on what is going on with the database itself.
On Sun, Jan 23, 2011 at 8:55 PM, Steven Elliott Jr wrote:
> I remember that the one time I tried sqlite it complained until I put a .db
> suffix on the name of my database. If
The error that I am seeing is in the shell/ the terminal. I am unable to
paste the exception problems on here. But I've typed it... look below
After I've ran the python manage.py runserver, there was NO errors. But when
I try to use, python manage.py syncdb, it showed errors/exceptions:
Traceback
I remember that the one time I tried sqlite it complained until I put a .db
suffix on the name of my database. If you do not specify the full path and just
specify a name, then it will just create the database file in your project's
root directory.
So, under name just put:
'NAME' : 'database.
On Monday, January 24, 2011 1:36:10 PM UTC+11, Kimberly wrote:
>
> username@debian:~/wikicamps$ python manage.py runserver
> Validating models
> 0 errors found
>
> Django version 1.2.4, using settings 'wikicamp.settings'
> Development server is running at http://127.0.0.1:8000/
> Quit the ser
username@debian:~/wikicamps$ python manage.py runserver
Validating models
0 errors found
Django version 1.2.4, using settings 'wikicamp.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
It runs fine, but yet I faced problem with the database ENG
Provide the full error including any Python traceback so we can see where
the error is occurring. If running manage.py runserver, easiest thing to do
is to provide the whole output from running the command.
Graham
On Monday, January 24, 2011 1:11:47 PM UTC+11, Kimberly wrote:
>
> Still doesn't
Still doesn't work. But thank you for trying to help me. It keep giving me
the same ENGINE configuration that it is not set.
On Sun, Jan 23, 2011 at 8:05 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:
>
>
> On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
>>
>> Sorry abo
On Monday, January 24, 2011 12:42:57 PM UTC+11, Kimberly wrote:
>
> Sorry about that... here is what I have in the settings.py ( similiar to
> what you showed, but mine is abit different in the NAME section):
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3',
Sorry about that... here is what I have in the settings.py ( similiar to
what you showed, but mine is abit different in the NAME section):
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2',
'postgresql', 'mysql', 'sqlite3' or 'oracle'.
Rather than have us guess what is in your settings file, post that whole
section. For example:
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2',
'postgresql', 'mysql', 'sqlite3' or 'oracle'.
'NAME': os.path.join(ENVIRON_ROOT, 'db'
I've used the tutorials and it doesn't work. I've done exactly what the
tutorial says, and it keeps saying that the ENGINE has not been set in the
setting. I am also using Django 1.2 or higher version.
On Sun, Jan 23, 2011 at 6:29 PM, Karen Tracey wrote:
> On Sun, Jan 23, 2011 at 6:47 PM, Kimber
On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey wrote:
> it still doesn't work. I typed it like you've suggested and it keeps saying
> that the database ENGINE has not been set.
>
>
If you are using ENGINE by itself, you need to be using Django 1.2 or higher
and ENGINE is a key in the dictionary
it still doesn't work. I typed it like you've suggested and it keeps saying
that the database ENGINE has not been set.
On Sun, Jan 23, 2011 at 5:11 AM, Mark Penix wrote:
> your whole engine line should read
> 'ENGINE': 'django.db.backends.sqlite3'
>
> --
> You received this message because you a
your whole engine line should read
'ENGINE': 'django.db.backends.sqlite3'
--
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 unsubscribe from this group, send email to
django-u
Hello! I have a problem with the Django. I was able to create django-
admin.py startproject project in my home directory, and was able to
see the files such as manage.py, init.py, settings.py, and so on.
After some steps, I approached a problem with manage.py syncdb. It
says that the database ENGIN
49 matches
Mail list logo
