date:20130425

Re: ImproperlyConfigured: Requested setting USE_I18N, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before access

2013-04-25 Thread Iftikhar Ali



> but while testing and pychecker i am getting this error how should i 
> configure DJANGO_SETTINGS_MODULE
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Getting error on first step of tutorial

2013-04-25 Thread A. Dias

Hey Dennis! 

Have you figured out an answer for that one yet? cause i'm dealing with the 
exact same error and it would be great if you had a solution for it!

Cheers,
Alex

Terça-feira, 9 de Abril de 2013 7:03:28 UTC+1, mill...@telusplanet.net 
escreveu:
>
> I'm new to web frameworks and am trying the Django tutorial (
> https://docs.djangoproject.com/en/1.5/intro/tutorial01/)
>
> Environment:
>   Windows 7 64 bi
>   Python 2.7 32 bit
>
> Installed Django V1.5.1 with (not using virtualenv):
>   pip install --upgrade django
>
> Get 'Successfully installed Django' message
>
> Then followed the tutorial instructions and cd into my trial directory 
> called tmp,
> then create base application using:
>   django-admin.py startproject mysite
>
> Resulted in the expected creation of:
>  mysite/
>  manage.py
>  mysite/
>  __init__.py
>  settings.py
>  uls.py
>  wsgi.py
>
> Then cd into outer mysite directory and use:
>   python manage.py runserver
>
> This gives the following traceback:
>
> Validating models...
>
> Unhandled exception in thread started by  of  ds.runserver.Command object at 0x03008C90>>
> Traceback (most recent call last):
>   File 
> "c:\python27\lib\site-packages\django\core\management\commands\runserver.py", 
> line 92, in inner_run
> self.validate(display_num_errors=True)
>   File "c:\python27\lib\site-packages\django\core\management\base.py", 
> line 280, in validate
> num_errors = get_validation_errors(s, app)
>   File 
> "c:\python27\lib\site-packages\django\core\management\validation.py", line 
> 35, in get_validation_errors
> for (app_name, error) in get_app_errors().items():
>   File "c:\python27\lib\site-packages\django\db\models\loading.py", line 
> 166, in get_app_errors
> self._populate()
>   File "c:\python27\lib\site-packages\django\db\models\loading.py", line 
> 72, in _populate
> self.load_app(app_name, True)
>   File "c:\python27\lib\site-packages\django\db\models\loading.py", line 
> 96, in load_app
> models = import_module('.models', app_name)
>   File "c:\python27\lib\site-packages\django\utils\importlib.py", line 35, 
> in import_module
> __import__(name)
>   File "c:\python27\lib\site-packages\django\contrib\auth\models.py", line 
> 370, in 
> class AbstractUser(AbstractBaseUser, PermissionsMixin):
>   File "c:\python27\lib\site-packages\django\db\models\base.py", line 213, 
> in __new__
> new_class.add_to_class(field.name, copy.deepcopy(field))
>   File "c:\python27\lib\site-packages\django\db\models\base.py", line 265, 
> in add_to_class
> value.contribute_to_class(cls, name)
>   File 
> "c:\python27\lib\site-packages\django\db\models\fields\__init__.py", line 
> 257, in contribute_to_class
> cls._meta.add_field(self)
>   File "c:\python27\lib\site-packages\django\db\models\options.py", line 
> 179, in add_field
> self.local_fields.insert(bisect(self.local_fields, field), field)
>   File "c:\python27\lib\functools.py", line 56, in 
> '__lt__': [('__gt__', lambda self, other: other < self),
>   File "c:\python27\lib\functools.py", line 56, in 
> '__lt__': [('__gt__', lambda self, other: other < self),
>
> .
> .
> almost 500 repetitions until recursion depth error
> .
> .
>   
>   File "c:\python27\lib\functools.py", line 56, in 
> '__lt__': [('__gt__', lambda self, other: other < self),
> RuntimeError: maximum recursion depth exceeded in cmp
>
>
> Any ideas about what is wrong, or other tests I can do?
>
> Thanks,
> Dennis
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

How can I completely remove Django and reinstall it - I've broken something

2013-04-25 Thread Garry Pettet

I'm a complete newcomer to Python and the Django framework so please be 
gentle.

I'm on a Mac 10.8 and MAMP. I was following the tutorial and installed the 
latest stable version (1.5) of Django using pip thanks to the instructions 
on this 
page.
 
For some reason, I decided immediately after this to install instead the 
development version (1.6dev) by cloning the git repository using these 
instructions.
 
At this point, everything was OK and running the following code:

>>> import django
>>> print(django.get_version())


printed out version 1.6dev-blahblahblah.

I then tried to create my first project with this command:

django-admin.py startproject mysite


It worked. Here's where I did something stupid. I changed my mind at this 
point and thought it might be better to stick with the stable development 
version rather than the bleeding edge version and so I tried to remove the 
development version. All I did was delete the django folder found after 
typing this command:

python -c "import sys; sys.path = sys.path[1:]; import django; 
print(django.__path__)"


I then reran pip and it said everything was installed correctly. When I get 
the version number from the Python interpreter I get this output:

>>> import django
>>> print(django.get_version())
1.5.1


However, when I try to create a new project I get the following error:

django-admin.py startproject mysite
Traceback (most recent call last):
  File "/usr/local/bin/django-admin.py", line 4, in 
from pkg_resources import require; 
require('Django==1.6.dev20130425172216')
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py",
 
line 2607, in 
parse_requirements(__requires__), Environment()
  File 
"/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py",
 
line 565, in resolve
raise DistributionNotFound(req)  # XXX put more info here
pkg_resources.DistributionNotFound: Django==1.6.dev20130425172216
Garrys-MacBook-Air-2:~ Garry$ 

Sorry for being stupid but how can I fix this??

Thanks

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How can I divide a page into multiple parts using multiple html files and django templates?

2013-04-25 Thread Nikolas Stevenson-Molnar

I'm not sure I understand your end goal. You /can/ extend your includes,
you'd just include the extended template. E.g.:

sidenav_base.html


sidenav_specific.html
{% extends "sidenav_base.html" %}


base.html
{% include "sidenav_specific.html" %}

Or if you're then extending base.html and want a different side nav,
then put that last bit in a block:
{% block sidenav %}
{% include "sidenav_base.html" %}
{% endblock %}

And then in your subclass of base.html:
{% extends "base.html" %}
{% block sidenav %}
{% include "sidenav_specific.html" %}
{% endblock %}

_Nik

On 4/25/2013 5:13 PM, bilgehan.bal...@gmail.com wrote:
> Let us assume that I have 5 files like this that are included by
> base.html via "include". How would I then extend each of those? Looks
> like once you include a couple pages, you have no way of extending
> them each, because you have to render one child template.
>
> Perhaps the best practice is to mix multiple views into one page, but
> I have no experience with django so I don't know.
>
> Bahadir
>
> On Thursday, April 25, 2013 12:22:52 PM UTC-7, Nikolas
> Stevenson-Molnar wrote:
>
> The include would probably help you here:
> https://docs.djangoproject.com/en/1.5/ref/templates/builtins/#include
> 
>
>
> _Nik
>
> On 4/25/2013 11:56 AM, bilgeha...@gmail.com  wrote:
> > Hi,
> >
> > I want to divide a page into parts, such as sidenav.html,
> topnav.html
> > and so on such that the base.html is not cluttered with details
> of the
> > complex topnav or sidebar. Problem is Django template
> inheritence can
> > only have one to one parent child relationship and I cannot have
> > multiple html child templateslike this. What would be the best
> way to
> > go with this?
> >
> > Some of my examples:
> >
> > sidebar.html
> > {% extends "base.html" %}
> > {% block sidebar %{
> > 
> > {% endblock %}
> >
> > head.html
> > {% extends "base.html" %}
> > {% block head %{
> > 
> > {% endblock %}
> >
> > topnav.html
> > {% extends "base.html" %}
> > {% block topnav %{
> > 
> > {% endblock %}
> >
> >
> > ... and  base.html as simple as below:
> > {% load staticfiles %}
> > 
> > {% block head %}{% endblock head %}
> > 
> > {% block topnav %}{% endblock topnav %}
> > {% block container %}{% endblock container %}
> > {% block sidebar %}{% endblock sidebar %}
> > 
> > 
> >
> > If what I am doing above is not best practice, what is the best
> > practice to divide pages into concepts like this? This is just the
> > beginning, essentially I want to insert more levels into this
> > hierarchy, encapsulating details in different levels so that it
> is a
> > maintainable program.
> >
> > Thanks,
> > Bahadir
> > --
> > 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...@googlegroups.com .
> > To post to this group, send email to django...@googlegroups.com
> .
> > Visit this group at
> http://groups.google.com/group/django-users?hl=en
> .
> > For more options, visit https://groups.google.com/groups/opt_out
> .
> >  
> >  
>
> -- 
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Unexpected Server Error (500) in tutorial

2013-04-25 Thread Mike Dewhirst


On 26/04/2013 3:41am, dsmakear...@gmail.com wrote:

I am running python 3.3.1, django-dev, Windows 7,





When I Set DEBUG=False, I then get "Server Error (500)" not 404.

With some experimentation, I discovered that if I set DEBUG=False the
tutorial app appears to always fail with Server Error 500. As a test, I
went back to tutorial part 1. created a new minimal project, confirmed
that it worked, then set DEBUG=False. and voila I get Server Error (500)
again.


Try launching your browser at http://localhost:8000/admin instead of 
127.0.0.1:8000 and make sure 'localhost' is in ALLOWED_HOSTS.


That should make the 500 error go away when DEBUG == False

Mike



That is:

  * DEBUG = True, in debug mode - the code works without error
  * DEBUG = False, in production mode - the code fails Server Error (500)

Aside from my setting DEBUG to False, this is all django generated code.

I am a django newbie, but this feels like a bug.

Checking the IRC archives I see more than one question about cryptic
Server Error (500) occurrences.

Comments?




--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How can I divide a page into multiple parts using multiple html files and django templates?

2013-04-25 Thread bilgehan . balban

Let us assume that I have 5 files like this that are included by base.html 
via "include". How would I then extend each of those? Looks like once you 
include a couple pages, you have no way of extending them each, because you 
have to render one child template.

Perhaps the best practice is to mix multiple views into one page, but I 
have no experience with django so I don't know.

Bahadir

On Thursday, April 25, 2013 12:22:52 PM UTC-7, Nikolas Stevenson-Molnar 
wrote:
>
> The include would probably help you here: 
> https://docs.djangoproject.com/en/1.5/ref/templates/builtins/#include 
>
> _Nik 
>
> On 4/25/2013 11:56 AM, bilgeha...@gmail.com  wrote: 
> > Hi, 
> > 
> > I want to divide a page into parts, such as sidenav.html, topnav.html 
> > and so on such that the base.html is not cluttered with details of the 
> > complex topnav or sidebar. Problem is Django template inheritence can 
> > only have one to one parent child relationship and I cannot have 
> > multiple html child templateslike this. What would be the best way to 
> > go with this? 
> > 
> > Some of my examples: 
> > 
> > sidebar.html 
> > {% extends "base.html" %} 
> > {% block sidebar %{ 
> >  
> > {% endblock %} 
> > 
> > head.html 
> > {% extends "base.html" %} 
> > {% block head %{ 
> >  
> > {% endblock %} 
> > 
> > topnav.html 
> > {% extends "base.html" %} 
> > {% block topnav %{ 
> >  
> > {% endblock %} 
> > 
> > 
> > ... and  base.html as simple as below: 
> > {% load staticfiles %} 
> >  
> > {% block head %}{% endblock head %} 
> >  
> > {% block topnav %}{% endblock topnav %} 
> > {% block container %}{% endblock container %} 
> > {% block sidebar %}{% endblock sidebar %} 
> >  
> >  
> > 
> > If what I am doing above is not best practice, what is the best 
> > practice to divide pages into concepts like this? This is just the 
> > beginning, essentially I want to insert more levels into this 
> > hierarchy, encapsulating details in different levels so that it is a 
> > maintainable program. 
> > 
> > Thanks, 
> > Bahadir 
> > -- 
> > 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...@googlegroups.com . 
> > To post to this group, send email to 
> > django...@googlegroups.com. 
>
> > Visit this group at http://groups.google.com/group/django-users?hl=en. 
> > For more options, visit https://groups.google.com/groups/opt_out. 
> >   
> >   
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Unexpected Server Error (500) in tutorial

2013-04-25 Thread Mike Dewhirst


On 26/04/2013 8:32am, dsmakear...@gmail.com wrote:

  That probably means the tutorial can't really demonstrate 404.html,
500.html, or 403.html  customization.



If you are getting 500 errors you should be able to see your own 
500.html displayed.





On Thursday, April 25, 2013 6:24:37 PM UTC-4, dsmak...@gmail.com wrote:

Thanks.

--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Unexpected Server Error (500) in tutorial

2013-04-25 Thread dsmakearney

 That probably means the tutorial can't really demonstrate 404.html, 
500.html, or 403.html  customization. 



On Thursday, April 25, 2013 6:24:37 PM UTC-4, dsmak...@gmail.com wrote:
>
> Thanks.

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Unexpected Server Error (500) in tutorial

2013-04-25 Thread dsmakearney

Thanks.

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cant syncdb with postgresql

2013-04-25 Thread Pedro Silva

i  already try it, no success, i think app its fine, its something with 
postgresql... 2 days ago i was able to sync, create.. db since yesterday 
its jus give that msg.
i already uninstall python and django, reinstall and get same erro. Still 
works fine with sqlite3, when i change the db... fails
its something with heroku i guess. i just copy and past the db configs from 
heroku.

Quinta-feira, 25 de Abril de 2013 16:47:06 UTC+1, Daniele Procida escreveu:
>
> On Thu, Apr 25, 2013, Pedro Silva > 
> wrote: 
>
> >installed apps: 
> >'django.contrib.auth', 
> >'django.contrib.contenttypes', 
> >'django.contrib.sessions', 
> >'django.contrib.messages', 
> >'django.contrib.staticfiles', 
> >'django.contrib.admin', 
> >'django.contrib.admindocs', 
> >'psycopg2.extensions', 
> >#my app 
> >'meetpop.meet', 
> >#more info at https://code.google.com/p/gsettings/wiki/API 
> >'meetpop.gsettings', 
> >#django logging view helper 
> >'django-log-file-viewer', 
> >#custom template tags 
> >'meetpop.meet.templatetags', 
> > 
> >its fresh, i can create a fresh sqllite db with no probs. 
>
> I would suggest trying it with only the django.contrib apps, and nothing 
> else. 
>
> If that doesn't work, then I don't know what to suggest. 
>
> Daniele 
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How can I divide a page into multiple parts using multiple html files and django templates?

2013-04-25 Thread Nikolas Stevenson-Molnar

The include would probably help you here:
https://docs.djangoproject.com/en/1.5/ref/templates/builtins/#include

_Nik

On 4/25/2013 11:56 AM, bilgehan.bal...@gmail.com wrote:
> Hi,
>
> I want to divide a page into parts, such as sidenav.html, topnav.html
> and so on such that the base.html is not cluttered with details of the
> complex topnav or sidebar. Problem is Django template inheritence can
> only have one to one parent child relationship and I cannot have
> multiple html child templateslike this. What would be the best way to
> go with this?
>
> Some of my examples:
>
> sidebar.html
> {% extends "base.html" %}
> {% block sidebar %{
> 
> {% endblock %}
>
> head.html
> {% extends "base.html" %}
> {% block head %{
> 
> {% endblock %}
>
> topnav.html
> {% extends "base.html" %}
> {% block topnav %{
> 
> {% endblock %}
>
>
> ... and  base.html as simple as below:
> {% load staticfiles %}
> 
> {% block head %}{% endblock head %}
> 
> {% block topnav %}{% endblock topnav %}
> {% block container %}{% endblock container %}
> {% block sidebar %}{% endblock sidebar %}
> 
> 
>
> If what I am doing above is not best practice, what is the best
> practice to divide pages into concepts like this? This is just the
> beginning, essentially I want to insert more levels into this
> hierarchy, encapsulating details in different levels so that it is a
> maintainable program.
>
> Thanks,
> Bahadir
> -- 
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

How can I divide a page into multiple parts using multiple html files and django templates?

2013-04-25 Thread bilgehan . balban

Hi,

I want to divide a page into parts, such as sidenav.html, topnav.html and 
so on such that the base.html is not cluttered with details of the complex 
topnav or sidebar. Problem is Django template inheritence can only have one 
to one parent child relationship and I cannot have multiple html child 
templateslike this. What would be the best way to go with this?

Some of my examples:

sidebar.html
{% extends "base.html" %}
{% block sidebar %{

{% endblock %}

head.html
{% extends "base.html" %}
{% block head %{

{% endblock %}

topnav.html
{% extends "base.html" %}
{% block topnav %{

{% endblock %}


... and  base.html as simple as below:
{% load staticfiles %}

{% block head %}{% endblock head %}

{% block topnav %}{% endblock topnav %}
{% block container %}{% endblock container %}
{% block sidebar %}{% endblock sidebar %}



If what I am doing above is not best practice, what is the best practice to 
divide pages into concepts like this? This is just the beginning, 
essentially I want to insert more levels into this hierarchy, encapsulating 
details in different levels so that it is a maintainable program.

Thanks,
Bahadir

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Problem with creating a one-to-one instance

2013-04-25 Thread Carsten Fuchs


Hi Tom,

Am 2013-04-25 18:53, schrieb Tom Evans:

Yes, this is correct, when you assign an object to a foreign key, it
must already be saved so that it has an id in order to persist in the
database.


It's very good to hear this, thank you very much for your reply!


In 1.4, the check is not present:
https://github.com/django/django/blob/stable/1.4.x/django/db/models/fields/related.py#L259
So I guess you're using 1.4!


No, I'm using 1.5.1 (sorry for not having mentioned this earlier), but didn't get any 
exception, exactly as shown in my original mail.


Thanks to your pointers into the code, I tested a bit more, and it seems that my case is 
not handled in class SingleRelatedObjectDescriptor, but in class 
ReverseSingleRelatedObjectDescriptor -- which I don't understand, but can easily trigger 
the assertion in line


https://github.com/django/django/blob/1.5.1/django/db/models/fields/related.py#L405

by a statement like   ma.vbp = SomeOtherClass()

The __set__ method in ReverseSingleRelatedObjectDescriptor does not seem to have an 
equivalent to the check in SingleRelatedObjectDescriptor, so this explains why I could 
do the original assignment   ma.vbp = Vorblendplan()


Best regards,
Carsten

--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Unexpected Server Error (500) in tutorial

2013-04-25 Thread C. Kirby

Django 1.5 made a change with 
https://docs.djangoproject.com/en/1.5/releases/1.5/#allowed-hosts-required-in-production

"The new 
ALLOWED_HOSTSsetting
 validates the request’s Host header and protects against 
host-poisoning attacks. This setting is now required whenever 
DEBUGis 
False, or else 
django.http.HttpRequest.get_host()will
 raise 
SuspiciousOperation.
 
For more details see the full 
documentationfor
 the new setting."

Full ALLWED_HOSTS documentation
https://docs.djangoproject.com/en/1.5/ref/settings/#std:setting-ALLOWED_HOSTS

On Thursday, April 25, 2013 12:41:12 PM UTC-5, dsmak...@gmail.com wrote:
>
> I am running python 3.3.1, django-dev, Windows 7,
>
> dev version of tutorial part 3 -
>  Customizing Error Views  
>  The 404 (page not found) view
>
> The suggested code works as expected though I have some quibbles about 
> documentation wording.
>
> BUT...
>
> When in settings.py DEBUG= True, django prints the stack trace plus a note 
> advising that this view is displayed because DEBUG is set to True.
>
> In settings.py, I see:
> # SECURITY WARNING: don't run with debug turned on in production!
> DEBUG = True
>
> Makes sense, besides I have created a 404.html and put it in the right 
> place, and I want to see it displayed
>
> When I Set DEBUG=False, I then get "Server Error (500)" not 404.
>
> With some experimentation, I discovered that if I set DEBUG=False the 
> tutorial app appears to always fail with Server Error 500. As a test, I 
> went back to tutorial part 1. created a new minimal project, confirmed that 
> it worked, then set DEBUG=False. and voila I get Server Error (500) again.
>
> That is:
>
>- DEBUG = True, in debug mode - the code works without error
>- DEBUG = False, in production mode - the code fails Server Error (500)
>
> Aside from my setting DEBUG to False, this is all django generated code.
>
> I am a django newbie, but this feels like a bug.  
>
> Checking the IRC archives I see more than one question about cryptic 
> Server Error (500) occurrences.
>
> Comments?
>
>
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Unexpected Server Error (500) in tutorial

2013-04-25 Thread dsmakearney

I am running python 3.3.1, django-dev, Windows 7,

dev version of tutorial part 3 -
 Customizing Error Views  
 The 404 (page not found) view

The suggested code works as expected though I have some quibbles about 
documentation wording.

BUT...

When in settings.py DEBUG= True, django prints the stack trace plus a note 
advising that this view is displayed because DEBUG is set to True.

In settings.py, I see:
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True

Makes sense, besides I have created a 404.html and put it in the right 
place, and I want to see it displayed

When I Set DEBUG=False, I then get "Server Error (500)" not 404.

With some experimentation, I discovered that if I set DEBUG=False the 
tutorial app appears to always fail with Server Error 500. As a test, I 
went back to tutorial part 1. created a new minimal project, confirmed that 
it worked, then set DEBUG=False. and voila I get Server Error (500) again.

That is:

   - DEBUG = True, in debug mode - the code works without error
   - DEBUG = False, in production mode - the code fails Server Error (500)
   
Aside from my setting DEBUG to False, this is all django generated code.

I am a django newbie, but this feels like a bug.  

Checking the IRC archives I see more than one question about cryptic Server 
Error (500) occurrences.

Comments?




-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Running into Unicode Decode Error when using django-admin.py startproject.

2013-04-25 Thread Eric Nielsen

I am brand new to Django and I am having a big problem right off the bat. I
cannot use startproject to begin my web app. When I use this command:

/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django/bin/django-admin.py

startproject cms

I get this error:

"UnicodeDecodeError: 'utf8' codec can't decode byte 0xb0 in position 37:
invalid start byte"

and then it doesn't create the web app. I have not even done any
programming and it seems like this is something that is wrong with the
Django files, but I am really confused as how their own files would have a
character not in the English language that would be making this error. I
have been searching online and I have found people with Unicode Decode
Errors, but not any during this specific step and I have not been able to
find an answer so far. I am running Django on a Mac with Snow Leopard and
am using the stable version of Django with Python 2.7. I have been trying
to figure this out for a while now and I just keep hitting walls, I would
really like to try Django. Thanks for any help!

--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Problem with creating a one-to-one instance

2013-04-25 Thread Tom Evans

On Thu, Apr 25, 2013 at 4:55 PM, Carsten Fuchs  wrote:
> Hi all,
> […]
> In the example that works (in my original mail, not quoted here), when the
> assignment is done, the Vorblendplan instance already has an id, so that it
> is properly carried into ma.vbp_id.
>
> Can someone confirm this, is my understanding correct?

Yes, this is correct, when you assign an object to a foreign key, it
must already be saved so that it has an id in order to persist in the
database. The code that does this is here:

https://github.com/django/django/blob/master/django/db/models/fields/related.py#L208

This is master, and you can see there is now a check in there - line
235 in master - that would have raised an exception in your example
(the check is also in 1.5).

In 1.4, the check is not present:

https://github.com/django/django/blob/stable/1.4.x/django/db/models/fields/related.py#L259

So I guess you're using 1.4!

Cheers

Tom

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Problem with creating a one-to-one instance

2013-04-25 Thread Carsten Fuchs


Hi all,

Am 16.04.2013 17:50, schrieb Carsten Fuchs:

I'm probably overlooking something very simple, but still cannot explain
what the code below does wrong: [...]

 >>> ma = Mitarbeiter.objects.get(key="F426")
 >>> ma.vbp  # ok, initially "None"
 >>> ma.vbp = Vorblendplan()
 >>> ma.vbp.save()
 >>> ma.save()

 >>> ma = Mitarbeiter.objects.get(key="F426")
 >>> ma.vbp  # Why still "None"??


I guess it's because the assignment

ma.vbp = Vorblendplan()

also updates ma.vbp_id (None), and is not updated in the subsequent

ma.vbp.save()

so that subsequently:

>>> ma.vbp.id
4741
>>> ma.vbp_id
# Still None


In the example that works (in my original mail, not quoted here), when 
the assignment is done, the Vorblendplan instance already has an id, so 
that it is properly carried into ma.vbp_id.


Can someone confirm this, is my understanding correct?

Best regards,
Carsten

--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cant syncdb with postgresql

2013-04-25 Thread Tom Evans

On Thu, Apr 25, 2013 at 3:59 PM, Pedro Silva  wrote:
> installed apps:
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> 'django.contrib.admin',
> 'django.contrib.admindocs',
> 'psycopg2.extensions',
> #my app
> 'meetpop.meet',
> #more info at https://code.google.com/p/gsettings/wiki/API
> 'meetpop.gsettings',
> #django logging view helper
> 'django-log-file-viewer',
> #custom template tags
> 'meetpop.meet.templatetags',
>
> its fresh, i can create a fresh sqllite db with no probs.
>

Comment out all apps except for those starting "django.".
Run syncdb
Re-enable one app
Re-run syncdb
Repeat

Which one does it crash on?

Cheers

Tom

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cant syncdb with postgresql

2013-04-25 Thread Daniele Procida

On Thu, Apr 25, 2013, Pedro Silva  wrote:

>installed apps:
>'django.contrib.auth',
>'django.contrib.contenttypes',
>'django.contrib.sessions',
>'django.contrib.messages',
>'django.contrib.staticfiles',
>'django.contrib.admin',
>'django.contrib.admindocs',
>'psycopg2.extensions',
>#my app
>'meetpop.meet',
>#more info at https://code.google.com/p/gsettings/wiki/API
>'meetpop.gsettings',
>#django logging view helper
>'django-log-file-viewer',
>#custom template tags 
>'meetpop.meet.templatetags',
>
>its fresh, i can create a fresh sqllite db with no probs.

I would suggest trying it with only the django.contrib apps, and nothing else.

If that doesn't work, then I don't know what to suggest.

Daniele 

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cant syncdb with postgresql

2013-04-25 Thread Pedro Silva

no luck with that

Quinta-feira, 25 de Abril de 2013 14:27:31 UTC+1, Timothy Makobu escreveu:
>
> You need to catch exceptions during a commit and rollback the incomplete 
> transaction.
>
> from django.db import connection
> connection._rollback()
>
> to rollback the current one.
>
>
> On Thu, Apr 25, 2013 at 4:08 PM, Pedro Silva 
> 
> > wrote:
>
>> I cant sync db with heroku postgresql, with sqllite works great.
>> Can anybody help me?
>> requeriments:
>> Django==1.4.5
>> PIL==1.1.7
>> distribute==0.6.36
>> dj-database-url==0.2.1
>> django-db-log==2.2.1
>> django-log-file-viewer==0.4
>> psycopg2==2.5
>> virtualenv==1.9.1
>>
>>
>> erro:
>> c:\WorkspacePY>python manage.py reset meet
>> Traceback (most recent call last):
>>   File "manage.py", line 10, in 
>> execute_from_command_line(sys.**argv)
>>   File 
>> "C:\Python27\lib\site-**packages\django\core\**management\__init__.py", 
>> line
>> 443, in execute_from_command_line
>> utility.execute()
>>   File 
>> "C:\Python27\lib\site-**packages\django\core\**management\__init__.py", 
>> line
>> 382, in execute
>> self.fetch_command(subcommand)**.run_from_argv(self.argv)
>>   File "C:\Python27\lib\site-**packages\django\core\**management\base.py", 
>> line 196,
>>  in run_from_argv
>> self.execute(*args, **options.__dict__)
>>   File "C:\Python27\lib\site-**packages\django\core\**management\base.py", 
>> line 232,
>>  in execute
>> output = self.handle(*args, **options)
>>   File "C:\Python27\lib\site-**packages\django\core\**management\base.py", 
>> line 304,
>>  in handle
>> app_output = self.handle_app(app, **options)
>>   File "C:\Python27\lib\site-**packages\django\core\**
>> management\commands\reset.py",
>>  line 34, in handle_app
>> sql_list = sql_reset(app, self.style, connection)
>>   File "C:\Python27\lib\site-**packages\django\core\**management\sql.py", 
>> line 107,
>> in sql_reset
>> return sql_delete(app, style, connection) + sql_all(app, style, 
>> connection)
>>   File "C:\Python27\lib\site-**packages\django\core\**management\sql.py", 
>> line 66, i
>> n sql_delete
>> table_names = connection.introspection.get_**table_list(cursor)
>>   File "C:\Python27\lib\site-**packages\django\db\backends\**
>> postgresql_psycopg2\int
>> rospection.py", line 33, in get_table_list
>> AND pg_catalog.pg_table_is_**visible(c.oid)""")
>>   File "C:\Python27\lib\site-**packages\django\db\backends\**util.py", 
>> line 40, in e
>> xecute
>> return self.cursor.execute(sql, params)
>>   File "C:\Python27\lib\site-**packages\django\db\backends\**
>> postgresql_psycopg2\bas
>> e.py", line 52, in execute
>> return self.cursor.execute(query, args)
>> django.db.utils.DatabaseError: current transaction is aborted, commands 
>> ignored
>> until end of transaction block
>>
>> sql:
>> 2013-04-25 11:42:54,790 [DEBUG] (0.238) 
>> SELECT c.relname
>> FROM pg_catalog.pg_class c
>> LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
>> WHERE c.relkind IN ('r', 'v', '')
>> AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
>> AND pg_catalog.pg_table_is_**visible(c.oid); args=()
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/django-users?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django 1.5.1 and formsets with more than 1000 initials

2013-04-25 Thread Carsten Fuchs


Hi Xavier,

thank you very much for your reply!  :)

Am 25.04.2013 07:31, schrieb Xavier Ordoquy:

I'm not sure whether the FormSet could extends itself this number if the 
initial_data is larger than 1000.


If I understand the documentation correctly, the purpose of the 
`max_num` parameter is to prevent that someone sends a manipulated, 
excessively large value in the hidden form field that states the number 
of (extra) forms that are submitted, whereas it is not (directly) 
related to the number of forms that are *actually* POSTed, or 
initialized via parameter `initials`.


(Thus my surprise when my application that worked without problems in 
Django 1.4 stopped working with Django 1.5.1, because the Formset 
factory was created as shown (with extra=0) and pruned to the default of 
1000 elements.)



You probably could open a ticket about that.


Well, recently I posted to the wrong list (a question that went 
unanswered here) and was promptly corrected (friendly, but firmly), so I 
rather wait a few more days if maybe someone else has additional info 
about this.


Best regards,
Carsten

--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cant syncdb with postgresql

2013-04-25 Thread Pedro Silva

installed apps:
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'django.contrib.admin',
'django.contrib.admindocs',
'psycopg2.extensions',
#my app
'meetpop.meet',
#more info at https://code.google.com/p/gsettings/wiki/API
'meetpop.gsettings',
#django logging view helper
'django-log-file-viewer',
#custom template tags 
'meetpop.meet.templatetags',

its fresh, i can create a fresh sqllite db with no probs.


Quinta-feira, 25 de Abril de 2013 15:10:21 UTC+1, Daniele Procida escreveu:
>
> On Thu, Apr 25, 2013, Pedro Silva > 
> wrote: 
>
> >I cant sync db with heroku postgresql, with sqllite works great. 
> >Can anybody help me? 
> >requeriments: 
> >Django==1.4.5 
> >PIL==1.1.7 
> >distribute==0.6.36 
> >dj-database-url==0.2.1 
> >django-db-log==2.2.1 
> >django-log-file-viewer==0.4 
> >psycopg2==2.5 
> >virtualenv==1.9.1 
>
> Can you list what you have in INSTALLED_APPS? 
>
> And, are you doing your syncdb on an empty database, or one with data 
> already in it? 
>
> Daniele 
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: ManyToMany relationship and raw sql queries

2013-04-25 Thread Matthieu Bouron

On Thursday, April 11, 2013 5:39:57 PM UTC+2, Tom Evans wrote:
>
> On Thu, Apr 11, 2013 at 3:42 PM, Matthieu Bouron 
> > wrote: 
> > Hello, 
> > 
> > Is there a way to handle many-to-many relationship with raw sql queries 
> ? 
> > I have the following model: 
> > 
> > from django.db import models 
> > 
> > class Tag(models.Model): 
> > name = models.CharField(max_length=512, unique=True) 
> > 
> > class Bookmark(models.Model): 
> > link = models.CharField(max_length=512) 
> > title = models.CharField(max_length=512) 
> > tags = models.ManyToManyField(Tag) 
> > added_at = models.DateField() 
> > 
> > Using Bookmark.objetcs.all() will result in a subquery for each row of 
> the 
> > bookmark table which is not acceptable for performance reasons. 
> > First question is there a way to fetch all the content with a single 
> query ? 
> > Second question is it possible to use raw sql queries. I tried the 
> > following: 
> > 
> > bookmarks = Bookmark.objects.raw( 
> > 'SELECT * FROM bookmarkmanager_bookmark b ' 
> > 'LEFT JOIN bookmarkmanager_bookmark_tags bt ON (b.id= 
> > bt.bookmark_id) ' 
> > 'LEFT JOIN bookmarkmanager_tag t ON (bt.tag_id = 
> t.id)' 
> > ) 
> > 
> > But when i tried to access the tags attribute on a bookmark i get the 
> > following exception: 
> > 
> > ValueError: "" needs to have a value for 
> field 
> > "bookmark" before this many-to-many relationship can be used. 
> > 
> > Thanks in advance, 
> > Matthieu 
> > 
>
> Are you tied to raw SQL queries? Django itself supports traversing M2M 
> relationships in a sane manner if you tell it to do so: 
>
>
> https://docs.djangoproject.com/en/1.5/ref/models/querysets/#prefetch-related 
>

Thanks.
Another problem remains ... performances are horrible even if i use 
values().
I have 1000 rows in base, executing from a script (db sqlite):
  - 800ms to fetch all the objects (traversing m2m with prefetch_related).
  - 200ms to fetch all the row from bookmark table without traversing the 
m2m relationship).

Are my results expected ?
Are there any plan on improving django orm performance ?

Matthieu

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Calling Jquery or javascript function based on an if condition

2013-04-25 Thread Iftikhar Ali

yes brother you can it is very easy
just put your condition in and if
you should have to know how the if condition is working in django templates


{% ifequals comparator1 comparator2 %}

call javascript function from here

{% end ifequals %} 

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: ImproperlyConfigured: Requested setting USE_I18N, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before access

2013-04-25 Thread Tom Evans

On Thu, Apr 25, 2013 at 2:56 PM, Iftikhar Ali  wrote:
> when i am running the project it is running perfectly fine but when i am
> trying to open django-admin.py shell the error:

Don;t use django-admin to launch the shell, only use django-admin to
create projects¹. Once you have created your project using
django-admin.py, use the manage.py script it created inside your
project to interact in any with it - creating apps, running syncdb,
accessing the project shell.

See the docs here:

https://docs.djangoproject.com/en/1.5/ref/django-admin/#django-admin-py-and-manage-py

The reason you want to use manage.py over django-admin,py is that
manage.py can usually find your settings automatically - it
automatically sets the environment variable DJANGO_SETTINGS_MODULE to
the correct value.

Cheers

Tom

¹ Or standalone apps. For apps within the project, you use manage.py
startapp, like everything else in the project.

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: I encountered a core exception and need help configuring for a database. My OS is Ubuntu 12.10 32 bit

2013-04-25 Thread C. Kirby

Can you show the file structure of you project like this:

/project
-app1/
--models.py
--views.py
-manage.py
-settings.py

with your actual files and structure?
Also it would be useful to see the contents of you manage.py file

On Friday, March 22, 2013 12:54:58 AM UTC-5, Lightning wrote:
>
> CORRECTION;
>
> I gave it a shot Bill an thanks for the reply btw ... this also id not 
> work I pasted what i did in the terminal. manage.py NOT settings.py is 
> nested in /home/lightning/Docments/django-works/mysite/manage.py. 
> settings.py is one down
>
>
> On Thu, Mar 21, 2013 at 10:51 PM, hugh Manchu 
> 
> > wrote:
>
>> I gave it a shot Bill an thanks for the reply btw ... this also id not 
>> work I pasted what i did in the terminal. settings.py is nested in 
>> /home/lightning/Docments/django-works/mysite/manage.py. settings.py is one 
>> down
>>
>>
>> On Thu, Mar 21, 2013 at 1:39 PM, Bill Freeman 
>> > wrote:
>>
>>> Setting an environment variable is done by saying something like:
>>>
>>> lightning@rigel5:~$ export DJANGO_SETTINGS_MODULE='mysite.settings'
>>>
>>> assuming that your settings.py file is in a directory named "mysite", in 
>>> turn in the current directory (your home directory, if I interpret your 
>>> prompt string correctly).  Then that command may work.
>>>
>>> But that's the painful way to do that.  Presumably there is a file named 
>>> manage.py either in the same directory as settings.py (older Djangos) or 
>>> one directory up (newer Djangos).  'cd' to the directory containing 
>>> manage.py and type:
>>>
>>> lightning@rigel5:pathToDirectoryContainingManage_py$ python manage.py 
>>> diffsettings
>>>
>>> If you look at manage.py with 'less' or with an editor, you will see 
>>> that it sets the DJANGO_SETTINGS_MODULE environment variable (though using 
>>> python code, rather than shell code) appropriately (for use from the 
>>> current directory) before doing other stuff.
>>>
>>> For my money, django-admin.py should only ever be used for its 
>>> startproject command.  Everything else should be done with manage.py after 
>>> cd'ing to the directory that contains it (or from a wsgi script, which also 
>>> sets the DJANGO_SETTINGS_MODULE environment variable and adjusts sys.path 
>>> to be sure that the directory containing manage.py is there, but that will 
>>> come much later for you, I think).
>>>
>>> Bill
>>>
>>> On Thu, Mar 21, 2013 at 1:13 PM, Lightning 
>>> > wrote:
>>>


 On Wednesday, March 20, 2013 11:50:49 PM UTC-7, Lightning wrote:
>
>
> 
>  
> **
>
> [image: enter image description here]I need help configuring for a 
> database. Is there a paper I can read that will give me an overview on 
> this 
> procedure? I encountered a core exception. My OS is Ubuntu 12.10 32 bit.
>
> ENVIRONMENT_VARIABLE = "DJANGO_SETTINGS_MODULE"
> class LazySettings(LazyObject):
> """
> A lazy proxy for either global Django settings or a custom settings 
> object.
> The user can manually configure settings prior to using them. 
> Otherwise,
> Django uses the settings module pointed to by DJANGO_SETTINGS_MODULE.
> """
>
>


  ImproperlyConfigured: Requested setting USE_I18N, but settings are not 
 configured. You must either define the environment variable 
 DJANGO_SETTINGS_MODULE or call settings.configure() before accessing 
 settings.
  
 -- 
 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...@googlegroups.com .

 To post to this group, send email to 
 django...@googlegroups.com
 .
 Visit this group at http://groups.google.com/group/django-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  

>>>
>>>  -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Django users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/django-users/h7BncMwxH7E/unsubscribe?hl=en
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> django-users...@googlegroups.com .
>>> To post to this group, send email to django...@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/django-users?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>
>>
>

-- 
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 th

Re: cant syncdb with postgresql

2013-04-25 Thread Daniele Procida

On Thu, Apr 25, 2013, Pedro Silva  wrote:

>I cant sync db with heroku postgresql, with sqllite works great.
>Can anybody help me?
>requeriments:
>Django==1.4.5
>PIL==1.1.7
>distribute==0.6.36
>dj-database-url==0.2.1
>django-db-log==2.2.1
>django-log-file-viewer==0.4
>psycopg2==2.5
>virtualenv==1.9.1

Can you list what you have in INSTALLED_APPS?

And, are you doing your syncdb on an empty database, or one with data already 
in it?

Daniele

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: I encountered a core exception and need help configuring for a database. My OS is Ubuntu 12.10 32 bit

2013-04-25 Thread Iftikhar Ali


>
>  buddy i am also getting the same error... if you have so far got the 
> answer please help me too...
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

ImproperlyConfigured: Requested setting USE_I18N, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing

2013-04-25 Thread Iftikhar Ali

when i am running the project it is running perfectly fine but when i am 
trying to open django-admin.py shell the error:

ImproperlyConfigured: Requested setting USE_I18N, but settings are not 
configured. You must either define the environment variable 
DJANGO_SETTINGS_MODULE or call settings.configure() before accessing 
settings.

is generated. Not only when opening the django-admin.py shell but also when 
testing and using pychecker. 
i follow the doc.djangoproject and opened the python shell and append the 
projectname.setting to  the sys.path. when i import first time it is ok but 
when i come out of python shell and re enter to the shell the 
projectname.setting is missing from the sys.path

i am totally blank what is going on around here can any body have the 
solution for this thanks in advance you guyz..

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cant syncdb with postgresql

2013-04-25 Thread Pedro Silva

no lock with that

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: handling IntegrityError: Duplicate entry in UserCreationForm

2013-04-25 Thread Kelly Nicholes

If you ever want to know how the UserCreationForm works, the source is 
always available not only on your machine but also on 
https://github.com/django/django/blob/master/django/contrib/auth/models.py


On Wednesday, April 24, 2013 9:27:39 AM UTC-6, sachin wrote:
>
> Hello,
>
> I m extending my auth user model to add addition entries like phone 
> numbers and emp_id. In the model I m marking both the fields as unique=True.
> Form generation is using UserCreationForm. But whenever I try to save same 
> phone number or emp_id it throws 
>
> *IntegrityError: (1062, "Duplicate entry '447' for key 'phone_num'")*
>
> How to handle this error and show it to user during form input?
>
> Also how do the same UserCreationForm validates duplicate entry for 
> username etc ??
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cant syncdb with postgresql

2013-04-25 Thread Timothy Makobu

You need to catch exceptions during a commit and rollback the incomplete
transaction.

from django.db import connection
connection._rollback()

to rollback the current one.


On Thu, Apr 25, 2013 at 4:08 PM, Pedro Silva wrote:

> I cant sync db with heroku postgresql, with sqllite works great.
> Can anybody help me?
> requeriments:
> Django==1.4.5
> PIL==1.1.7
> distribute==0.6.36
> dj-database-url==0.2.1
> django-db-log==2.2.1
> django-log-file-viewer==0.4
> psycopg2==2.5
> virtualenv==1.9.1
>
>
> erro:
> c:\WorkspacePY>python manage.py reset meet
> Traceback (most recent call last):
>   File "manage.py", line 10, in 
> execute_from_command_line(sys.**argv)
>   File "C:\Python27\lib\site-**packages\django\core\**management\__init__.py",
> line
> 443, in execute_from_command_line
> utility.execute()
>   File "C:\Python27\lib\site-**packages\django\core\**management\__init__.py",
> line
> 382, in execute
> self.fetch_command(subcommand)**.run_from_argv(self.argv)
>   File "C:\Python27\lib\site-**packages\django\core\**management\base.py",
> line 196,
>  in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "C:\Python27\lib\site-**packages\django\core\**management\base.py",
> line 232,
>  in execute
> output = self.handle(*args, **options)
>   File "C:\Python27\lib\site-**packages\django\core\**management\base.py",
> line 304,
>  in handle
> app_output = self.handle_app(app, **options)
>   File "C:\Python27\lib\site-**packages\django\core\**
> management\commands\reset.py",
>  line 34, in handle_app
> sql_list = sql_reset(app, self.style, connection)
>   File "C:\Python27\lib\site-**packages\django\core\**management\sql.py",
> line 107,
> in sql_reset
> return sql_delete(app, style, connection) + sql_all(app, style,
> connection)
>   File "C:\Python27\lib\site-**packages\django\core\**management\sql.py",
> line 66, i
> n sql_delete
> table_names = connection.introspection.get_**table_list(cursor)
>   File "C:\Python27\lib\site-**packages\django\db\backends\**
> postgresql_psycopg2\int
> rospection.py", line 33, in get_table_list
> AND pg_catalog.pg_table_is_**visible(c.oid)""")
>   File "C:\Python27\lib\site-**packages\django\db\backends\**util.py",
> line 40, in e
> xecute
> return self.cursor.execute(sql, params)
>   File "C:\Python27\lib\site-**packages\django\db\backends\**
> postgresql_psycopg2\bas
> e.py", line 52, in execute
> return self.cursor.execute(query, args)
> django.db.utils.DatabaseError: current transaction is aborted, commands
> ignored
> until end of transaction block
>
> sql:
> 2013-04-25 11:42:54,790 [DEBUG] (0.238)
> SELECT c.relname
> FROM pg_catalog.pg_class c
> LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
> WHERE c.relkind IN ('r', 'v', '')
> AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
> AND pg_catalog.pg_table_is_**visible(c.oid); args=()
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

cant syncdb with postgresql

2013-04-25 Thread Pedro Silva

I cant sync db with heroku postgresql, with sqllite works great.
Can anybody help me?
requeriments:
Django==1.4.5
PIL==1.1.7
distribute==0.6.36
dj-database-url==0.2.1
django-db-log==2.2.1
django-log-file-viewer==0.4
psycopg2==2.5
virtualenv==1.9.1


erro:
c:\WorkspacePY>python manage.py reset meet
Traceback (most recent call last):
  File "manage.py", line 10, in 
execute_from_command_line(sys.argv)
  File "C:\Python27\lib\site-packages\django\core\management\__init__.py", 
line
443, in execute_from_command_line
utility.execute()
  File "C:\Python27\lib\site-packages\django\core\management\__init__.py", 
line
382, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File "C:\Python27\lib\site-packages\django\core\management\base.py", line 
196,
 in run_from_argv
self.execute(*args, **options.__dict__)
  File "C:\Python27\lib\site-packages\django\core\management\base.py", line 
232,
 in execute
output = self.handle(*args, **options)
  File "C:\Python27\lib\site-packages\django\core\management\base.py", line 
304,
 in handle
app_output = self.handle_app(app, **options)
  File 
"C:\Python27\lib\site-packages\django\core\management\commands\reset.py",
 line 34, in handle_app
sql_list = sql_reset(app, self.style, connection)
  File "C:\Python27\lib\site-packages\django\core\management\sql.py", line 
107,
in sql_reset
return sql_delete(app, style, connection) + sql_all(app, style, 
connection)
  File "C:\Python27\lib\site-packages\django\core\management\sql.py", line 
66, i
n sql_delete
table_names = connection.introspection.get_table_list(cursor)
  File 
"C:\Python27\lib\site-packages\django\db\backends\postgresql_psycopg2\int
rospection.py", line 33, in get_table_list
AND pg_catalog.pg_table_is_visible(c.oid)""")
  File "C:\Python27\lib\site-packages\django\db\backends\util.py", line 40, 
in e
xecute
return self.cursor.execute(sql, params)
  File 
"C:\Python27\lib\site-packages\django\db\backends\postgresql_psycopg2\bas
e.py", line 52, in execute
return self.cursor.execute(query, args)
django.db.utils.DatabaseError: current transaction is aborted, commands 
ignored
until end of transaction block

sql:
2013-04-25 11:42:54,790 [DEBUG] (0.238) 
SELECT c.relname
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relkind IN ('r', 'v', '')
AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
AND pg_catalog.pg_table_is_visible(c.oid); args=()

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: handling IntegrityError: Duplicate entry in UserCreationForm

2013-04-25 Thread isachin

Thanx Siddharth and Pradeep, I will try both suggestion and let you know


On Thu, Apr 25, 2013 at 2:07 PM, Pradeep Kumar  wrote:

> Hi Sachin,
>
> If you have added the unique=True later and migrated the existing table, I
> would also suggest you to first clean up  the NULL and duplicate entries
> using a script or even from shell.
>
> After doing that you can use
> *  try: *
>  # your code here
> *  except IntegrityError: *
>  #create variables here to send user error message
>
> One more pointer - try checking for the user input( X.object.filter
> method) in the unique fields in database before performing .save
>
>
> On Thu, Apr 25, 2013 at 1:34 PM, Siddharth Ghumre <
> siddharth.ghumr...@gmail.com> wrote:
>
>> hi Sachin,
>>
>> Please use django's form clean method in order to validate your phone_num
>> field.
>> You can also override the django's clean method by using your own
>> clean_phone_field method.
>> Please refer the link:-
>>
>> https://docs.djangoproject.com/en/dev/ref/forms/validation/
>>
>> I am sure that a small googling on overriding the clean method in django
>> form class will defiantly help you.
>>
>> -Siddharth
>>
>>
>> On Wed, Apr 24, 2013 at 8:57 PM, sachin  wrote:
>>
>>> Hello,
>>>
>>> I m extending my auth user model to add addition entries like phone
>>> numbers and emp_id. In the model I m marking both the fields as unique=True.
>>> Form generation is using UserCreationForm. But whenever I try to save
>>> same phone number or emp_id it throws
>>>
>>> *IntegrityError: (1062, "Duplicate entry '447' for key 'phone_num'")*
>>>
>>> How to handle this error and show it to user during form input?
>>>
>>> Also how do the same UserCreationForm validates duplicate entry for
>>> username etc ??
>>>
>>>  --
>>> 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?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>  --
>> 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?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Django users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/django-users/EaYF9DEptLo/unsubscribe?hl=en
> .
> To unsubscribe from this group and all its topics, 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Sachin

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: handling IntegrityError: Duplicate entry in UserCreationForm

2013-04-25 Thread Pradeep Kumar

Hi Sachin,

If you have added the unique=True later and migrated the existing table, I
would also suggest you to first clean up  the NULL and duplicate entries
using a script or even from shell.

After doing that you can use
*  try: *
 # your code here
*  except IntegrityError: *
 #create variables here to send user error message

One more pointer - try checking for the user input( X.object.filter method)
in the unique fields in database before performing .save


On Thu, Apr 25, 2013 at 1:34 PM, Siddharth Ghumre <
siddharth.ghumr...@gmail.com> wrote:

> hi Sachin,
>
> Please use django's form clean method in order to validate your phone_num
> field.
> You can also override the django's clean method by using your own
> clean_phone_field method.
> Please refer the link:-
>
> https://docs.djangoproject.com/en/dev/ref/forms/validation/
>
> I am sure that a small googling on overriding the clean method in django
> form class will defiantly help you.
>
> -Siddharth
>
>
> On Wed, Apr 24, 2013 at 8:57 PM, sachin  wrote:
>
>> Hello,
>>
>> I m extending my auth user model to add addition entries like phone
>> numbers and emp_id. In the model I m marking both the fields as unique=True.
>> Form generation is using UserCreationForm. But whenever I try to save
>> same phone number or emp_id it throws
>>
>> *IntegrityError: (1062, "Duplicate entry '447' for key 'phone_num'")*
>>
>> How to handle this error and show it to user during form input?
>>
>> Also how do the same UserCreationForm validates duplicate entry for
>> username etc ??
>>
>>  --
>> 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?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: django development server timeout too quick

2013-04-25 Thread Siddharth Ghumre

Hi Hadi,

I am using sessions.middleware.SessionIdleTimeout in my app which takes
care of the session management

https://pypi.python.org/pypi/django-session-idle-timeout/1.0.1

Its clean and easy way to handle session timeouts.

-Siddharth



On Wed, Apr 24, 2013 at 11:57 AM, Hadi Sunyoto wrote:

> The problem is like this:
>
> i am using django admin, and in several forms, it might take around 10-20
> minutes to fill up.
> By the time save button is pressed, i am always redirected to login page.
>
> The question is: how can i make the timeout longer (or maybe last forever)
>
> I set the cache to file and session_engine to db
>
> CACHES = {
> 'default': {
> 'BACKEND': 'django.core.cache.backends.filebased.FileBasedCache',
> 'LOCATION': 'some/path',
> 'TIMEOUT': 10,
> }
> }
> SESSION_ENGINE = "django.contrib.sessions.backends.cached_db"
>
> What else am i missing here? any direction will be much appreciated
>
> i also have tried to set --noreload in runserver so that file changed does
> not get reloaded, but i still get the same problem.
>
> i don't plan on using apache/ngix/etc because this is only for my personal
> use
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: handling IntegrityError: Duplicate entry in UserCreationForm

2013-04-25 Thread Siddharth Ghumre

hi Sachin,

Please use django's form clean method in order to validate your phone_num
field.
You can also override the django's clean method by using your own
clean_phone_field method.
Please refer the link:-

https://docs.djangoproject.com/en/dev/ref/forms/validation/

I am sure that a small googling on overriding the clean method in django
form class will defiantly help you.

-Siddharth


On Wed, Apr 24, 2013 at 8:57 PM, sachin  wrote:

> Hello,
>
> I m extending my auth user model to add addition entries like phone
> numbers and emp_id. In the model I m marking both the fields as unique=True.
> Form generation is using UserCreationForm. But whenever I try to save same
> phone number or emp_id it throws
>
> *IntegrityError: (1062, "Duplicate entry '447' for key 'phone_num'")*
>
> How to handle this error and show it to user during form input?
>
> Also how do the same UserCreationForm validates duplicate entry for
> username etc ??
>
>  --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

38 matches

Mail list logo