Uptime all the time

[j harvey]

I am looking for ideas on how to keep my app running all the time, even 
when uploading data that will replace the current data. Some of these 
tables will have a million rows or more. Ideas?

Thanks in advance,

John

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8087a569-f379-4e0e-b3fa-92d281abad69n%40googlegroups.com.

Re: WSGI help required. Getting a 'No module named myFirstProject.wsgi' error.

[Harvey]

Hi 

My code looks like this...see below.  fails on last line. 
i.e. runfastcgi(method="threaded", daemonize="false")

Python Code is run from this 
path /home1/harveywe/www/dj/testProject/mySite.fcgi

environments 
PYTHONPATH=/home1/harveywe/.local/lib/python2.6/site-packages:/home1/harveywe/
PATH=/home1/harveywe/.local/bin:/home1/harveywe/.local/usr/bin:/usr/local/jdk/ 
 bin:/home1/harveywe/perl5/bin:/usr/lib64/qt-3.3/bin:/home1/harveywe/perl5/bin: 
 /ramdisk/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr 
 

This code being run on a ISP host (bluehost.com). 

Does any of this help?

Harevy


### MY CODE ##
harve...@harveywest.co.uk [~/www/dj/testProject]# cat mySite.fcgi
#!/usr/bin/python2.6
import sys, os

# Add a custom Python path.
sys.path.insert(0, "/home1/harveywe/.local/lib/python2.6")
sys.path.insert(13, "/home1/harveywe/django_projects/myFirstProject")


sys.path.insert(0, "/home1/harveywe/.local/lib/python2.6/flup-1.0.2")


# Switch to the directory of your project. (Optional.)
# os.chdir("/home/DJANGONOOB/django_projects/myFirstProject")

#from django.conf import settings

#settings.DEBUG = True




# Set the DJANGO_SETTINGS_MODULE environment variable.
os.environ['DJANGO_SETTINGS_MODULE'] = "settings"

from django.core.servers.fastcgi import runfastcgi
runfastcgi(method="threaded", daemonize="false")
 MY CODE END ###




On Tuesday, 29 May 2012 22:12:27 UTC+1, Harvey wrote:
>
> Setting up django for the first time 
>
> Any ideas what i need to look at to get this error to go away. Not 
> used "wsgi" before? 
>
>
> ~/www/django/mySite.fcgi 
>
> Traceback (most recent call last): 
>   File "./mySite.fcgi", line 19, in  
> runfastcgi(method="threaded", daemonize="false") 
>   File "/home1/harveywe/.local/lib/python2.6/site-packages/django/core/ 
> servers/fastcgi.py", line 182, in runfastcgi 
> WSGIServer(get_internal_wsgi_application(), **wsgi_opts).run() 
>   File "/home1/harveywe/.local/lib/python2.6/site-packages/django/core/ 
> servers/basehttp.py", line 60, in get_internal_wsgi_application 
> "could not import module '%s': %s" % (app_path, module_name, e)) 
> django.core.exceptions.ImproperlyConfigured: WSGI application 
> 'myFirstProject.wsgi.application' could not be loaded; could not 
> import module 'myFirstProject.wsgi': No module named 
> myFirstProject.wsgi 
>
> I'm assume this explains why i'm getting "HTTP Error 500 Internal 
> server error"

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/8emacSN1V_EJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

WSGI help required. Getting a 'No module named myFirstProject.wsgi' error.

[Harvey]

Setting up django for the first time

Any ideas what i need to look at to get this error to go away. Not
used "wsgi" before?


~/www/django/mySite.fcgi

Traceback (most recent call last):
  File "./mySite.fcgi", line 19, in 
runfastcgi(method="threaded", daemonize="false")
  File "/home1/harveywe/.local/lib/python2.6/site-packages/django/core/
servers/fastcgi.py", line 182, in runfastcgi
WSGIServer(get_internal_wsgi_application(), **wsgi_opts).run()
  File "/home1/harveywe/.local/lib/python2.6/site-packages/django/core/
servers/basehttp.py", line 60, in get_internal_wsgi_application
"could not import module '%s': %s" % (app_path, module_name, e))
django.core.exceptions.ImproperlyConfigured: WSGI application
'myFirstProject.wsgi.application' could not be loaded; could not
import module 'myFirstProject.wsgi': No module named
myFirstProject.wsgi

I'm assume this explains why i'm getting "HTTP Error 500 Internal
server error"

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Is django-syncr dead?

[Kevin Harvey]

Good day Djangonauts!

I'm wondering if anyone knows anything about django-syncr (
http://code.google.com/p/django-syncr/). The PyPI page hasn't been updated
for a year, and I think some of the YouTube API has changed. I'm bringing
an old project that relied pretty heavily on django-sycr up to Django
1.3.1, and it's not playing very nicely. I'm able to hack my way through
the code to get it to work, but there's always a better way than that,
right? Questions:

   - Is there something out there that I should be using besides
   django-syncr? Always interested in best practices.
   - If not, is there any interest in reviving this project? I'd be happy
   to contribute.
   - Any code out there that hasn't been committed that could be?
   - Anyone using django-syncr (particularly the YouTube parts) and new
   syncs are working properly? It seems to be trying non-exisitent URLs.

--
Kevin Harvey
Web Developer
kchar...@gmail.com
@kevinharvey <https://twitter.com/#%21/kevinharvey>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: What Can I use?

[Kevin Harvey]

I always look at djangopackages.com for questions like this: 
http://djangopackages.com/grids/g/commenting/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/Ber8mjS00bwJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: How do I sort choices by their localized label?

[Kevin Harvey]

Have you tried sorting them at the template level? A filter like dictsort 
might do the trick 
https://docs.djangoproject.com/en/dev/ref/templates/builtins/?from=olddocs#dictsort

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/xAdGQ21s2BcJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

'IOError: [Errno 2] No such file or directory' when testing file uploads

[Kevin Harvey]

I'm trying to write a test for a FileField on a model Photo. The FieldField 
is inherited from an base class Asset. I need to save the dimensions of the 
photo in the database, so I've got my own save method on my Photo model:

def save(self, *args, **kwargs):
# save the instance, so we can use the uploaded photo
super(Photo, self).save(*args, **kwargs)
im = Image.open(os.path.join(MEDIA_ROOT, self.file.name))
self.width, self.height = im.size
super(Photo, self).save(*args, **kwargs)

This works, but I can't test it. When I try to create an instance of this 
model in the test suite, it appears that the file is never moved to the 
MEDIA_ROOT, and self.file.name refers to the original file in the test 
directory of my app.

==
ERROR: testPhoto (caramel.content.tests.modelTests.ContentTest)
--
Traceback (most recent call last):
  File "../myproject/myproject/myapp/tests/modelTests.py", line 22, in setUp
credit="John Smith")
  File 
"/Users/username/workspace/eclipse/lib/python2.7/site-packages/django/db/models/manager.py",
 
line 138, in create
return self.get_query_set().create(**kwargs)
  File 
"/Users/username/workspace/eclipse/lib/python2.7/site-packages/django/db/models/query.py",
 
line 360, in create
obj.save(force_insert=True, using=self.db)
  File "../myproject/myproject/myapp/models.py", line 97, in save
im = Image.open(os.path.join(MEDIA_ROOT, self.file.name))
  File 
"/Users/username/workspace/eclipse/lib/python2.7/site-packages/PIL/Image.py", 
line 1952, in open
fp = __builtin__.open(fp, "rb")
IOError: [Errno 2] No such file or directory: 
'/Users/username/workspace/eclipse/project/media/../myproject/myproject/myapp/tests/assets/test.jpg'

I'm using PIL's width/height methods here because I can't use Django's own 
get_image_dimensions, as it's not an ImageField. Thanks in advance.

Kevin

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/NQnc9nXpZXkJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django - Verfication of runserver vs browser

[Kimberly Harvey]

Thanks, I restarted the whole Django program. Will send feedbacks if any
problems this week.

On Tue, Jan 25, 2011 at 12:17 AM, raj  wrote:

> If none of above seems to work, You may be using a browser like google
> chrome, which by default ignores the localhost.
>
> --
>  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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django - Verfication of runserver vs browser

[Kimberly Harvey]

I gotten far enough to where I was able to runserver and it detects NO
errors, and that I was able to create my superusers after I've syncdb the
manage.py file. On screen:  " You just installed Django's auth system, which
means you dont have any superusers defined, would you like to create on?"
Once i did all of that, and reun the server, it keeps saying there were no
errors. Yes, I checked the browser ON linux.

I am not on my personal computer right now to post what I am seeing. When I
get home, I will copy/paste exactly what it shows on the screen.

On Mon, Jan 24, 2011 at 1:15 PM, Steven Elliott Jr <steve...@me.com> wrote:

> Have you tried running it on a different port? Can you post the actual
> error message you get?
>
> -Steven Elliott Jr
>
> On Jan 24, 2011, at 2:05 PM, Kimberly Harvey <kharve...@gmail.com> wrote:
>
> I ran the browser in the linux.
>
> On Mon, Jan 24, 2011 at 12:57 PM, Javier Guerra Giraldez <<jav...@guerrag.com>
> jav...@guerrag.com> wrote:
>
>> On Mon, Jan 24, 2011 at 1:43 PM, Kimberly Harvey < <kharve...@gmail.com>
>> kharve...@gmail.com> wrote:
>> > I am using the Django inside the Linux-Debian on my windows 7 machine.
>>
>> do you run your browser in Windows or Linux?
>>
>> if it's on windows, then accessing the dev-server on the Linux virtual
>> machine is just like going to any other machine; you can't use
>> 127.0.0.1
>>
>> ah, and remember that your VM can't use the same IP# as your windows host
>>
>> --
>> Javier
>>
>> --
>> 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>
>> django-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> <django-users%2bunsubscr...@googlegroups.com>
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> <http://groups.google.com/group/django-users?hl=en>
>> http://groups.google.com/group/django-users?hl=en.
>>
>>
>  --
> 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-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>  --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django - Verfication of runserver vs browser

[Kimberly Harvey]

I ran the browser in the linux.

On Mon, Jan 24, 2011 at 12:57 PM, Javier Guerra Giraldez <jav...@guerrag.com
> wrote:

> On Mon, Jan 24, 2011 at 1:43 PM, Kimberly Harvey <kharve...@gmail.com>
> wrote:
> > I am using the Django inside the Linux-Debian on my windows 7 machine.
>
> do you run your browser in Windows or Linux?
>
> if it's on windows, then accessing the dev-server on the Linux virtual
> machine is just like going to any other machine; you can't use
> 127.0.0.1
>
> ah, and remember that your VM can't use the same IP# as your windows host
>
> --
> Javier
>
> --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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 <kharve...@gmail.com>wrote:

> 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.break
> because the Django originally used the settings.py), so that why I did the
> move 2 times. Originally before the settings.py.break came into play, there
> was another settings.py elsewhere in the file which create some corruption (
> hence, problem with configuration -- DATABASE ENGINE was not set).
> Therefore, to remove the settings.py from another location, I had to do what
> I did above. Oddly, it works.
>
> On Mon, Jan 24, 2011 at 12:29 PM, Mark Penix <mark.pe...@gmail.com> wrote:
>
>> This might be a stupid question but did you install the sqlite package?
>>
>>
>> On Mon, Jan 24, 2011 at 9:39 AM, Kelly Nicholes 
>> <kelbolici...@gmail.com>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 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 <graham.dumple...@gmail.com>
>>> 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 output again. You may not
>>> understand
>>> > what we are looking for. Don't care about what the error is at the
>>> point but
>>> > the information that those print statements should have output.
>>> >
>>> > Graham
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>>> >
>>> > > 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 Dumpleton <
>>> graham.d...@gmail.com>wrote:
>>> >
>>> > >> 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 you think it isn't.
>>> >
>>> > >> Graham
>>> >
>>> > >> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>>> >
>>> > >>> it says that the _file_ is not defined.
>>> >
>>> > >>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton <
>>> graha...@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 = {
>>> > >>>>> 'default': {
>>> > >>>>> 'ENGINE': 'django.db.backends.sqlite3',
>>> > >>>>> 'NAME': 'database.db',
>>> > >>>>> 'USER': '',
>>> > >>>>> 'PASSWORD': '',
>>> > >>>>> 'HOST': '',
>>> > >>>>> 'PORT': '',
>>> > >>>>> }
>>> > >>>>> }
>>> >
>>> > >>>>> it looks like in your configuration you are also missing a 

Re: Django Improper Configuration

[Kimberly Harvey]

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.break
because the Django originally used the settings.py), so that why I did the
move 2 times. Originally before the settings.py.break came into play, there
was another settings.py elsewhere in the file which create some corruption (
hence, problem with configuration -- DATABASE ENGINE was not set).
Therefore, to remove the settings.py from another location, I had to do what
I did above. Oddly, it works.

On Mon, Jan 24, 2011 at 12:29 PM, Mark Penix  wrote:

> 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 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:
>>  > 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 what the error is at the point
>> but
>> > the information that those print statements should have output.
>> >
>> > Graham
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>> >
>> > > 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 Dumpleton <
>> graham.d...@gmail.com>wrote:
>> >
>> > >> 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 you think it isn't.
>> >
>> > >> Graham
>> >
>> > >> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>> >
>> > >>> it says that the _file_ is not defined.
>> >
>> > >>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton <
>> graha...@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 = {
>> > > 'default': {
>> > > 'ENGINE': 'django.db.backends.sqlite3',
>> > > 'NAME': 'database.db',
>> > > 'USER': '',
>> > > 'PASSWORD': '',
>> > > 'HOST': '',
>> > > 'PORT': '',
>> > > }
>> > > }
>> >
>> > > it looks like in your configuration you are also missing a comma
>> after
>> > > the name of the database. Remember you must include that comma
>> because this
>> > > is a tuple.
>> >
>> >  That was already pointed out to them.
>> >
>> >  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 may
>> >  be modifying a different file to what is being read.
>> >
>> >  I would like to see them, instead of changing DATABASES yet again,
>> is to
>> >  add at the very end of their settings.py file, the lines:
>> >
>> >    print __file__
>> >    print 'DATABASES', DATABASES
>> >
>> >  This will prove two things. First that the file is being read as
>> the
>> >  output from this should show on stdout when running runserver or
>> syncdb.
>> >  Second, will show what Python is seeing DATABASES as being set to.
>> >
>> >  if it doesn't show, then wrong file. If shows, but is different to
>> what
>> >  they believe they are setting it to, they could have multiple
>> DATABASES
>> >  entries in file.
>> >
>> >  Graham
>> >
>> >   --
>> >  You received this message because you are subscribed to the Google
>> >  Groups "Django users" group.
>> >  To post to this group, send email to djan...@googlegroups.com.
>> >  To unsubscribe from this group, send email to
>> >  django-...@googlegroups.com.
>> >
>> >  For more options, visit this group at
>> > http://groups.google.com/group/django-users?hl=en.
>> >
>> > >>>  --
>> > >> 

Re: Django - Verfication of runserver vs browser

[Kimberly Harvey]

response to messages:

I am using the Django inside the Linux-Debian on my windows 7 machine. This
is what happen when I opened the terminal in the Django..
command: python manage.py runserver
It runs fine... 0 errors.
It shows me the url which is http://..  then I went to the browser on
the Djano which is run on the linux-Debian virtual box, and copied the url
that the terminal stated there were no errors. Once I did that, it  says it
refused connection.


Answer to Bill Freeman: Yes the broswer running on the same box as django (
Like I've mentioned above to another post). I will do what you suggest which
is to run the server 0.0.0.0:8000.
I don't understand on how I have a firewall when the terminal stated that
there are 0 errors after I ran the manage.py runserver.



On Mon, Jan 24, 2011 at 10:24 AM, Bill Freeman  wrote:

> Is the browser running on the same box as djanog?  By default, the
> development server won't answer requests that don't come from the
> local box.  If this is the issue, try:
>
>   python manage.py runserver 0.0.0.0:8000
>
> This tells the development server to accept requests from anywhere.
>
> It is also possible that you have firewall settings that prevent you
> from accessing the box.
>
> Bill
>
> On Mon, Jan 24, 2011 at 1:21 AM, Shawn Milochik 
> wrote:
> > If you've been messing around quite a bit trying to fix other issues, the
> port may be held up by a zombie process or something.
> >
> > Try rebooting. If that doesn't work, see if the command line where
> runserver is running displays any message.
> >
> > Shawn
> >
> > --
> > 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-users+unsubscr...@googlegroups.com
> .
> > For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
> >
> >
>
> --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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 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
>> page I wanted
>> 1) Google cache
>> 2) Internet Archive
>>
>
> If you have a new problem and can't work out out, I would strongly suggest
> you create a new distinct message thread so that it isn't buried in this
> one. This one has gone on so long that people would now be ignoring it most
> likely. Use a new thread for new issue and you will have more luck getting
> help with it. More than likely your issue is transient and will resolve
> itself. Am sure someone else will help if they are able. I am taking a break
> for a while.
>
> Graham
>
>
>> Please tell me that it has nothing to do with the settings, manage, urls,
>> etc files. Do I need to change my cache as it may be the problem?
>>
>> As for the question about the settings.py, and settings.py.broken, I won't
>> question it, lol.
>>
>> On Sun, Jan 23, 2011 at 11:50 PM, Graham Dumpleton <graham.d...@gmail.com
>> > wrote:
>>
>>>
>>>
>>> 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.py.broken which places all of the file of settings.py
>>>> inside the settings.py.broken. I then MOVED the file again from
>>>> settings.py.broken to settings.py and at the command line, python manage.py
>>>> syncdb it works! May I ask why it worked like that?
>>>>
>>>
>>> No idea. Just don't put any backup copy of settings.py in the directory
>>> above where the proper one is located. This is because Django does a trick
>>> with the Python module search path so that that parent directory gets added
>>> to sys.path for a moment and this may cause that backup copy to get imported
>>> wrongly meaning wrong settings used. So, don't question it, just be happy it
>>> is working. :-)
>>>
>>> Graham
>>>
>>>
>>>
>>>> On Sun, Jan 23, 2011 at 11:32 PM, Graham Dumpleton 
>>>> <graha...@gmail.com>wrote:
>>>>
>>>>>
>>>>>
>>>>> 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 if it works?
>>>>>>
>>>>>
>>>>> YES. YES. YES.
>>>>>
>>>>> :-)
>>>>>
>>>>> Graham
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton <grah...@gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 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 settings.__file__
>>>>>>>
>>>>>>>   import wikicamp.settings
>>>>>>>   print wikicamp.settings.__file__
>>>>>>>
>

Re: Django Improper Configuration

[Kimberly Harvey]

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
page I wanted
1) Google cache
2) Internet Archive

Please tell me that it has nothing to do with the settings, manage, urls,
etc files. Do I need to change my cache as it may be the problem?

As for the question about the settings.py, and settings.py.broken, I won't
question it, lol.

On Sun, Jan 23, 2011 at 11:50 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> 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.py.broken which places all of the file of settings.py
>> inside the settings.py.broken. I then MOVED the file again from
>> settings.py.broken to settings.py and at the command line, python manage.py
>> syncdb it works! May I ask why it worked like that?
>>
>
> No idea. Just don't put any backup copy of settings.py in the directory
> above where the proper one is located. This is because Django does a trick
> with the Python module search path so that that parent directory gets added
> to sys.path for a moment and this may cause that backup copy to get imported
> wrongly meaning wrong settings used. So, don't question it, just be happy it
> is working. :-)
>
> Graham
>
>
>
>> On Sun, Jan 23, 2011 at 11:32 PM, Graham Dumpleton <graham.d...@gmail.com
>> > wrote:
>>
>>>
>>>
>>> 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 if it works?
>>>>
>>>
>>> YES. YES. YES.
>>>
>>> :-)
>>>
>>> Graham
>>>
>>>
>>>
>>>>
>>>> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton 
>>>> <graha...@gmail.com>wrote:
>>>>
>>>>>
>>>>>
>>>>> 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 settings.__file__
>>>>>
>>>>>   import wikicamp.settings
>>>>>   print wikicamp.settings.__file__
>>>>>
>>>>>   after importing setting
>>>>>   print settings.__file__
>>>>>   OUTPUT: settings.pyc
>>>>>
>>>>>   import wikicamp.settings
>>>>>   print wikicamp.settings.__file__
>>>>>
>>>>>   OUTPUT: wikicamp/settings.pyc
>>>>>
>>>>> What directory did you do that from.
>>>>>
>>>>> If you didn't run this from inside of site directory as was expecting
>>>>> and you did it from your home directory, then you have a settings.py 
>>>>> sitting
>>>>> in your home directory which is the problem. Rename any settings.py file 
>>>>> you
>>>>> home directory to something else.
>>>>>
>>>>>   mv ~/settings.py ~/settings.py.broken
>>>>>
>>>>> In short, you have more than one settings.py file somewhere where it is
>>>>> being found and the second one is causing a conflict.
>>>>>
>>>>> Graham
>>>>>
>>>>>
>>>>>>  On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey 
>>>>>> <kha...@gmail.com>wrote:
>>>>>>
>>>>>>>  Sorry about that, there is nothing showing for either  echo
>>>>>>> $PYTHONPATH and  echo $

Re: Django Improper Configuration

[Kimberly Harvey]

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. I then MOVED the file again from
settings.py.broken to settings.py and at the command line, python manage.py
syncdb it works! May I ask why it worked like that?

On Sun, Jan 23, 2011 at 11:32 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> 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 if it works?
>>
>
> YES. YES. YES.
>
> :-)
>
> Graham
>
>
>
>>
>> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton <graham.d...@gmail.com
>> > wrote:
>>
>>>
>>>
>>> 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 settings.__file__
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>>   after importing setting
>>>   print settings.__file__
>>>   OUTPUT: settings.pyc
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>>   OUTPUT: wikicamp/settings.pyc
>>>
>>> What directory did you do that from.
>>>
>>> If you didn't run this from inside of site directory as was expecting and
>>> you did it from your home directory, then you have a settings.py sitting in
>>> your home directory which is the problem. Rename any settings.py file you
>>> home directory to something else.
>>>
>>>   mv ~/settings.py ~/settings.py.broken
>>>
>>> In short, you have more than one settings.py file somewhere where it is
>>> being found and the second one is causing a conflict.
>>>
>>> Graham
>>>
>>>
>>>> On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey <kha...@gmail.com>wrote:
>>>>
>>>>>  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 <graha...@gmail.com
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> 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 settings.__file__
>>>>>>>
>>>>>>>   import wikicamp.settings
>>>>>>>   print wikicamp.settings.__file__
>>>>>>>
>>>>>>> after importing setting
>>>>>>> print settings.__file__
>>>>>>> OUTPUT: settings.pyc
>>>>>>>
>>>>>>>  import wikicamp.settings
>>>>>>>   print wikicamp.settings.__file__
>>>>>>>
>>>>>>> OUTPUT: wikicamp/settings.pyc
>>>>>>>
>>>>>>
>>>>>> Unfortunately you did not show what PYTHONPATH, or
>>>>>> DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
>>>>>> cause,
>>>>>> but the above suggests that you have two Django projects created. One is 
>>>>>> at:
>>>>>>
>>>>>>   /home/username/wikicamp
>&

Re: Django Improper Configuration

[Kimberly Harvey]

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, 2011 at 11:25 PM, Kimberly Harvey <kharve...@gmail.com>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
> if it works?
>
> On Sun, Jan 23, 2011 at 11:17 PM, Graham Dumpleton <
> graham.dumple...@gmail.com> wrote:
>
>>
>>
>> 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 settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>>   after importing setting
>>   print settings.__file__
>>   OUTPUT: settings.pyc
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>>   OUTPUT: wikicamp/settings.pyc
>>
>> What directory did you do that from.
>>
>> If you didn't run this from inside of site directory as was expecting and
>> you did it from your home directory, then you have a settings.py sitting in
>> your home directory which is the problem. Rename any settings.py file you
>> home directory to something else.
>>
>>   mv ~/settings.py ~/settings.py.broken
>>
>> In short, you have more than one settings.py file somewhere where it is
>> being found and the second one is causing a conflict.
>>
>> Graham
>>
>>
>>> On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey <khar...@gmail.com>wrote:
>>>
>>>>  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.d...@gmail.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> 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 settings.__file__
>>>>>>
>>>>>>   import wikicamp.settings
>>>>>>   print wikicamp.settings.__file__
>>>>>>
>>>>>> after importing setting
>>>>>> print settings.__file__
>>>>>> OUTPUT: settings.pyc
>>>>>>
>>>>>>  import wikicamp.settings
>>>>>>   print wikicamp.settings.__file__
>>>>>>
>>>>>> OUTPUT: wikicamp/settings.pyc
>>>>>>
>>>>>
>>>>> Unfortunately you did not show what PYTHONPATH, or
>>>>> DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
>>>>> cause,
>>>>> but the above suggests that you have two Django projects created. One is 
>>>>> at:
>>>>>
>>>>>   /home/username/wikicamp
>>>>>
>>>>> and the other at:
>>>>>
>>>>>   /home/username/wikicamp/wikicamp
>>>>>
>>>>> Can you confirm this by indicating whether then file:
>>>>>
>>>>>   /home/username/wikicamp/wikicamp/settings.py
>>>>>
>>>>> exists.
>>>>>
>>>>> If this is write, then what is happening is that when syncb is being
>>>>> running it is actually picking up the settings file from that second site
>>>>> nested within the first.
>>>>>
>>>>> If that is what has been done, then do:
>>>>>
>>>>>
>

Re: Django Improper Configuration

[Kimberly Harvey]

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.dumple...@gmail.com> wrote:

>
>
> 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 settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
>   after importing setting
>   print settings.__file__
>   OUTPUT: settings.pyc
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
>   OUTPUT: wikicamp/settings.pyc
>
> What directory did you do that from.
>
> If you didn't run this from inside of site directory as was expecting and
> you did it from your home directory, then you have a settings.py sitting in
> your home directory which is the problem. Rename any settings.py file you
> home directory to something else.
>
>   mv ~/settings.py ~/settings.py.broken
>
> In short, you have more than one settings.py file somewhere where it is
> being found and the second one is causing a conflict.
>
> Graham
>
>
>> On Sun, Jan 23, 2011 at 11:02 PM, Kimberly Harvey <khar...@gmail.com>wrote:
>>
>>> 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.d...@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> 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 settings.__file__
>>>>>
>>>>>   import wikicamp.settings
>>>>>   print wikicamp.settings.__file__
>>>>>
>>>>> after importing setting
>>>>> print settings.__file__
>>>>> OUTPUT: settings.pyc
>>>>>
>>>>>  import wikicamp.settings
>>>>>   print wikicamp.settings.__file__
>>>>>
>>>>> OUTPUT: wikicamp/settings.pyc
>>>>>
>>>>
>>>> Unfortunately you did not show what PYTHONPATH, or
>>>> DJANGO_SETTINGS_MODULE was set to in environment to eliminate them as 
>>>> cause,
>>>> but the above suggests that you have two Django projects created. One is 
>>>> at:
>>>>
>>>>   /home/username/wikicamp
>>>>
>>>> and the other at:
>>>>
>>>>   /home/username/wikicamp/wikicamp
>>>>
>>>> Can you confirm this by indicating whether then file:
>>>>
>>>>   /home/username/wikicamp/wikicamp/settings.py
>>>>
>>>> exists.
>>>>
>>>> If this is write, then what is happening is that when syncb is being
>>>> running it is actually picking up the settings file from that second site
>>>> nested within the first.
>>>>
>>>> If that is what has been done, then do:
>>>>
>>>>
>>>>   mv /home/username/wikicamp/wikicamp 
>>>> /home/username/wikicamp/wikicamp.broken
>>>>
>>>> Also be aware that you shouldn't create Django apps with the same name
>>>> as the project either, as the duplication of name can cause problems there
>>>> as well, although for an app you wouldn't have a settings.py file in it,
>>>> which in this case it seems you do.
>>>>
>>>> Graham
>>>>
>>>>
>>>>> These might produce exceptions depending on where you current working
>>>>> directory is.
>>>>>
>>>>> This is to show whether you may have created a backup copy of
>>>>> settings.py file somewhere which is being found instead of that in same

Re: Django Improper Configuration

[Kimberly Harvey]

  /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 <kharve...@gmail.com>wrote:

> 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 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 settings.__file__
>>>
>>>   import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>> after importing setting
>>> print settings.__file__
>>> OUTPUT: settings.pyc
>>>
>>>  import wikicamp.settings
>>>   print wikicamp.settings.__file__
>>>
>>> OUTPUT: wikicamp/settings.pyc
>>>
>>
>> Unfortunately you did not show what PYTHONPATH, or DJANGO_SETTINGS_MODULE
>> was set to in environment to eliminate them as cause, but the above suggests
>> that you have two Django projects created. One is at:
>>
>>   /home/username/wikicamp
>>
>> and the other at:
>>
>>   /home/username/wikicamp/wikicamp
>>
>> Can you confirm this by indicating whether then file:
>>
>>   /home/username/wikicamp/wikicamp/settings.py
>>
>> exists.
>>
>> If this is write, then what is happening is that when syncb is being
>> running it is actually picking up the settings file from that second site
>> nested within the first.
>>
>> If that is what has been done, then do:
>>
>>
>>   mv /home/username/wikicamp/wikicamp /home/username/wikicamp/wikicamp.broken
>>
>> Also be aware that you shouldn't create Django apps with the same name as
>> the project either, as the duplication of name can cause problems there as
>> well, although for an app you wouldn't have a settings.py file in it, which
>> in this case it seems you do.
>>
>> Graham
>>
>>
>>> These might produce exceptions depending on where you current working
>>> directory is.
>>>
>>> This is to show whether you may have created a backup copy of settings.py
>>> file somewhere which is being found instead of that in same directory as
>>> manage.py.
>>>
>>> Finally, if you have modified manage.py, tell is what you have changed it
>>> to.
>>>
>>>
>>>
>>> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton <
>>> graham.d...@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> 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
>>>>> File
>>>>> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
>>>>> 379, in execute
>>>>>   self.fetch_command(subcommand).run_from_argv(self.argv)
>>>>> File
>>>>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
>>>>> 191,
>>>>> in run_from_argv
>>>>> self.exectured(*args, **options._dict_)
>>>>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>>>>> line 220, in execute
>>>>> output = self.handle(*args, **options)
>>>>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>>>>> line 351, in handle
>>>>>return self.handle_noargs(**options)
>>>>> File
>>>>> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
>>>>> line 52, in handle_noargs
>>>>> cursor = connection.cursor()
>>>>> File
>>>>> "/usr/lib/python2.5/site-packages/dj

Re: Django Improper Configuration

[Kimberly Harvey]

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 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 settings.__file__
>>
>>   import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> after importing setting
>> print settings.__file__
>> OUTPUT: settings.pyc
>>
>>  import wikicamp.settings
>>   print wikicamp.settings.__file__
>>
>> OUTPUT: wikicamp/settings.pyc
>>
>
> Unfortunately you did not show what PYTHONPATH, or DJANGO_SETTINGS_MODULE
> was set to in environment to eliminate them as cause, but the above suggests
> that you have two Django projects created. One is at:
>
>   /home/username/wikicamp
>
> and the other at:
>
>   /home/username/wikicamp/wikicamp
>
> Can you confirm this by indicating whether then file:
>
>   /home/username/wikicamp/wikicamp/settings.py
>
> exists.
>
> If this is write, then what is happening is that when syncb is being
> running it is actually picking up the settings file from that second site
> nested within the first.
>
> If that is what has been done, then do:
>
>
>   mv /home/username/wikicamp/wikicamp /home/username/wikicamp/wikicamp.broken
>
> Also be aware that you shouldn't create Django apps with the same name as
> the project either, as the duplication of name can cause problems there as
> well, although for an app you wouldn't have a settings.py file in it, which
> in this case it seems you do.
>
> Graham
>
>
>> These might produce exceptions depending on where you current working
>> directory is.
>>
>> This is to show whether you may have created a backup copy of settings.py
>> file somewhere which is being found instead of that in same directory as
>> manage.py.
>>
>> Finally, if you have modified manage.py, tell is what you have changed it
>> to.
>>
>>
>>
>> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> 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
 File
 "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
 379, in execute
   self.fetch_command(subcommand).run_from_argv(self.argv)
 File
 "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 
 191,
 in run_from_argv
 self.exectured(*args, **options._dict_)
 File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
 line 220, in execute
 output = self.handle(*args, **options)
 File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
 line 351, in handle
return self.handle_noargs(**options)
 File
 "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
 line 52, in handle_noargs
 cursor = connection.cursor()
 File
 "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py", line
 15, in complain
 raise ImproperlyConfigured("You hav
 en't set the database ENGINE setting yet.")

 THE ABOVE IS when I typed python manage.py syncdb

>>>
>>> Okay, if you definitely 100% aren't seeing something like:
>>>
>>> /home/username/wikicamp/settings.pyc
>>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>>>
>>> when running syncdb, then having a hard time explaining why it isn't
>>> being loaded.
>>>
>>> Please do the following and provide the output:
>>>
>>>   pwd
>>>
>>> This is to show us the directory you are in when you are running
>>> runserver and syncdb.
>>>
>>>   echo $PYTHONPATH
>>>
>>> This is to show us if you have a custom Python module search path set in
>>> your environment.
>>>
>>>   echo $DJANGO_SETTINGS_MODULE
>>>
>>> This is show is if you are setting where Django should find its settings
>>> module.
>>>
>>> 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__
>>>
>>> These might produce exceptions depending on where you current working
>>> directory is.
>>>
>>> This is to show whether you may have created a backup copy of settings.py
>>> file somewhere which is being found instead of that in same directory as
>>> manage.py.
>>>
>>> Finally, if you have 

Re: Django Improper Configuration

[Kimberly Harvey]

I did not modified the manage.py file





On Sun, Jan 23, 2011 at 10:44 PM, Kimberly Harvey <kharve...@gmail.com>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 settings.__file__
>
>   import wikicamp.settings
>   print wikicamp.settings.__file__
>
> after importing setting
> print settings.__file__
> OUTPUT: settings.pyc
>
>  import wikicamp.settings
>   print wikicamp.settings.__file__
>
> OUTPUT: wikicamp/settings.pyc
>
> These might produce exceptions depending on where you current working
> directory is.
>
> This is to show whether you may have created a backup copy of settings.py
> file somewhere which is being found instead of that in same directory as
> manage.py.
>
> Finally, if you have modified manage.py, tell is what you have changed it
> to.
>
>
>
> On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton <
> graham.dumple...@gmail.com> wrote:
>
>>
>>
>> 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
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
>>> 379, in execute
>>>   self.fetch_command(subcommand).run_from_argv(self.argv)
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 191,
>>> in run_from_argv
>>> self.exectured(*args, **options._dict_)
>>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>>> line 220, in execute
>>> output = self.handle(*args, **options)
>>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>>> line 351, in handle
>>>return self.handle_noargs(**options)
>>> File
>>> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
>>> line 52, in handle_noargs
>>> cursor = connection.cursor()
>>> File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
>>> line 15, in complain
>>> raise ImproperlyConfigured("You hav
>>> en't set the database ENGINE setting yet.")
>>>
>>> THE ABOVE IS when I typed python manage.py syncdb
>>>
>>
>> Okay, if you definitely 100% aren't seeing something like:
>>
>> /home/username/wikicamp/settings.pyc
>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>>
>> when running syncdb, then having a hard time explaining why it isn't being
>> loaded.
>>
>> Please do the following and provide the output:
>>
>>   pwd
>>
>> This is to show us the directory you are in when you are running runserver
>> and syncdb.
>>
>>   echo $PYTHONPATH
>>
>> This is to show us if you have a custom Python module search path set in
>> your environment.
>>
>>   echo $DJANGO_SETTINGS_MODULE
>>
>> This is show is if you are setting where Django should find its settings
>> module.
>>
>> 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__
>>
>> These might produce exceptions depending on where you current working
>> directory is.
>>
>> This is to show whether you may have created a backup copy of settings.py
>> file somewhere which is being found instead of that in same directory as
>> manage.py.
>>
>> Finally, if you have modified manage.py, tell is what you have changed it
>> to.
>>
>> Graham
>>
>> Below is when I ran the python manage.py runserver
>>> /home/username/wikicamp/settings.pyc
>>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>>> validating models...
>>> 0 errors found
>>>
>>> Django version 1.2.4, using settings 'wikicamp.settings'
>>> Developmen

Re: Django Improper Configuration

[Kimberly Harvey]

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 importing setting
print settings.__file__
OUTPUT: settings.pyc

 import wikicamp.settings
  print wikicamp.settings.__file__

OUTPUT: wikicamp/settings.pyc

These might produce exceptions depending on where you current working
directory is.

This is to show whether you may have created a backup copy of settings.py
file somewhere which is being found instead of that in same directory as
manage.py.

Finally, if you have modified manage.py, tell is what you have changed it
to.



On Sun, Jan 23, 2011 at 10:27 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> 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
>> File
>> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
>> 379, in execute
>>   self.fetch_command(subcommand).run_from_argv(self.argv)
>> File
>> "/usr/lib/python2.5/site-packages/django/core/management/base.py", line 191,
>> in run_from_argv
>> self.exectured(*args, **options._dict_)
>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>> line 220, in execute
>> output = self.handle(*args, **options)
>> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
>> line 351, in handle
>>return self.handle_noargs(**options)
>> File
>> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
>> line 52, in handle_noargs
>> cursor = connection.cursor()
>> File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
>> line 15, in complain
>> raise ImproperlyConfigured("You hav
>> en't set the database ENGINE setting yet.")
>>
>> THE ABOVE IS when I typed python manage.py syncdb
>>
>
> Okay, if you definitely 100% aren't seeing something like:
>
> /home/username/wikicamp/settings.pyc
> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>
> when running syncdb, then having a hard time explaining why it isn't being
> loaded.
>
> Please do the following and provide the output:
>
>   pwd
>
> This is to show us the directory you are in when you are running runserver
> and syncdb.
>
>   echo $PYTHONPATH
>
> This is to show us if you have a custom Python module search path set in
> your environment.
>
>   echo $DJANGO_SETTINGS_MODULE
>
> This is show is if you are setting where Django should find its settings
> module.
>
> 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__
>
> These might produce exceptions depending on where you current working
> directory is.
>
> This is to show whether you may have created a backup copy of settings.py
> file somewhere which is being found instead of that in same directory as
> manage.py.
>
> Finally, if you have modified manage.py, tell is what you have changed it
> to.
>
> Graham
>
> Below is when I ran the python manage.py runserver
>> /home/username/wikicamp/settings.pyc
>> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>> 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
>>
>> Those are the outputs after y
>>
>>
>> On Sun, Jan 23, 2011 at 10:11 PM, Graham Dumpleton > > wrote:
>>
>>>
>>>
>>> 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 output again. You may not
 understand what we are looking for. Don't care about what the error is at
 the point but the information that those print statements should have
 output.

>>>
>>> For the record, I would expect to see those print statements produce
>>> output at least twice. This is because settings.py actually gets imported
>>> multiple times. So, for example I see:
>>>
>>> Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
>>> Traceback (most recent call last):
>>>   File "manage.py", line 2, in 
>>> from django.core.management import execute_manager
>>> ImportError: No 

Re: Django Improper Configuration

[Kimberly Harvey]

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 <kharve...@gmail.com>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
> File
> "/usr/lib/python2.5/site-packages/django/core/management/_init_.py", line
> 379, in execute
>   self.fetch_command(subcommand).run_from_argv(self.argv)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 191, in run_from_argv
> self.exectured(*args, **options._dict_)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 220, in execute
> output = self.handle(*args, **options)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 351, in handle
>return self.handle_noargs(**options)
> File
> "/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
> line 52, in handle_noargs
> cursor = connection.cursor()
> File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
> line 15, in complain
> raise ImproperlyConfigured("You hav
> en't set the database ENGINE setting yet.")
>
> THE ABOVE IS when I typed python manage.py syncdb
>
>
>
>
> Below is when I ran the python manage.py runserver
> /home/username/wikicamp/settings.pyc
> DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> 'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
>
> 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
>
> Those are the outputs after y
>
>
> On Sun, Jan 23, 2011 at 10:11 PM, Graham Dumpleton <
> graham.dumple...@gmail.com> wrote:
>
>>
>>
>> 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 output again. You may not
>>> understand what we are looking for. Don't care about what the error is at
>>> the point but the information that those print statements should have
>>> output.
>>>
>>
>> For the record, I would expect to see those print statements produce
>> output at least twice. This is because settings.py actually gets imported
>> multiple times. So, for example I see:
>>
>> Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
>> Traceback (most recent call last):
>>   File "manage.py", line 2, in 
>> from django.core.management import execute_manager
>> ImportError: No module named django.core.management
>> Grumpys-MacBook-Pro:mysite graham$ source ../../bin/activate
>> (django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
>> /Library/WebServer/Sites/django-2/projects/mysite/settings.py
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
>> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
>> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
>> 'PASSWORD': '', 'PORT': ''}}
>> Validating models...
>>
>> 0 errors found
>> Django version 1.3 beta 1, using settings 'mysite.settings'
>> Development server is running at http://127.0.0.1:8000/
>> Quit the server with CONTROL-C.
>>
>>
>> ^C(django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py syncdb
>> /Libra

Re: Django Improper Configuration

[Kimberly Harvey]

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
379, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
line 191, in run_from_argv
self.exectured(*args, **options._dict_)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
220, in execute
output = self.handle(*args, **options)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
351, in handle
   return self.handle_noargs(**options)
File
"/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
line 52, in handle_noargs
cursor = connection.cursor()
File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
line 15, in complain
raise ImproperlyConfigured("You hav
en't set the database ENGINE setting yet.")

THE ABOVE IS when I typed python manage.py syncdb




Below is when I ran the python manage.py runserver
/home/username/wikicamp/settings.pyc
DATABASES { 'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
'wiki.db', 'HOST': '', 'USER': '', 'PASSWORD':'', 'PORT':''}}
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

Those are the outputs after y


On Sun, Jan 23, 2011 at 10:11 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

>
>
> 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 output again. You may not
>> understand what we are looking for. Don't care about what the error is at
>> the point but the information that those print statements should have
>> output.
>>
>
> For the record, I would expect to see those print statements produce output
> at least twice. This is because settings.py actually gets imported multiple
> times. So, for example I see:
>
> Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
> Traceback (most recent call last):
>   File "manage.py", line 2, in 
> from django.core.management import execute_manager
> ImportError: No module named django.core.management
> Grumpys-MacBook-Pro:mysite graham$ source ../../bin/activate
> (django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py runserver
> /Library/WebServer/Sites/django-2/projects/mysite/settings.py
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> /Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> Validating models...
>
> 0 errors found
> Django version 1.3 beta 1, using settings 'mysite.settings'
> Development server is running at http://127.0.0.1:8000/
> Quit the server with CONTROL-C.
>
>
> ^C(django-2)Grumpys-MacBook-Pro:mysite graham$ python manage.py syncdb
> /Library/WebServer/Sites/django-2/projects/mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> /Library/WebServer/Sites/django-2/projects/mysite/../mysite/settings.pyc
> DATABASES {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME':
> '/Library/WebServer/Sites/django-2/db/database.db', 'HOST': '', 'USER': '',
> 'PASSWORD': '', 'PORT': ''}}
> Creating tables ...
> Installing custom SQL ...
> Installing indexes ...
> No fixtures found.
>
> Don't get me started on the multiple imports of settings.py file. :-(
>
> Graham
>
>
> On Monday, January 24, 2011 2:48:50 PM UTC+11, Kimberly wrote:
>>
>>> 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 

Re: Django Improper Configuration

[Kimberly Harvey]

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_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
379, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
line 191, in run_from_argv
self.exectured(*args, **options._dict_)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
220, in execute
output = self.handle(*args, **options)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py", line
351, in handle
   return self.handle_noargs(**options)
File
"/usr/lib/python2.5/site-packages/django/core/management/commands/syncdb.py",
line 52, in handle_noargs
cursor = connection.cursor()
File "/usr/lib/python2.5/site-packages/django/db/backends/dummy/base.py",
line 15, in complain
raise ImproperlyConfigured("You hav
en't set the database ENGINE setting yet.")


On Sun, Jan 23, 2011 at 9:54 PM, Steven Elliott Jr  wrote:

> 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
> you're going to need to know how to write python code if you're to get
> anywhere.
>
> It's definitely possible to learn both at the same time but I'd read
> through, and work through a few python tutorials first then come back to
> Django.
>
> I know this is probably not what you'd like to hear and it's just my two
> cents so...
>
> Anyway, keep posting and we will try to help.
>
> -Steven
>
> On Jan 23, 2011, at 10:40 PM, Graham Dumpleton 
> wrote:
>
> 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 you think it isn't.
>
> Graham
>
> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>>
>> it says that the _file_ is not defined.
>>
>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton 
>> 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 = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': 'database.db',
 'USER': '',
 'PASSWORD': '',
 'HOST': '',
 'PORT': '',
 }
 }

 it looks like in your configuration you are also missing a comma after
 the name of the database. Remember you must include that comma because this
 is a tuple.

>>>
>>> That was already pointed out to them.
>>>
>>> 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 may
>>> be modifying a different file to what is being read.
>>>
>>> I would like to see them, instead of changing DATABASES yet again, is to
>>> add at the very end of their settings.py file, the lines:
>>>
>>>   print __file__
>>>   print 'DATABASES', DATABASES
>>>
>>> This will prove two things. First that the file is being read as the
>>> output from this should show on stdout when running runserver or syncdb.
>>> Second, will show what Python is seeing DATABASES as being set to.
>>>
>>> if it doesn't show, then wrong file. If shows, but is different to what
>>> they believe they are setting it to, they could have multiple DATABASES
>>> entries in file.
>>>
>>> Graham
>>>
>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>> For more options, visit this group at
>>> 
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> 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-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> 

Re: Django Improper Configuration

[Kimberly Harvey]

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 Dumpleton <
graham.dumple...@gmail.com> wrote:

> 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 you think it isn't.
>
> Graham
>
>
> On Monday, January 24, 2011 2:35:06 PM UTC+11, Kimberly wrote:
>
>> it says that the _file_ is not defined.
>>
>> On Sun, Jan 23, 2011 at 9:28 PM, Graham Dumpleton 
>> 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 = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': 'database.db',
 'USER': '',
 'PASSWORD': '',
 'HOST': '',
 'PORT': '',
 }
 }

 it looks like in your configuration you are also missing a comma after
 the name of the database. Remember you must include that comma because this
 is a tuple.

>>>
>>> That was already pointed out to them.
>>>
>>> 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 may
>>> be modifying a different file to what is being read.
>>>
>>> I would like to see them, instead of changing DATABASES yet again, is to
>>> add at the very end of their settings.py file, the lines:
>>>
>>>   print __file__
>>>   print 'DATABASES', DATABASES
>>>
>>> This will prove two things. First that the file is being read as the
>>> output from this should show on stdout when running runserver or syncdb.
>>> Second, will show what Python is seeing DATABASES as being set to.
>>>
>>> if it doesn't show, then wrong file. If shows, but is different to what
>>> they believe they are setting it to, they could have multiple DATABASES
>>> entries in file.
>>>
>>> Graham
>>>
>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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 = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.sqlite3',
>> 'NAME': 'database.db',
>> 'USER': '',
>> 'PASSWORD': '',
>> 'HOST': '',
>> 'PORT': '',
>> }
>> }
>>
>> it looks like in your configuration you are also missing a comma after the
>> name of the database. Remember you must include that comma because this is a
>> tuple.
>>
>
> That was already pointed out to them.
>
> 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 may be
> modifying a different file to what is being read.
>
> I would like to see them, instead of changing DATABASES yet again, is to
> add at the very end of their settings.py file, the lines:
>
>   print __file__
>   print 'DATABASES', DATABASES
>
> This will prove two things. First that the file is being read as the output
> from this should show on stdout when running runserver or syncdb. Second,
> will show what Python is seeing DATABASES as being set to.
>
> if it doesn't show, then wrong file. If shows, but is different to what
> they believe they are setting it to, they could have multiple DATABASES
> entries in file.
>
> Graham
>
>  --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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 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, or
> whatever it is you must remember to save your work after you've made and
> edit.
>
>
> --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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.sqlite3',
> 'NAME': 'database.db',
>'USER': '',
>'PASSWORD': '',
>'HOST': '',
>'PORT': '',
>}
> }
>
> it looks like in your configuration you are also missing a comma after the
> name of the database. Remember you must include that comma because this is a
> tuple.
>
>
>
> --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

grah...@gmail.com>wrote:
>>>>>>
>>>>>>>  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', 'database.db'),
>>>>>>>  # Or path to database file if using sqlite3.
>>>>>>> 'USER': '',  # Not used with sqlite3.
>>>>>>> 'PASSWORD': '',  # Not used with sqlite3.
>>>>>>> 'HOST': '',  # Set to empty string for
>>>>>>> localhost. Not used with sqlite3.
>>>>>>> 'PORT': '',  # Set to empty string for
>>>>>>> default. Not used with sqlite3.
>>>>>>> }
>>>>>>> }
>>>>>>>
>>>>>>> This will allow everyone to see if you have mucked up some other part
>>>>>>> of the settings.
>>>>>>>
>>>>>>> Graham
>>>>>>>
>>>>>>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>>>>>>>
>>>>>>>>  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 <kmt...@gmail.com>wrote:
>>>>>>>>
>>>>>>>>>   On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey <
>>>>>>>>> kha...@gmail.com> 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 of settings for the 
>>>>>>>>> default
>>>>>>>>> database, not a single ENGINE line in settings.py. See:
>>>>>>>>>
>>>>>>>>> <http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases>
>>>>>>>>> http://docs.djangoproject.com/
>>>>>>>>> en/dev/ref/settings/?from=olddocs#databases
>>>>>>>>>
>>>>>>>>> for details.
>>>>>>>>>
>>>>>>>>> If you are using a Django version prior to 1.2, the setting you
>>>>>>>>> should be using is DATABASE_ENGINE (see
>>>>>>>>> <http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine>
>>>>>>>>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine),
>>>>>>>>> not just ENGINE.
>>>>>>>>>
>>>>>>>>> Karen
>>>>>>>>> --
>>>>>>>>> <http://tracey.org/kmt/>http://tracey.org/kmt/
>>>>>>>>>
>>>>>>>>>  --
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "Django users" group.
>>>>>>>>> To post to this group, send email to dja...@googlegroups.com.
>>>>>>>>> To unsubscribe from this group, send email to
>>>>>>>>> djan...@googlegroups.com.
>>>>>>>>>
>>>>>>>>> For more options, visit this group at
>>>>>>>>> <http://groups.google.com/group/django-users?hl=en>
>>>>>>>>> http://groups.google.com/group/django-users?hl=en.
>>>>>>>>>
>>>>>>>>
>>>>>>>>  --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "Django users" group.
>>>>>>> To post to this group, send email to dja...@googlegroups.com.
>>>>>>> To unsubscribe from this group, send email to
>>>>>>> djang...@googlegroups.com.
>>>>>>> For more options, visit this group at
>>>>>>> <http://groups.google.com/group/django-users?hl=en>
>>>>>>> http://groups.google.com/group/django-users?hl=en.
>>>>>>>
>>>>>>
>>>>>>  --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Django users" group.
>>>>> To post to this group, send email to djan...@googlegroups.com.
>>>>> To unsubscribe from this group, send email to
>>>>> django-...@googlegroups.com.
>>>>> For more options, visit this group at
>>>>> <http://groups.google.com/group/django-users?hl=en>
>>>>> http://groups.google.com/group/django-users?hl=en.
>>>>>
>>>>
>>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>> For more options, visit this group at
>>> <http://groups.google.com/group/django-users?hl=en>
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> 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-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>  --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

'PORT': '',  # Set to empty string for
>>>>>> default. Not used with sqlite3.
>>>>>> }
>>>>>> }
>>>>>>
>>>>>> Inside the settings.py file, in the template_dirs section, there's a
>>>>>> line says os.path.join(os.path.dirname(_file_), 'templates')
>>>>>>
>>>>>> If I comment that, then there's a error saying it doesn't recognize
>>>>>> _file_. I commented that line, then it says that the setting ENGINE has 
>>>>>> not
>>>>>> been set.
>>>>>>
>>>>>>
>>>>>> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
>>>>>> <grah...@gmail.com>wrote:
>>>>>>
>>>>>>>  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', 'database.db'),
>>>>>>>  # Or path to database file if using sqlite3.
>>>>>>> 'USER': '',  # Not used with sqlite3.
>>>>>>> 'PASSWORD': '',  # Not used with sqlite3.
>>>>>>> 'HOST': '',  # Set to empty string for
>>>>>>> localhost. Not used with sqlite3.
>>>>>>> 'PORT': '',  # Set to empty string for
>>>>>>> default. Not used with sqlite3.
>>>>>>> }
>>>>>>> }
>>>>>>>
>>>>>>> This will allow everyone to see if you have mucked up some other part
>>>>>>> of the settings.
>>>>>>>
>>>>>>> Graham
>>>>>>>
>>>>>>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>>>>>>>
>>>>>>>>  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 <kmt...@gmail.com>wrote:
>>>>>>>>
>>>>>>>>>   On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey <
>>>>>>>>> kha...@gmail.com> 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 of settings for the 
>>>>>>>>> default
>>>>>>>>> database, not a single ENGINE line in settings.py. See:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>>>>>>>>>
>>>>>>>>> for details.
>>>>>>>>>
>>>>>>>>> If you are using a Django version prior to 1.2, the setting you
>>>>>>>>> should be using is DATABASE_ENGINE (see
>>>>>>>>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine),
>>>>>>>>> not just ENGINE.
>>>>>>>>>
>>>>>>>>> Karen
>>>>>>>>> --
>>>>>>>>> http://tracey.org/kmt/
>>>>>>>>>
>>>>>>>>>  --
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "Django users" group.
>>>>>>>>> To post to this group, send email to dja...@googlegroups.com.
>>>>>>>>> To unsubscribe from this group, send email to
>>>>>>>>> djan...@googlegroups.com.
>>>>>>>>>
>>>>>>>>> For more options, visit this group at
>>>>>>>>> http://groups.google.com/group/django-users?hl=en.
>>>>>>>>>
>>>>>>>>
>>>>>>>>  --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "Django users" group.
>>>>>>> To post to this group, send email to dja...@googlegroups.com.
>>>>>>> To unsubscribe from this group, send email to
>>>>>>> djang...@googlegroups.com.
>>>>>>> For more options, visit this group at
>>>>>>> http://groups.google.com/group/django-users?hl=en.
>>>>>>>
>>>>>>
>>>>>>  --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Django users" group.
>>>>> To post to this group, send email to djan...@googlegroups.com.
>>>>> To unsubscribe from this group, send email to
>>>>> django-...@googlegroups.com.
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/group/django-users?hl=en.
>>>>>
>>>>
>>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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 ENGINE.
On Sun, Jan 23, 2011 at 8:19 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

> 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 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.d...@gmail.com>wrote:
>>
>>>
>>>
>>> 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', # Add
>>>> 'postgresql_psycopg2', 'postgresql', 'mysql', 'sqlite3' or 'oracle'.
>>>> 'NAME':  'home/username/directory/database'  #
>>>> Or path to database file if using sqlite3.
>>>>
>>>
>>> You deleted the comma after the string and missing leading slash on path.
>>> Try:
>>>
>>> 'NAME':  '/home/username/directory/database',  #
>>> Or path to database file if using sqlite3.
>>>
>>> Not sure how you didn't just get a syntax error.
>>>
>>> Graham
>>>
>>>
>>>> 'USER': '',  # Not used with sqlite3.
>>>> 'PASSWORD': '',  # Not used with sqlite3.
>>>> 'HOST': '',  # Set to empty string for
>>>> localhost. Not used with sqlite3.
>>>> 'PORT': '',  # Set to empty string for
>>>> default. Not used with sqlite3.
>>>> }
>>>> }
>>>>
>>>> Inside the settings.py file, in the template_dirs section, there's a
>>>> line says os.path.join(os.path.dirname(_file_), 'templates')
>>>>
>>>> If I comment that, then there's a error saying it doesn't recognize
>>>> _file_. I commented that line, then it says that the setting ENGINE has not
>>>> been set.
>>>>
>>>>
>>>> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
>>>> <graha...@gmail.com>wrote:
>>>>
>>>>>  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', 'database.db'),
>>>>># Or path to database file if using sqlite3.
>>>>> 'USER': '',  # Not used with sqlite3.
>>>>> 'PASSWORD': '',  # Not used with sqlite3.
>>>>> 'HOST': '',  # Set to empty string for
>>>>> localhost. Not used with sqlite3.
>>>>> 'PORT': '',  # Set to empty string for
>>>>> default. Not used with sqlite3.
>>>>> }
>>>>> }
>>>>>
>>>>> This will allow everyone to see if you have mucked up some other part
>>>>> of the settings.
>>>>>
>>>>> Graham
>>>>>
>>>>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>>>>>
>>>>>>  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 <kmt...@gmail.com>wrote:
>>>>>>
>>

Re: Django Improper Configuration

[Kimberly Harvey]

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 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'.
>> 'NAME':  'home/username/directory/database'  # Or
>> path to database file if using sqlite3.
>>
>
> You deleted the comma after the string and missing leading slash on path.
> Try:
>
> 'NAME':  '/home/username/directory/database',  # Or
> path to database file if using sqlite3.
>
> Not sure how you didn't just get a syntax error.
>
> Graham
>
>
>> 'USER': '',  # Not used with sqlite3.
>> 'PASSWORD': '',  # Not used with sqlite3.
>> 'HOST': '',  # Set to empty string for
>> localhost. Not used with sqlite3.
>> 'PORT': '',  # Set to empty string for
>> default. Not used with sqlite3.
>> }
>> }
>>
>> Inside the settings.py file, in the template_dirs section, there's a line
>> says os.path.join(os.path.dirname(_file_), 'templates')
>>
>> If I comment that, then there's a error saying it doesn't recognize
>> _file_. I commented that line, then it says that the setting ENGINE has not
>> been set.
>>
>>
>> On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton 
>> <graham.d...@gmail.com>wrote:
>>
>>> 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', 'database.db'),
>>>  # Or path to database file if using sqlite3.
>>> 'USER': '',  # Not used with sqlite3.
>>> 'PASSWORD': '',  # Not used with sqlite3.
>>> 'HOST': '',  # Set to empty string for
>>> localhost. Not used with sqlite3.
>>> 'PORT': '',  # Set to empty string for
>>> default. Not used with sqlite3.
>>> }
>>> }
>>>
>>> This will allow everyone to see if you have mucked up some other part of
>>> the settings.
>>>
>>> Graham
>>>
>>> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>>>
>>>> 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 <kmt...@gmail.com> wrote:
>>>>
>>>>>  On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey <kha...@gmail.com>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 of settings for the default
>>>>> database, not a single ENGINE line in settings.py. See:
>>>>>
>>>>>
>>>>> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>>>>>
>>>>> for details.
>>>>>
>>>>> If you are using a Django version prior to 1.2, the setting you should
>>>>> be using is DATABASE_ENGINE (see
>>>>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine),
>>>>> not just ENGINE.
>>>>>
>>>>> Karen
>>>>> --
>>>>> http://tracey.org/kmt/
>>>>>
>>>>>  --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Django users" group.
>>>

Re: Questions - Django -- Bash problem

[Kimberly Harvey]

By the way, it is Django 1.2.4 to be exact

On Sun, Jan 23, 2011 at 7:38 PM, Karen Tracey <kmtra...@gmail.com> wrote:

> On Sun, Jan 23, 2011 at 8:27 PM, Kimberly Harvey <kharve...@gmail.com>wrote:
>
>> Problems ( this is very frustrating!).
>>
>> In the settings.py file, I'm using the django 1.2 or higher, so it has
>> ENGINE : '", and whatsnot
>> I set the ENGINE to sqlite3, that didn't work. Then I added the path, and
>> that still doesn't work. It keeps saying that the ENGINE has not been set. I
>> have no clue what is wrong, I've gone through the tutorial so many times and
>> I feel that there must be something I am overlooking. I am using the Django
>> in the Linux-Debian. Please help, because Django is not cooperating with the
>> database and I have no clue what is going on other than the engine part but
>> that has been set.
>>
>>
> It might help if you copy/pasted the database settings portion from your
> settings.py file into your email to the group. You say you have taken it
> exactly from the tutorial but the error message is saying something else,
> and in such cases the error message is generally correct: really, the
> tutorial is not entirely broken so you have something that is not right but
> you have not given us enough information to help diagnose what it is. (That
> too is frustrating.)
>
> Also please indicate exactly what level of Django you are using. Why do you
> say 1.2 or higher?  That's what I said to indicate what level you need in
> order to use the settings syntax you appear to be using but you ought to
> know exactly what you are using, and be able to state that. The fact that
> you are saying 1.2 or higher instead of stating exactly what you are using
> does not give me confidence that you know what level you are using. One of
> the reasons you would be getting the error message you are reporting is if
> you are in fact using 1.1 but trying to use 1.2 syntax for the database
> settings.
>
> Karen
> --
> http://tracey.org/kmt/
>
>  --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Questions - Django -- Bash problem

[Kimberly Harvey]

Karen, I've already posted the result to the board. I am new to this Django
world so I do not have full confident with how all of this work. Just
started learning, so this is very new to me.

By the way, sorry that I did not post the result earlier along with my
frustration, I wasn't thinking, so I apologize once again. I am using Django
1.2 and to ensure that the Django has been installed, I run a test in the
shell and it exists.

On Sun, Jan 23, 2011 at 7:38 PM, Karen Tracey <kmtra...@gmail.com> wrote:

> On Sun, Jan 23, 2011 at 8:27 PM, Kimberly Harvey <kharve...@gmail.com>wrote:
>
>> Problems ( this is very frustrating!).
>>
>> In the settings.py file, I'm using the django 1.2 or higher, so it has
>> ENGINE : '", and whatsnot
>> I set the ENGINE to sqlite3, that didn't work. Then I added the path, and
>> that still doesn't work. It keeps saying that the ENGINE has not been set. I
>> have no clue what is wrong, I've gone through the tutorial so many times and
>> I feel that there must be something I am overlooking. I am using the Django
>> in the Linux-Debian. Please help, because Django is not cooperating with the
>> database and I have no clue what is going on other than the engine part but
>> that has been set.
>>
>>
> It might help if you copy/pasted the database settings portion from your
> settings.py file into your email to the group. You say you have taken it
> exactly from the tutorial but the error message is saying something else,
> and in such cases the error message is generally correct: really, the
> tutorial is not entirely broken so you have something that is not right but
> you have not given us enough information to help diagnose what it is. (That
> too is frustrating.)
>
> Also please indicate exactly what level of Django you are using. Why do you
> say 1.2 or higher?  That's what I said to indicate what level you need in
> order to use the settings syntax you appear to be using but you ought to
> know exactly what you are using, and be able to state that. The fact that
> you are saying 1.2 or higher instead of stating exactly what you are using
> does not give me confidence that you know what level you are using. One of
> the reasons you would be getting the error message you are reporting is if
> you are in fact using 1.1 but trying to use 1.2 syntax for the database
> settings.
>
> Karen
> --
> http://tracey.org/kmt/
>
>  --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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'.
'NAME':  'home/username/directory/database'  # Or
path to database file if using sqlite3.
'USER': '',  # Not used with sqlite3.
'PASSWORD': '',  # Not used with sqlite3.
'HOST': '',  # Set to empty string for
localhost. Not used with sqlite3.
'PORT': '',  # Set to empty string for default.
Not used with sqlite3.
}
}

Inside the settings.py file, in the template_dirs section, there's a line
says os.path.join(os.path.dirname(_file_), 'templates')

If I comment that, then there's a error saying it doesn't recognize _file_.
I commented that line, then it says that the setting ENGINE has not been
set.


On Sun, Jan 23, 2011 at 7:32 PM, Graham Dumpleton <
graham.dumple...@gmail.com> wrote:

> 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', 'database.db'),
># Or path to database file if using sqlite3.
> 'USER': '',  # Not used with sqlite3.
> 'PASSWORD': '',  # Not used with sqlite3.
> 'HOST': '',  # Set to empty string for
> localhost. Not used with sqlite3.
> 'PORT': '',  # Set to empty string for default.
> Not used with sqlite3.
> }
> }
>
> This will allow everyone to see if you have mucked up some other part of
> the settings.
>
> Graham
>
> On Monday, January 24, 2011 11:39:02 AM UTC+11, Kimberly wrote:
>
>> 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 <kmtr...@gmail.com> wrote:
>>
>>> On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey <khar...@gmail.com>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 of settings for the default
>>> database, not a single ENGINE line in settings.py. See:
>>>
>>> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>>>
>>> for details.
>>>
>>> If you are using a Django version prior to 1.2, the setting you should be
>>> using is DATABASE_ENGINE (see
>>> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), not
>>> just ENGINE.
>>>
>>> Karen
>>> --
>>> http://tracey.org/kmt/
>>>
>>>  --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To post to this group, send email to django...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> django-users...@googlegroups.com.
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-users?hl=en.
>>>
>>
>>  --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Questions - Django -- Bash problem

[Kimberly Harvey]

Problems ( this is very frustrating!).

In the settings.py file, I'm using the django 1.2 or higher, so it has
ENGINE : '", and whatsnot
I set the ENGINE to sqlite3, that didn't work. Then I added the path, and
that still doesn't work. It keeps saying that the ENGINE has not been set. I
have no clue what is wrong, I've gone through the tutorial so many times and
I feel that there must be something I am overlooking. I am using the Django
in the Linux-Debian. Please help, because Django is not cooperating with the
database and I have no clue what is going on other than the engine part but
that has been set.

2011/1/23 Łukasz Rekucki 

> On 23 January 2011 11:54, Kimberly  wrote:
> > Hello, I have another question. When it comes to Django, I notice some
> > people type as django-admin startproject project and some have to type
> > as django-admin.py startproject project ( in my case, I had to do
> > that), is it base on the setup of the Django that cause the
> > differences between the admin.py and admin?
>
> Django provides the script as "django-admin.py"; Some Linux
> distributions (like Ubuntu) package Django with the script renamed to
> "django-admin". So that's the cause of the difference and it's not
> something that Django has any influence on.
>
> >
> > Also, on the command line, I typed " manage.py startapp tolls"  after
> > being side my project directory and now it says bash: manage.py:
> > command not found
>
> Yes, because that's how bash works. If the script is not on PATH, then
> bash won't find it. If you want to run a script from current
> directory:
>
>./manage.py startapp tolls
>
> Note, that the file has to be executable, for this to work (it's not
> by default). That's why Django's tutorial suggests writing:
>
>python manage.py startapp tolls
>
> To avoid the need of explaining about bash, permission, etc.
>
> >
> > I've checked the directory I am using and the manage.py file is there.
> > I also set the _init_.py to where the operating system - os is
> > imported and that the django_setting_module is set to settings. Any
> > advices will be greatly appreciated. Thanks!
> >
>
> --
> Łukasz Rekucki
>
> --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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 <kmtra...@gmail.com> wrote:

> On Sun, Jan 23, 2011 at 6:47 PM, Kimberly Harvey <kharve...@gmail.com>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 of settings for the default
> database, not a single ENGINE line in settings.py. See:
>
> http://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#databases
>
> for details.
>
> If you are using a Django version prior to 1.2, the setting you should be
> using is DATABASE_ENGINE (see
> http://docs.djangoproject.com/en/1.1/ref/settings/#database-engine), not
> just ENGINE.
>
> Karen
> --
> http://tracey.org/kmt/
>
>  --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Improper Configuration

[Kimberly Harvey]

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 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Installing Django on Linux-Derbian using virtualBox on Windows 7 Machine

[Kimberly Harvey]

That is exactly what I am doing right now, I between the crawl and walk
phrase now, lol.

On Thu, Jan 20, 2011 at 9:23 PM, Mike Ramirez <gufym...@gmail.com> wrote:

>  On Thursday, January 20, 2011 07:09:10 pm Kimberly Harvey wrote:
>
> > Thanks for the tips and advices. I still believe Django can be run on the
>
> > linux-Debian version.
>
> No one is saying otherwise.
>
> > There are some updated Django which I've already
>
> > saved on my usb flash drive which I will soon run some commands on the
>
> > linux as some other people has advised me to do so. The person wants me
> to
>
> > learn more about django but NOT right away. However, I like to pick up on
>
> > things quick.
>
> Remember: Crawl, Walk, Run. Otherwise you're in for a hell of a time.
>
> Mike
>
>  --
>
> All generalizations are false, including this one.
>
> -- Mark Twain
>
>  --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Installing Django on Linux-Derbian using virtualBox on Windows 7 Machine

[Kimberly Harvey]

Thanks for the tips and advices. I still believe Django can be run on the
linux-Debian version. There are some updated Django which I've already saved
on my usb flash drive which I will soon run some commands on the linux as
some other people has advised me to do so. The person wants me to learn more
about django but NOT right away. However, I like to pick up on things quick.
I am getting the hang of some of the materials I've read but it takes some
time for me to fully grasp it since I am new to this. If any more advices
regarding to commands, let me know. Some people sent different commands on
how to install the Django/ Django-Python... I will test it out and see what
happens.

On Thu, Jan 20, 2011 at 7:40 PM, Kenneth Gonsalves
wrote:

> On Thu, 2011-01-20 at 22:58 +0100, Ivo Brodien wrote:
> > > But in order to do that, don't I need to have the Django source file
> > somewhere in my  computer/ or in my case.
> >
> > apt-get gets packages from the internet.
> >
> > And btw. Ubuntu is based on Debian.
>
> and btw, the django version in debian is too old to be of use
> --
> regards
> KG
> http://lawgon.livejournal.com
> Coimbatore LUG rox
> http://ilugcbe.techstud.org/
>
> --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Installing Django on Linux-Derbian using virtualBox on Windows 7 Machine

[Kimberly Harvey]

MY boss never mentioned about using the Ubuntu, just want me to use the
Debian.

Thanks

On Thu, Jan 20, 2011 at 3:58 PM, Ivo Brodien  wrote:

>
>
> > But in order to do that, don't I need to have the Django source file
> somewhere in my  computer/ or in my case.
>
> apt-get gets packages from the internet.
>
> And btw. Ubuntu is based on Debian.

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Installing Django on Linux-Derbian using virtualBox on Windows 7 Machine

[Kimberly Harvey]

I cannot install the Ubuntu, I have to use Derbian for work purposes.

On Thu, Jan 20, 2011 at 3:45 PM, Shawn Milochik <sh...@milochik.com> wrote:

> On 01/20/2011 04:40 PM, Kimberly Harvey wrote:
>
>> Right now, I am having problem with the installation of linux ( I will try
>> to figure that out if not, will contact you about that). I do have a problem
>> with installing the Django on Linux. I am new to the Django world, so I've
>> already downloaded the Django to my usb drive. Is there a certain way I have
>> to install it into Linux--Derbian? I also have Python 2.5.2 (before I've
>> installed linux), so do I also need a certain way to install python in linux
>> ( if it is not there)?
>>
>
> This list doesn't support Linux installations, but you shouldn't have much
> trouble with a modern distribution. If you have the freedom to do so, try
> installing Ubuntu instead of Debian.
>
> Once you get there, you'll be able to install Django using these docs:
> http://docs.djangoproject.com/en/1.2/intro/install/
>
> Shawn
>
>
> --
> 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-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Installing Django on Linux-Derbian using virtualBox on Windows 7 Machine

[Kimberly Harvey]

But in order to do that, don't I need to have the Django source file
somewhere in my  computer/ or in my case.. I've downloaded the Django tar
file to my usb flash drive? The command you gave me, that works in the linux
world, right? Like I said, I am new to this Djando materials.

On Thu, Jan 20, 2011 at 3:42 PM, Michael  wrote:

> You can probably just run "sudo apt-get install python-django" from the
> command line.
>
> --
> Michael 
>
> On Thu, 2011-01-20 at 13:26 -0800, Kimberly wrote:
> > Hello, I am new to the Django world and I was wondering if someone can
> > help me step by step on how to install the Django on my Linux program.
> > I've read some tutorial guides and I am abit lost and faced some
> > issues. I am currently on linux and need to know how to add packages,
> > and things in order to run the Django. Please contact me. Thanks!
> >
>
> --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Installing Django on Linux-Derbian using virtualBox on Windows 7 Machine

[Kimberly Harvey]

Right now, I am having problem with the installation of linux ( I will try
to figure that out if not, will contact you about that). I do have a problem
with installing the Django on Linux. I am new to the Django world, so I've
already downloaded the Django to my usb drive. Is there a certain way I have
to install it into Linux--Derbian? I also have Python 2.5.2 (before I've
installed linux), so do I also need a certain way to install python in linux
( if it is not there)?

On Thu, Jan 20, 2011 at 3:37 PM, Shawn Milochik  wrote:

> Exactly what have you tried, and where do you get stuck? What error message
> are you getting?
>
> --
> 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-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.