Re: ImportError at/ No module name

2012-12-24 Thread Ryan Blunden
Did this fix the problem for you?

Did you create the application using `python manage.py startapp blog`? If 
so, that would've created the blog 
applicationas
 a Python module. The __init__.py is required so Python knows to treat 
the directory containing the __int__.py as a 
module
.

You can also run `python manage.py validate` when debugging these sort of 
issues instead of running the local server as a faster feedback loop.

Let us know how you go.

Cheers,
Ryan

On Thursday, December 20, 2012 5:27:42 AM UTC-8, djangobie wrote:
>
> Hi, I have just started practicing a tutorial for buidling a  basic blog ( 
> http://www.djangorocks.com/tutorials/how-to-create-a-basic-blog-in-django/starting-your-application.html
>  )
>
> Did exactly the same (except, using 'djangopractice' as project name 
> instead of 'djangorocks')
> Actually It also did run twice, but than started showing ImportError.
>
> My files:
> 
> ***settings.py***
> 
> # Django settings for djangopractice project.
> #import os, django
> #DJANGO_ROOT = os.path.dirname(os.path.realpath(django.__file__))
> #SITE_ROOT = os.path.dirname(os.path.realpath('__file__'))
>
> DEBUG = True
> TEMPLATE_DEBUG = DEBUG
>
> ADMINS = (
> # ('Your Name', 'your_...@example.com '),
> )
>
> MANAGERS = ADMINS
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.mysql', # Add 'postgresql_psycopg2', 
> 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': 'djangopractice',  # Or path to 
> database file if using sqlite3.
> 'USER': 'root',  # Not used with sqlite3.
> 'PASSWORD': '1290',  # 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.
> }
> }
>
> # Local time zone for this installation. Choices can be found here:
> # http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
> # although not all choices may be available on all operating systems.
> # In a Windows environment this must be set to your system time zone.
> TIME_ZONE = 'Asia/Karachi'
>
> # Language code for this installation. All choices can be found here:
> # http://www.i18nguy.com/unicode/language-identifiers.html
> LANGUAGE_CODE = 'en-us'
>
> SITE_ID = 1
>
> # If you set this to False, Django will make some optimizations so as not
> # to load the internationalization machinery.
> USE_I18N = True
>
> # If you set this to False, Django will not format dates, numbers and
> # calendars according to the current locale.
> USE_L10N = True
>
> # If you set this to False, Django will not use timezone-aware datetimes.
> USE_TZ = True
>
> # Absolute filesystem path to the directory that will hold user-uploaded 
> files.
> # Example: "/home/media/media.lawrence.com/media/"
> MEDIA_ROOT = ''
>
> # URL that handles the media served from MEDIA_ROOT. Make sure to use a
> # trailing slash.
> # Examples: "http://media.lawrence.com/media/";, "http://example.com/media/
> "
> MEDIA_URL = ''
>
> # Absolute path to the directory static files should be collected to.
> # Don't put anything in this directory yourself; store your static files
> # in apps' "static/" subdirectories and in STATICFILES_DIRS.
> # Example: "/home/media/media.lawrence.com/static/"
> STATIC_ROOT = ''
>
> # URL prefix for static files.
> # Example: "http://media.lawrence.com/static/";
> STATIC_URL = '/static/'
>
> # Additional locations of static files
> STATICFILES_DIRS = (
> # Put strings here, like "/home/html/static" or "C:/www/django/static".
> # Always use forward slashes, even on Windows.
> # Don't forget to use absolute paths, not relative paths.
> )
>
> # List of finder classes that know how to find static files in
> # various locations.
> STATICFILES_FINDERS = (
> 'django.contrib.staticfiles.finders.FileSystemFinder',
> 'django.contrib.staticfiles.finders.AppDirectoriesFinder',
> #'django.contrib.staticfiles.finders.DefaultStorageFinder',
> )
>
> # Make this unique, and don't share it with anybody.
> SECRET_KEY = '@io!2+0*rw1o0tjq%t5zb8e$v(wf3p#yk_8#lb^%hrerzijwt1'
>
> # List of callables that know how to import templates from various sources.
> TEMPLATE_LOADERS = (
> 'django.template.loaders.filesystem.Loader',
> 'django.template.loaders.app_directories.Loader',
> # 'django.template.loaders.eggs.Loader',
> )
>
> MIDDLEWARE_CLASSES = (
> 'django.middleware.common.CommonMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.middleware.csrf.CsrfViewMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
> 'django.contrib.messages.middleware.MessageMiddleware',
> # Uncomment the next line for si

Append [RESOLVED] to your post subject if you got to a working solution

2012-12-24 Thread Ryan Blunden
Hi everyone,

After this very revealing 
post,
 
I want to do what I can to support new people coming to Django. 

Like many Django developers and supporters, I'm busy and so to make it as 
easy as possible to provide support in this forum, it would be great if you 
could *append [RESOLVED] to your post subject if you got to a working 
solution.*
*
*
This allows me and others to quickly scan the discussion list to see what 
needs attention.

Perhaps there is a better system I'm not aware of? Whatever it is, I just 
want to be able to provide help to those that need it in the most time 
efficient way possible.

Cheers,
Ryan

-- 
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/-/v2w_elHfeL8J.
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 ratings problem

2012-12-24 Thread Ryan Blunden
Can you share the error and the stack trace at http://pastie.org/.

Sharing environmental information such as OS, Python version, Django 
version, reported django-ratings app version is also critical in helping 
your figure out what the issue is.

Cheers,
Ryan

On Monday, December 24, 2012 10:35:44 AM UTC-8, sri wrote:
>
> Hi, 
>
>
> I am trying to add django-ratings to my app and it keeps falling over when 
> i try to add a rating. The steps i have followed is below 
>
> 1) pip install django-ratings 
>
> 2) Add 'djangoratings' to my settings.py 
>
> 3) Add a field in my model class with field name "cust_rating = 
> RatingField(range=5)"
>
>
> Now when i try to add a rating by adding the below line, system is 
> throwing an error.
>
>
> mymodel.cust_rating.add(score=int(4), user=request.user, 
> ip_address=request.META['REMOTE_ADDR'])
>
>
> Can anyone help with what i am missing?
>
>
> Thanks
>

-- 
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/-/ojF2nbxOTTUJ.
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: Append [RESOLVED] to your post subject if you got to a working solution

2012-12-25 Thread Ryan Blunden
True, it will break the thread if reading via email only.

Can you propose another way that when going to the groups posts page, you 
can scan and see which topics require further assistance? 

That is the problem I'm trying to solve.

On Tuesday, December 25, 2012 12:51:48 AM UTC-8, אברהם סרור wrote:
>
> I oppose adding [RESOLVED] to the subject, this means changing the subject 
> to a complete different string and detaching it from the thread. not sure 
> how this would work for google groups, but many people (me included) read 
> on gmail, it happened to me not long ago (can't remember which mailing list 
> it was), someone added a {RESOLVED] at the end of the subject, meaning I 
> got an email detached from the discussion.
>
> if someone would post a message after they got a solution they could just 
> add RESOLVED to the first line of the body and then post their conclusions 
> on how they got there. problem is that often people go silence when they 
> achieved the solution.
>
> also take in consideration that some posts are discussions like this one, 
> not answers to a specific problem.
>
> avraham
>
>
> On Tue, Dec 25, 2012 at 8:20 AM, Ryan Blunden 
> 
> > wrote:
>
>> Hi everyone,
>>
>> After this very revealing 
>> post<http://www.pythondiary.com/blog/Dec.22,2012/basically-dead-django-community.html>,
>>  
>> I want to do what I can to support new people coming to Django. 
>>
>> Like many Django developers and supporters, I'm busy and so to make it as 
>> easy as possible to provide support in this forum, it would be great if you 
>> could *append [RESOLVED] to your post subject if you got to a working 
>> solution.*
>> *
>> *
>> This allows me and others to quickly scan the discussion list to see what 
>> needs attention.
>>
>> Perhaps there is a better system I'm not aware of? Whatever it is, I just 
>> want to be able to provide help to those that need it in the most time 
>> efficient way possible.
>>
>> Cheers,
>> Ryan
>>
>> -- 
>> 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/-/v2w_elHfeL8J.
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/Vs-XR4tF3G0J.
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 1.4 manage.py cannot find settings

2012-12-25 Thread Ryan Blunden
I would say stay away using PyCharm to manage your Django application until 
you're more experienced. Learn to manage your app purely through the 
command line first.

On Tuesday, December 25, 2012 9:28:15 AM UTC-8, Victor Rocha wrote:
>
> Your welcome! Merry Christmas
>
>
>
> On Tue, Dec 25, 2012 at 12:25 PM, huw_at1 
> > wrote:
>
>> Hiya - sorry yeah I pasted the wrong manage.py file initially. It should 
>> have been the test.settings manage.py.
>>
>> I figured it out partially anyway - I needed to change the project 
>> directory setting in the IDE as you said.
>>
>> Thanks for the help.
>>
>>
>> On Tuesday, December 25, 2012 5:14:03 PM UTC, Victor Rocha wrote:
>>
>>> I don't think I can be of more help. Hopefully someone with experience 
>>> with PyCharm can chime in.
>>> This is probably not what you want to hear but ditch windows, ditch 
>>> pycharm use windows and vim or at least gedit.
>>>
>>> One last comment, in your manage.py file i can see this 'pkadata.settings'; 
>>> i didnt see that directory when you showed me your file structure.
>>>
>>>
>>>
>>> On Tue, Dec 25, 2012 at 12:01 PM, huw_at1  wrote:
>>>
 pkadata.settings
>>>
>>>
>>>  -- 
>> 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/-/xbeOEaE7Ah4J.
>>
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/FeHXglY42PAJ.
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: debugging issues with settings.py and database (postgres) and syncdb

2012-12-26 Thread Ryan Blunden
Are the user and password fields meant  to be blank?

Cheers,
Ryan

On Dec 26, 2012, at 9:40 AM, Dan Richards  wrote:

> First off, I am a newbie to django, python and postgres - so I suspect I am 
> missing something obvious, but I am stumped.  Any ideas will be gratefully 
> accepted...
> 
> I get the popular "Improperly configured settings.DATABASES" error message 
> when I run syncdb on my test app.  I am running:
> 
> django 1.4.3
> postgres 9.2
> MAC OS 10.6.8
> 
> I have verified that it is picking up the right settings.py file (the one in 
> the app subdirectory) so I assume there is either something wrong with the 
> settings I have entered or something wrong with postgres.  How does one debug 
> this??
> 
> I can connect to my database via psql, but nothing I have tried seems to work 
> and there seems to be very little I can do to actually debug what the problem 
> is...when the syncdb doesn't work, how do you debug to figure out what 
> exactly isn't working???
> 
> My settings.py file:
> 
> # Django settings for hellodjango project.
> 
> DEBUG = True
> TEMPLATE_DEBUG = DEBUG
> 
> ADMINS = (
> ('Joe Smith', 'jsm...@foobar.com'),
> )
> 
> MANAGERS = ADMINS
> 
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.postgresql_psycopg2', # Add 
> 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': 'test_db1',  # 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.
> }
> }
> 
> # Local time zone for this installation. Choices can be found here:
> # http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
> # although not all choices may be available on all operating systems.
> # In a Windows environment this must be set to your system time zone.
> TIME_ZONE = 'America/New_York'
> 
> # Language code for this installation. All choices can be found here:
> # http://www.i18nguy.com/unicode/language-identifiers.html
> LANGUAGE_CODE = 'en-us'
> 
> SITE_ID = 1
> 
> # If you set this to False, Django will make some optimizations so as not
> # to load the internationalization machinery.
> USE_I18N = True
> 
> # If you set this to False, Django will not format dates, numbers and
> # calendars according to the current locale.
> USE_L10N = True
> 
> # If you set this to False, Django will not use timezone-aware datetimes.
> USE_TZ = True
> 
> # Absolute filesystem path to the directory that will hold user-uploaded 
> files.
> # Example: "/home/media/media.lawrence.com/media/"
> MEDIA_ROOT = ''
> 
> # URL that handles the media served from MEDIA_ROOT. Make sure to use a
> # trailing slash.
> # Examples: "http://media.lawrence.com/media/";, "http://example.com/media/";
> MEDIA_URL = ''
> 
> # Absolute path to the directory static files should be collected to.
> # Don't put anything in this directory yourself; store your static files
> # in apps' "static/" subdirectories and in STATICFILES_DIRS.
> # Example: "/home/media/media.lawrence.com/static/"
> STATIC_ROOT = ''
> 
> # URL prefix for static files.
> # Example: "http://media.lawrence.com/static/";
> STATIC_URL = '/static/'
> 
> # Additional locations of static files
> STATICFILES_DIRS = (
> # Put strings here, like "/home/html/static" or "C:/www/django/static".
> # Always use forward slashes, even on Windows.
> # Don't forget to use absolute paths, not relative paths.
> )
> 
> # List of finder classes that know how to find static files in
> # various locations.
> STATICFILES_FINDERS = (
> 'django.contrib.staticfiles.finders.FileSystemFinder',
> 'django.contrib.staticfiles.finders.AppDirectoriesFinder',
> #'django.contrib.staticfiles.finders.DefaultStorageFinder',
> )
> 
> # Make this unique, and don't share it with anybody.
> SECRET_KEY = '3*a*mgk*)dcdyzi8v4#2%z^mt^63-uqq5g)q63)xy37ogcqxux'
> 
> # List of callables that know how to import templates from various sources.
> TEMPLATE_LOADERS = (
> 'django.template.loaders.filesystem.Loader',
> 'django.template.loaders.app_directories.Loader',
> # 'django.template.loaders.eggs.Loader',
> )
> 
> MIDDLEWARE_CLASSES = (
> 'django.middleware.common.CommonMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.middleware.csrf.CsrfViewMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
> 'django.contrib.messages.middleware.MessageMiddleware',
> # Uncomment the next line for simple clickjacking protection:
> # 'django.middleware.clickjacking.XFrameOptionsMiddleware',
> )
> 
> ROOT_URLCONF = 'hellodjango.urls'
> 
> # Python dotted path to the WSGI application used by Django's runserver.
> WSGI_APPLICATION = 'hellodj

Re: debugging issues with settings.py and database (postgres) and syncdb

2012-12-26 Thread Ryan Blunden
Ok. I would try setting the ENGINE value to *sqlite3* and try running *syncdb
*again. If that works (which it should), then we can presume it's a
configuration access problem with the DB.


On 26 December 2012 13:18, Dan Richards  wrote:

> NO, just me messing around that it made no difference.  I have the db
> access to all and trust and the error doesn't change no matter what I use
> there.  It feels like it could be a permissions problem, but I don't know
> how to track it down other than to verify I can access postgres via psql
> which I can do...
>
>
> On Wednesday, December 26, 2012 12:40:28 PM UTC-5, Dan Richards wrote:
>>
>> First off, I am a newbie to django, python and postgres - so I suspect I
>> am missing something obvious, but I am stumped.  Any ideas will be
>> gratefully accepted...
>>
>> I get the popular "Improperly configured settings.DATABASES" error
>> message when I run syncdb on my test app.  I am running:
>>
>> django 1.4.3
>> postgres 9.2
>> MAC OS 10.6.8
>>
>> I have verified that it is picking up the right settings.py file (the one
>> in the app subdirectory) so I assume there is either something wrong with
>> the settings I have entered or something wrong with postgres.  How does one
>> debug this??
>>
>> I can connect to my database via psql, but nothing I have tried seems to
>> work and there seems to be very little I can do to actually debug what the
>> problem is...when the syncdb doesn't work, how do you debug to figure out
>> what exactly isn't working???
>>
>> My settings.py file:
>>
>> # Django settings for hellodjango project.
>>
>> DEBUG = True
>> TEMPLATE_DEBUG = DEBUG
>>
>> ADMINS = (
>> ('Joe Smith', 'jsm...@foobar.com'),
>> )
>>
>> MANAGERS = ADMINS
>>
>> DATABASES = {
>> 'default': {
>> 'ENGINE': 'django.db.backends.**postgresql_psycopg2', # Add
>> 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
>> 'NAME': 'test_db1',  # 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.
>> }
>> }
>>
>> # Local time zone for this installation. Choices can be found here:
>> # 
>> http://en.wikipedia.org/wiki/**List_of_tz_zones_by_name
>> # although not all choices may be available on all operating systems.
>> # In a Windows environment this must be set to your system time zone.
>> TIME_ZONE = 'America/New_York'
>>
>> # Language code for this installation. All choices can be found here:
>> # 
>> http://www.i18nguy.com/**unicode/language-identifiers.**html
>> LANGUAGE_CODE = 'en-us'
>>
>> SITE_ID = 1
>>
>> # If you set this to False, Django will make some optimizations so as not
>> # to load the internationalization machinery.
>> USE_I18N = True
>>
>> # If you set this to False, Django will not format dates, numbers and
>> # calendars according to the current locale.
>> USE_L10N = True
>>
>> # If you set this to False, Django will not use timezone-aware datetimes.
>> USE_TZ = True
>>
>> # Absolute filesystem path to the directory that will hold user-uploaded
>> files.
>> # Example: 
>> "/home/media/media.lawrence.**com/media/
>> "
>> MEDIA_ROOT = ''
>>
>> # URL that handles the media served from MEDIA_ROOT. Make sure to use a
>> # trailing slash.
>> # Examples: 
>> "http://media.lawrence.com/**media/",
>> "http://example.com/media/";
>> MEDIA_URL = ''
>>
>> # Absolute path to the directory static files should be collected to.
>> # Don't put anything in this directory yourself; store your static files
>> # in apps' "static/" subdirectories and in STATICFILES_DIRS.
>> # Example: 
>> "/home/media/media.lawrence.**com/static/
>> "
>> STATIC_ROOT = ''
>>
>> # URL prefix for static files.
>> # Example: 
>> "http://media.lawrence.com/**static/
>> "
>> STATIC_URL = '/static/'
>>
>> # Additional locations of static files
>> STATICFILES_DIRS = (
>> # Put strings here, like "/home/html/static" or
>> "C:/www/django/static".
>> # Always use forward slashes, even on Windows.
>> # Don't forget to use absolute paths, not relative paths.
>> )
>>
>> # List of finder classes that know how to find static files in
>> # various locations.
>> STATICFILES_FINDERS = (
>> 'django.contrib.staticfiles.**finders.FileSystemFinder',
>> 'django.contrib.staticfiles.**finders.AppDirectoriesFinder',
>> #'django.contrib.staticfiles.**finders.DefaultStorageFinder',
>> )
>>
>> # Make this unique, and don't share it with anybody.
>> SECRET_KEY = '3*a*mgk*)dcdy

Re: Python shell doesn't launch

2012-12-26 Thread Ryan Blunden
That's Python's standard output when starting an interactive session.

On 26/12/2012, at 2:05 PM, rktur...@gmail.com wrote:

> Whenever I run "python manage.py shell," I don't get any errors, but  I get 
> the following:
> 
> C:\Python27\Lib\site-packages\django\bin\mysite>python manage.py shell
> Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] on 
> win
> 32
> Type "help", "copyright", "credits" or "license" for more information.
> (InteractiveConsole)
> 
> Any ideas on what am I doing or have done wrong?
> 
> 
> 
> -- 
> 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/-/cBacqTBYkgQJ.
> 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: Python shell doesn't launch

2012-12-26 Thread Ryan Blunden
Glad to be able to help.

I've got a few tips too :)

  - Use the excellent Django Extensions app which once you add it to your 
INSTALLED_APPS tuple, will allow you to run python manage.py shell_plus, which 
automatically imports all of the models for apps. This is great as it's not 
often that you want to use shell without importing some models at least.

Also, install iPython, it has great features (e.g. command history) that make 
it much friendlier than the standard interactive mode.

Cheers,
Ryan

On 26/12/2012, at 2:45 PM, rktur...@gmail.com wrote:

> You know what? I didn't "expect" anything because I HAVEN'T DONE THIS 
> BEFORE That is why I am doing an introductory tutorial. Thanks, Ramiro - 
> highly intelligent answer. Ryan - you are a professional.  
> 
> On Wednesday, December 26, 2012 5:05:10 PM UTC-5, rktu...@gmail.com wrote:
> Whenever I run "python manage.py shell," I don't get any errors, but  I get 
> the following:
> 
> C:\Python27\Lib\site-packages\django\bin\mysite>python manage.py shell
> Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] on 
> win
> 32
> Type "help", "copyright", "credits" or "license" for more information.
> (InteractiveConsole)
> 
> Any ideas on what am I doing or have done wrong?
> 
> 
> 
> -- 
> 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/-/_O0uxSfrIHIJ.
> 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: no Polls in the admin page

2012-12-26 Thread Ryan Blunden
Can you provide the contents of your admin.py in your polls app. If you've got 
the below code, then I'm not sure how that is happening.
class PollAdmin(admin.ModelAdmin):
fields = ['pub_date', 'question']

admin.site.register(Poll, PollAdmin)

Cheers,
Ryan

On 26/12/2012, at 11:09 AM, Kelketek Rritaa  wrote:

> I'm having precisely the same issue with precisely the same side effects. 
> Further, I am able to get output to my logs by adding a print statement to 
> the admin.py file. So I know it's being executed, it just doesn't show up in 
> the admin page. Running syncdb has not fixed it.
> 
> Has anyone found a solution to this? There obviously must be something else 
> that needs to be done, as all the other apps continue to hum along just fine 
> in the admin page.
> 
> On Thursday, November 1, 2012 1:59:18 PM UTC-5, Mihail Mihalache wrote:
> I have followed the django tutorial up to part 2 - 
> https://docs.djangoproject.com/en/1.4/intro/tutorial02/ .
> Everything worked fine, until I couldn't see the Polls entry on the admin 
> page. I have checked that I have done everything mentioned in the tutorial. 
> I get no error whatsoever. I have no idea what's wrong.
> There is a polls entry INSTALLED_APPS.
> 
> -- 
> 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/-/eQx6YFul_j4J.
> 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: no Polls in the admin page

2012-12-27 Thread Ryan Blunden
I'm not aware of any upstream apps 'masking' the display of other apps in the 
admin root page but I would try to disable all other third party (non-Django 
contrib) apps and see if that changes the result.

On 27/12/2012, at 6:46 AM, Kelketek Rritaa  wrote:

> I'd been trying several things to see if they'd work, so I went with the 
> absolute minimum that /should/ work:
> 
> from polls.models import Poll
> from django.contrib import admin
> admin.site.register(Poll)
> 
> Putting in the code you've given me does not work either.
> 
> HOWEVER, yesterday I was poking around with it quite a bit, and was able to 
> find out the following.
> 
> 1. Even though the polls app isn't showing on the index page, 
> admin/polls/poll/ works fine.
> 2. Admin does register the poll program:
> 
> In [1]: from django.contrib import admin
> 
> In [2]: import polls.admin
> 
> In [3]: admin.site._registry
> Out[3]: {polls.models.Poll: }
> 
> 3. It should be noted that this project is an already existing one I'm trying 
> to modify. Do you know if there's a way to 'mask' what applications end up on 
> the admin page? If so, this may have been enabled by the upstream for my 
> project, and I need to find a way to disable this.
> 
> On Wednesday, December 26, 2012 5:43:38 PM UTC-6, Ryan Blunden wrote:
> Can you provide the contents of your admin.py in your polls app. If you've 
> got the below code, then I'm not sure how that is happening.
> class PollAdmin(admin.ModelAdmin):
> fields = ['pub_date', 'question']
> 
> admin.site.register(Poll, PollAdmin)
> 
> Cheers,
> Ryan
> 
> On 26/12/2012, at 11:09 AM, Kelketek Rritaa  wrote:
> 
>> I'm having precisely the same issue with precisely the same side effects. 
>> Further, I am able to get output to my logs by adding a print statement to 
>> the admin.py file. So I know it's being executed, it just doesn't show up in 
>> the admin page. Running syncdb has not fixed it.
>> 
>> Has anyone found a solution to this? There obviously must be something else 
>> that needs to be done, as all the other apps continue to hum along just fine 
>> in the admin page.
>> 
>> On Thursday, November 1, 2012 1:59:18 PM UTC-5, Mihail Mihalache wrote:
>> I have followed the django tutorial up to part 2 - 
>> https://docs.djangoproject.com/en/1.4/intro/tutorial02/ .
>> Everything worked fine, until I couldn't see the Polls entry on the admin 
>> page. I have checked that I have done everything mentioned in the tutorial. 
>> I get no error whatsoever. I have no idea what's wrong.
>> There is a polls entry INSTALLED_APPS.
>> 
>> -- 
>> 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/-/eQx6YFul_j4J.
>> 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 view this discussion on the web visit 
> https://groups.google.com/d/msg/django-users/-/fTqX2fAFtY4J.
> 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: no Polls in the admin page

2012-12-27 Thread Ryan Blunden
Awesome! Glad you got it solved. 

On 27/12/2012, at 11:43 AM, Kelketek Titikilik Rritaa  
wrote:

> I found the issue. The issue appears to be in a template override for
> the Admin app that the upstream provider added. When this was moved
> out of the way, the standard template was loaded, and polls showed up.
> 
> On Thu, Dec 27, 2012 at 1:06 PM, Ryan Blunden  wrote:
>> I'm not aware of any upstream apps 'masking' the display of other apps in
>> the admin root page but I would try to disable all other third party
>> (non-Django contrib) apps and see if that changes the result.
>> 
>> On 27/12/2012, at 6:46 AM, Kelketek Rritaa  wrote:
>> 
>> I'd been trying several things to see if they'd work, so I went with the
>> absolute minimum that /should/ work:
>> 
>> from polls.models import Poll
>> from django.contrib import admin
>> admin.site.register(Poll)
>> 
>> Putting in the code you've given me does not work either.
>> 
>> HOWEVER, yesterday I was poking around with it quite a bit, and was able to
>> find out the following.
>> 
>> 1. Even though the polls app isn't showing on the index page,
>> admin/polls/poll/ works fine.
>> 2. Admin does register the poll program:
>> 
>> In [1]: from django.contrib import admin
>> 
>> In [2]: import polls.admin
>> 
>> In [3]: admin.site._registry
>> Out[3]: {polls.models.Poll: }
>> 
>> 3. It should be noted that this project is an already existing one I'm
>> trying to modify. Do you know if there's a way to 'mask' what applications
>> end up on the admin page? If so, this may have been enabled by the upstream
>> for my project, and I need to find a way to disable this.
>> 
>> On Wednesday, December 26, 2012 5:43:38 PM UTC-6, Ryan Blunden wrote:
>>> 
>>> Can you provide the contents of your admin.py in your polls app. If you've
>>> got the below code, then I'm not sure how that is happening.
>>> 
>>> class PollAdmin(admin.ModelAdmin):
>>>fields = ['pub_date', 'question']
>>> 
>>> admin.site.register(Poll, PollAdmin)
>>> 
>>> 
>>> Cheers,
>>> Ryan
>>> 
>>> On 26/12/2012, at 11:09 AM, Kelketek Rritaa  wrote:
>>> 
>>> I'm having precisely the same issue with precisely the same side effects.
>>> Further, I am able to get output to my logs by adding a print statement to
>>> the admin.py file. So I know it's being executed, it just doesn't show up in
>>> the admin page. Running syncdb has not fixed it.
>>> 
>>> Has anyone found a solution to this? There obviously must be something
>>> else that needs to be done, as all the other apps continue to hum along just
>>> fine in the admin page.
>>> 
>>> On Thursday, November 1, 2012 1:59:18 PM UTC-5, Mihail Mihalache wrote:
>>>> 
>>>> I have followed the django tutorial up to part 2 -
>>>> https://docs.djangoproject.com/en/1.4/intro/tutorial02/ .
>>>> Everything worked fine, until I couldn't see the Polls entry on the admin
>>>> page. I have checked that I have done everything mentioned in the tutorial.
>>>> I get no error whatsoever. I have no idea what's wrong.
>>>> There is a polls entry INSTALLED_APPS.
>>> 
>>> 
>>> --
>>> 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/-/eQx6YFul_j4J.
>>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msg/django-users/-/fTqX2fAFtY4J.
>> 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
>&g

Re: Admin page not found error

2012-12-28 Thread Ryan Blunden
It appears that the problem is to do with the Sites app.

Have you ran `python manage.py syncdb`? If the sites app is in the 
INSTALLED_APPS tuple, this takes care of creating a site for you that has an id 
of 1 which is what will match the default SITE_ID value in your settings.py

Things to try:

1) Comment out the sites app in INSTALLED_APPS

or

2) Ensure you have SITE_ID = 1in your settings and create a Site model entry 
with an id of 1. 

Cheers,
Ryan

On 28/12/2012, at 12:29 AM, Shahjalal Hossain  wrote:

> 
> 
> 
> Hi, I am new at Django. I am learning Django from instruction manual "a basic 
> poll application". I was doing step by step. But, at a certain point I 
> stacked. 
> 
> It does not shows admin page as "2.4 Writing your first Django app, part 2". 
> I have done all the steps, like uncomment settings.py and urls.py and run the 
> syncdb. I am writing on code on Aptana Studio 3. For convenient, I have given 
> some images. and source files.
> 
> Thanks, in advance.
> 
> settings.py
> 
> INSTALLED_APPS = (
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.sites',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> # Uncomment the next line to enable the admin:
> 'django.contrib.admin',
> # Uncomment the next line to enable admin documentation:
> # 'django.contrib.admindocs',
> 'polls',
> )
> 
> urls.py
> 
> from django.conf.urls import patterns, include, url
> 
> # Uncomment the next two lines to enable the admin:
> from django.contrib import admin 
> admin.autodiscover()
> 
> urlpatterns = patterns('',
> # Examples:
> # url(r'^$', 'mysite.views.home', name='home'),
> # url(r'^mysite/', include('mysite.foo.urls')),
> 
> # Uncomment the admin/doc line below to enable admin documentation:
> # url(r'^admin/doc/', include('django.contrib.admindocs.urls')),
> 
> # Uncomment the next line to enable the admin:
> url(r'^admin/', include(admin.site.urls)),
> )
> 
> 
> 
> 
> -- 
> 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/-/A_uLa0LzjUYJ.
> 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.



http://www.deploydjango.com/ - A good resource for advice on project structure and deployment

2012-12-28 Thread Ryan Blunden
I stumbled across http://www.deploydjango.com/ while looking for info on 
running New Relic monitoring for Django 1.45 in pure WSGI.

Looks like a good resource for people starting out with Django and looking 
for deployment guides.

-- 
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/-/mxarYnxMVjgJ.
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: Task/project management open source django application?

2012-12-28 Thread Ryan Blunden
That's the only app I could quickly find that's been taken to completion.

Unless you're wanting a plug-and-play solution like that, I would just create a 
todo-list app yourself. If you're not experienced in Django, there are plenty 
of tutorials out there for building one. If you go this route, be sure to check 
the Django version they use before you start (don't use anything below 1.3)

Cheers,
Ryan

On 28/12/2012, at 1:04 PM, Mark London  wrote:

> Hi - I'm looking for an open source project/task management system, based on 
> django.  Something like this one:
> 
> http://birdhouse.org/software/2008/09/django-todo/
> 
> Are there any others out there like this?  Thanks. 
> 
> - Mark 
> 
> 
> -- 
> 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/-/A1kZL3c8nckJ.
> 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: When I set DEBUG=False, my 404.html doesn't appear

2012-12-29 Thread Ryan Blunden
All I can suggest is to double-check the TEMPLATE_DIRS tuple to ensure the path 
is correct.

On 29/12/2012, at 7:59 AM, "Dae James"  wrote:

> I put my 404.html into root of the directory specified in TEMPLATE_DIRS. 
> However, when I visit an inexisting page, the browser's 404.html appears 
> rather than my own 404.html page.
> What's wrong with me ?
> PS: I've set the DEBUG variable in settings.py to False.
>  
> Dae James
> -- 
> 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: problem while passing a list of string to javascript in template

2012-12-29 Thread Ryan Blunden
Django presumes all template variables are "unsafe" by default to prevent XSS 
attacks which is why it's encoded the quotes.

Read up on filters and auto-escaping and you'll be able to figure out the rest.

Cheers,
Ryan

On 29/12/2012, at 7:57 AM, "Everest K.C."  wrote:

> Hello Everyone,
> I have problem while passing a list of string from django views to javascript 
> template. The quotation mark gets converted into hex and I cannot use it to 
> plot graph using jpplot. I even tried replace method of javascript to replace 
> the hex to convert to '. 
> 
> The codes are as follows:
> From views.py :
> from django.shortcuts import render_to_response
> 
> def abc(request):
>   s1=[1, 5 , 8 , 3]
>   ticks=["a", "b", "c", "d"]
>   return render_to_response('abc.html', {'s1':s1, 'ticks':ticks})
> 
> From .html file (of template):
>  $(document).ready(function(){
> $.jqplot.config.enablePlugins = true;
>var s1 ={{ s1 }}
>var ticks ={{ ticks }}
> plot1 = $.jqplot('chart1', [s1], {
> // Only animate if we're not using excanvas (not in IE 7 or IE 
> 8)..
> animate: !$.jqplot.use_excanvas,
> seriesDefaults:{
> renderer:$.jqplot.BarRenderer,
> pointLabels: { show: true }
> },
> axes: {
> xaxis: {
> renderer: $.jqplot.CategoryAxisRenderer,
> ticks: ticks
> }
> },
> highlighter: { show: false }
> });
> 
> $('#chart1').bind('jqplotDataClick', 
> function (ev, seriesIndex, pointIndex, data) {
> $('#info1').html('series: '+seriesIndex+', point: 
> '+pointIndex+', data: '+data);
> }
> );
> });
> 
> 
> when I view the source of the html file i get {{ ticks }} as
> ['a', 'b', 'c', 'd']
> 
> 
> -- 
> 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/-/mlgFT3rjmLQJ.
> 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: Problem with auto tests Get an error creating the test database: (1044, "Access denied for user 'viewbank_django'@'localhost' to database 'test_viewbank_django'")

2012-12-29 Thread Ryan Blunden
Hey Jeff,

There sure is. Just specify a "TEST_NAME" key in the database configuration 
dictionary and you're good to go.

https://docs.djangoproject.com/en/dev/topics/testing/overview/#the-test-database

Cheers,
Ryan

On 29/12/2012, at 7:27 AM, Jeff  wrote:

> When I run the command - "python manage.py test polls" I get the following 
> error - error creating the test database: (1044, "Access denied for user 
> 'viewbank_django'@'localhost' to database 'test_viewbank_django'")
> 
> I am using a shared server that will only allow me to create a database 
> prefixed with viewbank_.
> 
> Using the MYSQL client I can create viewbank_django_test or any variation I 
> like as long as it starts with viewbank_.
> 
> Is there a way to change the way django names the test database?
> 
> Thanks in advance
> Jeff
> 
> -- 
> 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/-/oxBvQnPWaJgJ.
> 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: Question about URL namespaces

2012-12-29 Thread Ryan Blunden
I've never used this feature but I believe it was created so that for a single 
Django project, you could provide multiple administration apps. For example, 
you might have one for customers and one for back office staff that expose 
different models, have different permissions etc.

So to answer your question about what "application" means in this context, it 
means a Django application (e.g. django.contrib.admin).

Cheers,
Ryan

On 29/12/2012, at 4:44 AM, "Dae James"  wrote:

> When I was reading django's URL document, I come across "URL namespaces".
> The raw sentence is "When you need to deploy multiple instances of a single 
> application, it can be helpful to be able to differentiate between instances."
> I'm very confused here. What the application here refer to? Does it mean  
> models ? Or something else I don't know?
> Thank you~~
>  
> Dae James
> -- 
> 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: Bug in inlines.js

2012-12-29 Thread Ryan Blunden
You should post this to https://code.djangoproject.com/newticket

Cheers,
Ryan

On 29/12/2012, at 12:50 AM, Ruud van der Weide  wrote:

> I just noticed a small bug in inlines.js. In the part where the "addButton" 
> is included, the following check is used:
> if ($this.attr("tagName") == "TR") {
> This check doesn't work as expected however. The attr-method reads an 
> attribute. "tagName" isn't an attribute. This check should be:
> if ($this.is("tr")) {
> 
> Due to this bug, the "Add another ..." link gets positioned weirdly when 
> using a TabularInline.
> 
> - Ruud
> 
> -- 
> 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/-/LmL4VKrIpPkJ.
> 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: Admin page not found error

2012-12-29 Thread Ryan Blunden
I added a record to the django_site table (which Django on the first syncdb run 
for the Sites app) and then I could view the admin fine.

So you can either try this or just delete the sqlite.db file and run syncdb 
again which will also fix the problem.

Also, you don't need to specify the database path as an absolute path. It's 
relative to the Django project root folder so just "sqlite.db" would be fine.

Happy coding.

Cheers,
Ryan

On 29/12/2012, at 12:14 AM, Shahjalal Hossain  wrote:

> 
> 
> On Friday, December 28, 2012 9:29:50 AM UTC+1, Shahjalal Hossain wrote:
> 
> 
> 
> 
> 
> 
> 
> Hi, I am new at Django. I am learning Django from instruction manual "a basic 
> poll application". I was doing step by step. But, at a certain point I 
> stacked. 
> 
> It does not shows admin page as "2.4 Writing your first Django app, part 2". 
> I have done all the steps, like uncomment settings.py and urls.py and run the 
> syncdb. I am writing on code on Aptana Studio 3. For convenient, I have given 
> some images. and source files.
> 
> Thanks, in advance.
> 
> settings.py
> 
> INSTALLED_APPS = (
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.sites',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> # Uncomment the next line to enable the admin:
> 'django.contrib.admin',
> # Uncomment the next line to enable admin documentation:
> # 'django.contrib.admindocs',
> 'polls',
> )
> 
> urls.py
> 
> from django.conf.urls import patterns, include, url
> 
> # Uncomment the next two lines to enable the admin:
> from django.contrib import admin 
> admin.autodiscover()
> 
> urlpatterns = patterns('',
> # Examples:
> # url(r'^$', 'mysite.views.home', name='home'),
> # url(r'^mysite/', include('mysite.foo.urls')),
> 
> # Uncomment the admin/doc line below to enable admin documentation:
> # url(r'^admin/doc/', include('django.contrib.admindocs.urls')),
> 
> # Uncomment the next line to enable the admin:
> url(r'^admin/', include(admin.site.urls)),
> )
> 
> 
> 
> 
> -- 
> 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/-/mW2jgtuPr_gJ.
> 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: Access denied for user

2012-12-29 Thread Ryan Blunden
You either need to create an account for this user with access to the database 
or check the username and password provided.

How are you administering the DB? PHPMyAdmin?

On 27/12/2012, at 6:22 AM, El sayed Gamal  wrote:

> You need to change your mysql database configurations, that's is it.
> 
> On Thursday, December 27, 2012 3:45:58 PM UTC+2, Sanket Garg wrote:
> i m trying to follow the following guide
> 
> https://docs.djangoproject.com/en/1.3/intro/tutorial01/
> 
> but i m getting error
> ERROR 1045 (28000): Access denied for user 'Sanket'@'localhost' (using 
> password: YES)
> 
> do i need to login in as superuser or something? i m stuck :/
> 
> -- 
> 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/-/F-R0nE018soJ.
> 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: Using django-profiles app twice in one project.

2012-12-29 Thread Ryan Blunden
The AUTH_PROFILE_MODULE functionality is being deprecated in Django 1.5 in 
favour of being able to create your own custom User models. It sounds like that 
would be the way to go, especially as the 1.5 release is just around the corner 
and trunk is normally rock solid.

Cheers,
Ryan

On 27/12/2012, at 6:01 AM, Bill Freeman  wrote:

> 
> 
> On Thu, Dec 27, 2012 at 12:51 AM, Mark Shervey  wrote:
> I'm trying to use three different instances of the django-profiles app in one 
> project (developed here: https://bitbucket.org/ubernostrum/django-profiles).  
> I can make the whole thing work fine with one instance, but when I create the 
> three different instances with different names, I get this error:  "Exception 
> Value:   Unable to load the profile model, check AUTH_PROFILE_MODULE in your 
> project settings."  Is there a way to create thee different 
> AUTH_PROFILE_MODULE settings?
> 
> I know this is probably not the best practice, but it's something we need to 
> hack for now
> 
> I'm able to get django-profiles 
> (https://bitbucket.org/ubernostrum/django-profiles) working fine as one app 
> (vendor), but when I try to run two apps (vendor and coordinator) I get this 
> error: "Exception Value:   Unable to load the profile model, check 
> AUTH_PROFILE_MODULE in your project settings.".  I know it's because I need 
> this variable to point at the profile app, but is there a way that I can 
> either 1) Point it two places, or 2) create a new variable for it to resolve 
> to?
> 
> 
> Perhaps if you explained why you need three different profile apps, we could 
> offer another way to go.
> 
> The design of the profile stuff only offers one known connection between User 
> and a profile model.
> 
> I'm going to guess that you are looking to have three categories of 
> membership, with different sets of fields.  There are two ways that I see:
> 
>   1. A single profile model with all the fields, plus either a member_type 
> choice field, of several booleans indicating whether this member has those 
> features (lets a member live in more that one category if that's desirable).  
> Then all the views have to be careful to show (or allow editing of) only what 
> the given member type should be able to see.  The downside is that the admin 
> as it stands will not be suitable for the less technical manager, but even 
> this can be fixed with a custom template for this admin (though I tend to 
> like specific non-admin profile management views when things get this 
> squirrelly - often already useful to let users manage certain fields of their 
> own profiles).
> 
>   2. Write your own profile feature that can choose among several distinct 
> profile models and monkey patch it in so that any needed additional app that 
> finds profile from user in the standard way gets your chosen profile instance.
> 
> Bill
> 
> Note: use of the term "monkey patch" is intentionally pejorative.
> 
> 
> -- 
> 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: Actions after logout

2012-12-29 Thread Ryan Blunden
When you say you haver a "process in place", do you mean code sitting in a file?

If you haven't already, create a logout url and hook it up to your code to 
delete the log out data. Then just call django.contrib.auth.logout() somewhere 
in your logout view.

Cheers,
Ryan

On 27/12/2012, at 6:50 AM, 4 The good Life we work <4thegdl...@googlemail.com> 
wrote:

> Hallo,
> 
> I would like to delete certain data + login data after logout.
> 
> I have a process in place and would like to delete the
> data inserted if the process is not followed to the last step.
> 
> Thanks for your support,
> Michael
> 
> -- 
> 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: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-29 Thread Ryan Blunden
Can you provide a single example of one of the fixture objects you're trying to 
import, as well as the model it corresponds to?

On 29/12/2012, at 11:34 AM, Sam Raker  wrote:

> Hello,
> I've got a very tight deadline, and I'm encountering a very frustrating 
> problem. Every time I try to use loaddata to load my data into my database, I 
> get the loaddata error in the subject. I've tried YAML, I've tried JSON, I've 
> tried excerpting only a few lines of each, all to no avail. I'm really at my 
> rope's end. I don't think my models are flawed in any significant way--each 
> refers to only one field in one other model (the primary key in four out of 
> five of them). 
> 
> I need to get this working by the 2nd, and I've looked all over the internet 
> and posted a question at Stackoverflow and still can't figure it out. I 
> really need some help.
> 
> Thanks,
> -sam
> 
> -- 
> 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/-/WLBxL9nsC1IJ.
> 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.



Django 1.7 - What are you most excited about?

2014-07-29 Thread Ryan Blunden
Hi everyone,

I'm giving a lightening talk at the San Francisco Django meetup tomorrow 
night about some of the awesome new features in Django 1.7.

I wanted to highlight not just what *I think* are the best new features, 
but what members of the community are most excited about.

Would be great to hear from the Django core contributors too.

Thanks also Django Devs for getting RC 2 up in time for my talk, brilliant 
timing there!

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/afb4376a-853d-46df-8db3-e37e5740d91b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django 1.7 - What are you most excited about?

2014-07-30 Thread Ryan Blunden
Hi Carlos,

I’ve read all the release notes and already have my short list of what I think 
the best features are. But this will be heavily skewed towards the types of 
Django apps I create and how I use Django.

I wanted to know what the Django community thought were the best new features.

Speaking of which, which is your favorite new feature?  


On Tuesday, July 29, 2014 at 7:08 PM, carlos wrote:

> Hi maybe you need read the release note Django 1.7 about the new features
> https://docs.djangoproject.com/en/dev/releases/1.7/
>  
> Cheers :)
>  
>  
> On Tue, Jul 29, 2014 at 7:31 PM, Ryan Blunden  (mailto:ryan.blun...@gmail.com)> wrote:
> > Hi everyone,
> >  
> > I'm giving a lightening talk at the San Francisco Django meetup tomorrow 
> > night about some of the awesome new features in Django 1.7.  
> >  
> > I wanted to highlight not just what I think are the best new features, but 
> > what members of the community are most excited about.
> >  
> > Would be great to hear from the Django core contributors too.  
> >  
> > Thanks also Django Devs for getting RC 2 up in time for my talk, brilliant 
> > timing there!  
> >  
> > --  
> > 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 
> > (mailto:django-users+unsubscr...@googlegroups.com).
> > To post to this group, send email to django-users@googlegroups.com 
> > (mailto:django-users@googlegroups.com).
> > Visit this group at http://groups.google.com/group/django-users.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/django-users/afb4376a-853d-46df-8db3-e37e5740d91b%40googlegroups.com
> >  
> > (https://groups.google.com/d/msgid/django-users/afb4376a-853d-46df-8db3-e37e5740d91b%40googlegroups.com?utm_medium=email&utm_source=footer).
> > For more options, visit https://groups.google.com/d/optout.
>  
> --  
> 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 
> (mailto:django-users+unsubscr...@googlegroups.com).
> To post to this group, send email to django-users@googlegroups.com 
> (mailto:django-users@googlegroups.com).
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CAM-7rO1np13wV_vnuWSCmqeA9oaksdD1MnZFnQz7K2qpNP0yyQ%40mail.gmail.com
>  
> (https://groups.google.com/d/msgid/django-users/CAM-7rO1np13wV_vnuWSCmqeA9oaksdD1MnZFnQz7K2qpNP0yyQ%40mail.gmail.com?utm_medium=email&utm_source=footer).
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/91F231DB9F5B470BA3A6A9B99D49A7BB%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django 1.7 - What are you most excited about?

2014-07-30 Thread Ryan Blunden
Thanks Marc and Russ for your replies, greatly appreciated.

Here are my favorites:

App Loading
Applications can run code at startup, before Django does anything else, with 
the ready() method of their configuration.
Apps now don’t need a models.py to be a valid app.
Applications can be given a verbose_name for the admin.
autodiscover() no longer needed, Django calls this automatically.


System check framework
./manage.py check. Many times, validate would pass but the app would crash once 
started. I’ve noticed this to be much more robust.


Admin
You can now implement site_header, site_title, and index_title attributes on a 
custom AdminSite in order to easily change the admin site’s page title and 
header text. No more needing to override templates!
@register decorator to register a ModelAdmin.
ModelAdmin.list_display_links = None to disable links on the change list page 
grid.


Auth
django.contrib.auth.views.password_reset() takes an optional 
html_email_template_name parameter used to send a multipart HTML email for 
password resets.


Email
send_mail() now accepts an html_message parameter for sending a multipart 
text/plain and text/html email.


Managers
Better Managers by subleasing QuerySet and using query set.as_manager()


Templates
The new truncatechars_html filter truncates a string to be no longer than the 
specified number of characters, taking HTML into account.  


Requests and responses
The new JsonResponse subclass  






On Wednesday, July 30, 2014 at 9:41 AM, Ryan Blunden wrote:

> Hi Carlos,
>  
> I’ve read all the release notes and already have my short list of what I 
> think the best features are. But this will be heavily skewed towards the 
> types of Django apps I create and how I use Django.
>  
> I wanted to know what the Django community thought were the best new features.
>  
> Speaking of which, which is your favorite new feature?  
>  
> On Tuesday, July 29, 2014 at 7:08 PM, carlos wrote:
>  
> > Hi maybe you need read the release note Django 1.7 about the new features
> > https://docs.djangoproject.com/en/dev/releases/1.7/
> >  
> > Cheers :)
> >  
> >  
> > On Tue, Jul 29, 2014 at 7:31 PM, Ryan Blunden  > (mailto:ryan.blun...@gmail.com)> wrote:
> > > Hi everyone,
> > >  
> > > I'm giving a lightening talk at the San Francisco Django meetup tomorrow 
> > > night about some of the awesome new features in Django 1.7.  
> > >  
> > > I wanted to highlight not just what I think are the best new features, 
> > > but what members of the community are most excited about.
> > >  
> > > Would be great to hear from the Django core contributors too.  
> > >  
> > > Thanks also Django Devs for getting RC 2 up in time for my talk, 
> > > brilliant timing there!  
> > >  
> > > --  
> > > 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 
> > > (mailto:django-users+unsubscr...@googlegroups.com).
> > > To post to this group, send email to django-users@googlegroups.com 
> > > (mailto:django-users@googlegroups.com).
> > > Visit this group at http://groups.google.com/group/django-users.
> > > To view this discussion on the web visit 
> > > https://groups.google.com/d/msgid/django-users/afb4376a-853d-46df-8db3-e37e5740d91b%40googlegroups.com
> > >  
> > > (https://groups.google.com/d/msgid/django-users/afb4376a-853d-46df-8db3-e37e5740d91b%40googlegroups.com?utm_medium=email&utm_source=footer).
> > > For more options, visit https://groups.google.com/d/optout.
> >  
> > --  
> > 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 
> > (mailto:django-users+unsubscr...@googlegroups.com).
> > To post to this group, send email to django-users@googlegroups.com 
> > (mailto:django-users@googlegroups.com).
> > Visit this group at http://groups.google.com/group/django-users.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/django-users/CAM-7rO1np13wV_vnuWSCmqeA9oaksdD1MnZFnQz7K2qpNP0yyQ%40mail.gmail.com
> >  
> > (https://groups.google.com/d/msgid/django-users/CAM-7rO1np13wV_vnuWSCmqeA9oaksdD1MnZFnQz7K2qpNP0yyQ%40mail.gmail.com?utm_medium=email&utm_source=footer).
> > For more options, visit https://groups.google.com/d/optout.
>

Re: Access to custom fields in view?

2014-07-30 Thread Ryan Blunden
I would use the @property decorator.

class template(models.Model):
... 
 
@property
def responsive(self):

try:
responsive = templates_propiedad.objects.get(propiedad="features", 
valor="responsive", plantilla=self)
salida = "1"
except:
salida = "0"
return salida

@property
def engine(self):
try:
engine = 
templates_propiedad.objects.get(propiedad="prestashop-compatibility", 
plantilla=self)
salida = engine.valor
except:
salida = "0"
return salida

On Wednesday, July 30, 2014 at 11:02 AM, Miguel Angel Yáñez Camacho wrote:

> Hi all from spain and sorry for my bad english ;)
>  
> Hi a have in this model 2 custom fields: "responsive" and "engine"
>  
> class template(models.Model):
> state = models.IntegerField()  # estado del template 1= activo, 0= 
> inactivo
> tid = models.IntegerField(primary_key=True)
> price = models.IntegerField()  # precio unidad
> priceexc = models.IntegerField()  # precio exclusivo
> inserted_date = models.DateTimeField(null=True, blank=True)
> update_date = models.DateTimeField(null=True, blank=True)
> live_preview_url = models.CharField(max_length=1000, null=True, 
> blank=True)
> tipo = models.ForeignKey(tipo)
> keywords = models.CharField(max_length=9000, null=True, blank=True)
> screen_preview_s = models.CharField(max_length=1000, null=True, 
> blank=True)
> screen_preview_l = models.CharField(max_length=1000, null=True, 
> blank=True)
> origen = models.ForeignKey(origen)
> url_compra = models.CharField(max_length=1000, null=True, blank=True)
> promocionada = models.BooleanField(default=False)
> portada = models.BooleanField(default=False)
>  
> def __unicode__(self):
> return self.live_preview_url
>  
> def _get_responsive(self):
>  
> try:
> responsive = 
> templates_propiedad.objects.get(propiedad="features", valor="responsive", 
> plantilla=self)
> salida = "1"
> except:
> salida = "0"
> return salida
> responsive = property(_get_responsive)
>  
> def _get_engine(self):
> try:
> engine = 
> templates_propiedad.objects.get(propiedad="prestashop-compatibility", 
> plantilla=self)
> salida = engine.valor
> except:
> salida = "0"
> return salida
>  
> engine = property(_get_engine)
> in my view in this code i can access to a regular field but i CANT access to 
> custom fields, give me error
> plantillas_db = 
> templates_keyword.objects.select_related('plantilla').filter(keyword=bd_keywordsfinal,
>  plantilla__state='1', 
> plantilla__promocionada=False).distinct().order_by('-plantilla__inserted_date')
>  
> s = set(plantillas_db)
> for i in s:
> print(i.id)
> print(i.responsive)
> print(i.engine)
> How can i access to this fields?
> thanks
>  
> Miguel
> --  
> 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 
> (mailto:django-users+unsubscr...@googlegroups.com).
> To post to this group, send email to django-users@googlegroups.com 
> (mailto:django-users@googlegroups.com).
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/6177a2f8-f2d7-4b88-bc83-fc2d9bccf284%40googlegroups.com
>  
> (https://groups.google.com/d/msgid/django-users/6177a2f8-f2d7-4b88-bc83-fc2d9bccf284%40googlegroups.com?utm_medium=email&utm_source=footer).
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5ABC7736D24A460AB3DCD6207E103EE4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Djamin, a new and clean styles for Django admin.

2014-08-01 Thread Ryan Blunden
This looks pretty clean. I’ll give it a try on a new Django app I’m developing. 
  

Have you tested it on Django 1.7?  


On Friday, August 1, 2014 at 11:13 AM, Herson wrote:

> Hey guys, in the last days, i push my new project called Djamin[0], a new and 
> clean styles for django admin.
>  
> I hope you like and i sent in django dev tool for a proposal to change.  
>  
> Forken, commit and send suggestions, all are welcome.
>  
> [0] https://github.com/hersonls/djamin
>  
> --  
> Herson Leite, Software Developer
> www.hersonls.com.br (http://www.hersonls.com.br)
> --  
> 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 
> (mailto:django-users+unsubscr...@googlegroups.com).
> To post to this group, send email to django-users@googlegroups.com 
> (mailto:django-users@googlegroups.com).
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CA%2BdbW11d2ZYeqHVYDjA1c-0Xx31nThgNjWAt%3Du9FVsuxOWTFqw%40mail.gmail.com
>  
> (https://groups.google.com/d/msgid/django-users/CA%2BdbW11d2ZYeqHVYDjA1c-0Xx31nThgNjWAt%3Du9FVsuxOWTFqw%40mail.gmail.com?utm_medium=email&utm_source=footer).
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/EE78BEAF6E5E43CD9D66FB81CBBC2C0C%40gmail.com.
For more options, visit https://groups.google.com/d/optout.