Translation and messages framework problem

[Kaloian]

Hi, 
Everywhere else in my project where I use django messages framework and 
translation everything works like charm, except this one place. 
I have a simple view like this:

from django.utils.translation import ugettext_lazy as _def 
toggle_publish(request,action,post_id):
try:
post = Post.objects.get(id = post_id)
if action=='publish':
post.status = 1
post.save()
messages.success(request, _('The post was published successfully!'))
elif action == 'unpublish':
post.status = 0
post.save()
messages.success(request, _('The post was unpublished!'))
except Post.DoesNotExist:
messages.error(request, _('You are not authorized to publish/unpublish 
this post!'))

return HttpResponseRedirect('/list_posts/')




The problem is that the message is always displayed in English, even though 
the current language is different. 

The strange thing is that when I visit the url for lets say publish, two or 
more times consequently the message is displayed in the correct language 
after the first time. 

But clicking publish, than unpublish (which is the normal flow) shows the 
message only in English. 

Do you have any ideas what could be causing 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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1cd41a82-b6a7-4ab9-ab5d-b40231dc7a05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gunicorn sock file is missing?

[Kaloian]

>
> Did you try to sudo to the user running gunicorn and creating the socket?

Do you mean to create the socket manually? Haven't tried that. 

The directory and all its parents are owned by the user running gunicorn 
and also have 777 permissions. I am no sure I understand what you mean by - 
"The user isn't in one of the new group cause he is logged in" . 
Is it possible the reason to be something from the virtual env since the 
directory  /webapps/my-app/run/ is inside virtual env path. 

Thanks,
Kaloian


On Friday, March 6, 2015 at 5:01:55 PM UTC+2, aRkadeFR wrote:
>
>  
> On 03/06/2015 01:30 PM, Kaloian wrote:
>  
> Hi Erik, and thanks for the help. 
>
> Well it appears to be a permission issue after all, but I really cannot 
> understand why. I tried to change the directory for the sock file from 
> /webapps/my-app/run/gunicorn.sock to /sockets/gunicorn.sock and gunicorn 
> started normally. I tried to give full permissions to /webapps/my-app/run/ 
> but still no success. I never tried to create the sock file myself and the 
> /webapps/my-app/run/ dir is empty all the time. I cannot understand what is 
> stopping gunicorn from creating the sock file in this directory. 
>  
>
> Did you try to sudo to the user running gunicorn and creating the socket?
> Some hints:
> - The user can't access the directory cause he is not allowed to index one 
> of his parent
> - The user isn't in one of the new group cause he is logged in
> - ... ?
>
> Most of the time sudo to the user is useful for me
>
>  
> Regards,
> Kaloian 
>
> On Thursday, February 26, 2015 at 10:47:41 AM UTC+2, Erik Cederstrand 
> wrote: 
>>
>>
>> > Den 26/02/2015 kl. 07.56 skrev Kaloian <kaloian...@gmail.com>: 
>> > 
>> > Hi Erik, 
>> > 
>> > No it doesn't start at all, running the gunicorn_start script gives: 
>> > 
>> > [ERROR] Retrying in 1 second. 
>> > [ERROR] Retrying in 1 second. 
>> > [ERROR] Retrying in 1 second. 
>> > [ERROR] Retrying in 1 second. 
>> > [ERROR] Retrying in 1 second. 
>> > [ERROR] Can't connect to /path/to/my/gunicorn.sock 
>> > 
>> > This is why I thought that the missing sock file is failing it to 
>> start. Do you think it could be something else? 
>> > I have already tried to add the absolute path in gunicorn_start but 
>> nothing changed. 
>>
>> A UNIX socket is like a TCP connection, except it's represented as a 
>> file. gunicorn is supposed to create it on startup and destroy it on 
>> shutdown, and it shouldn't be present when gunicorn is not running. 
>>
>> Maybe you tried to create /path/to/my/gunicorn.sock yourself, and the 
>> file is now garbage? Try deleting it. Otherwise, another instance of 
>> gunicorn may be running already. Try "ps aux | grep gunicorn" or "lsof -U | 
>> grep gunicorn" if you're on Linux. Also, the user running gunicorn_start 
>> must have access to create files in /path/to/my/ 
>>
>> Erik
>
>  -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/59fe3b92-d9d7-4e03-b8f3-b0be1c355d78%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/django-users/59fe3b92-d9d7-4e03-b8f3-b0be1c355d78%40googlegroups.com?utm_medium=email_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/d55eb7d8-f81d-4992-b5ac-5c453a27cd80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gunicorn sock file is missing?

[Kaloian]

Hi Erik, and thanks for the help. 

Well it appears to be a permission issue after all, but I really cannot 
understand why. I tried to change the directory for the sock file from 
/webapps/my-app/run/gunicorn.sock to /sockets/gunicorn.sock and gunicorn 
started normally. I tried to give full permissions to /webapps/my-app/run/ 
but still no success. I never tried to create the sock file myself and the 
/webapps/my-app/run/ dir is empty all the time. I cannot understand what is 
stopping gunicorn from creating the sock file in this directory. 

Regards,
Kaloian 

On Thursday, February 26, 2015 at 10:47:41 AM UTC+2, Erik Cederstrand wrote:
>
>
> > Den 26/02/2015 kl. 07.56 skrev Kaloian <kaloian...@gmail.com 
> >: 
> > 
> > Hi Erik, 
> > 
> > No it doesn't start at all, running the gunicorn_start script gives: 
> > 
> > [ERROR] Retrying in 1 second. 
> > [ERROR] Retrying in 1 second. 
> > [ERROR] Retrying in 1 second. 
> > [ERROR] Retrying in 1 second. 
> > [ERROR] Retrying in 1 second. 
> > [ERROR] Can't connect to /path/to/my/gunicorn.sock 
> > 
> > This is why I thought that the missing sock file is failing it to start. 
> Do you think it could be something else? 
> > I have already tried to add the absolute path in gunicorn_start but 
> nothing changed. 
>
> A UNIX socket is like a TCP connection, except it's represented as a file. 
> gunicorn is supposed to create it on startup and destroy it on shutdown, 
> and it shouldn't be present when gunicorn is not running. 
>
> Maybe you tried to create /path/to/my/gunicorn.sock yourself, and the file 
> is now garbage? Try deleting it. Otherwise, another instance of gunicorn 
> may be running already. Try "ps aux | grep gunicorn" or "lsof -U | grep 
> gunicorn" if you're on Linux. Also, the user running gunicorn_start must 
> have access to create files in /path/to/my/ 
>
> Erik

-- 
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/59fe3b92-d9d7-4e03-b8f3-b0be1c355d78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gunicorn sock file is missing?

[Kaloian]

Hi Erik,

No it doesn't start at all, running the gunicorn_start script gives: 


*[ERROR] Retrying in 1 second.*
*[ERROR] Retrying in 1 second.*
*[ERROR] Retrying in 1 second.*
*[ERROR] Retrying in 1 second.*
*[ERROR] Retrying in 1 second.**[ERROR] Can't connect to 
/path/to/my/gunicorn.sock *

This is why I thought that the missing sock file is failing it to start. Do 
you think it could be something else? 
I have already tried to add the absolute path in gunicorn_start but nothing 
changed. 

Thanks,
Kaloian


On Wednesday, February 25, 2015 at 11:55:43 AM UTC+2, Erik Cederstrand 
wrote:
>
>
> > Den 25/02/2015 kl. 07.16 skrev Kaloian <kaloian...@gmail.com 
> >: 
> > 
> > I have an ansible provisioned VM based on this one 
> https://github.com/jcalazan/ansible-django-stack but for some reason 
> trying to start Gunicorn gives the following error: 
> > 
> > Can't connect to /path/to/my/gunicorn.sock 
> > 
> > [...] 
> > 
> > Can anyone point me to any direction what could be causing the missing 
> gunicorn.sock file ? 
>
> Is gunicorn even running? If not, you ned to find out why it failed to 
> start, or why it crashed. As a start, try adding the absolute path to 
> gunicorn in your gunicorn_start script instead of just "exec gunicorn". 
>
> Erik 
>

-- 
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/e326ee4c-1443-4f59-a00a-9249269caad1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gunicorn sock file is missing?

[Kaloian]

I have an ansible provisioned VM based on this one 
https://github.com/jcalazan/ansible-django-stack but for some reason trying 
to start Gunicorn gives the following error:

*Can't connect to /path/to/my/gunicorn.sock *

and in nginx log file:

*connect() to unix:/path/to/my/gunicorn.sock failed (2: No such file or 
directory) while connecting to upstream*

And the socket file is really missing in the specified directory. I have 
checked the permissions of the directory and they are fine.

Here is my gunicorn_start script:


NAME="{{ application_name }}" 
DJANGODIR={{ application_path }} 
SOCKFILE={{ virtualenv_path }}/run/gunicorn.sock 
USER={{ gunicorn_user }} GROUP={{ gunicorn_group }} 
NUM_WORKERS={{ gunicorn_num_workers }} 

# Set this to 0 for unlimited requests. During development, you might want to # 
set this to 1 to automatically restart the process on each request (i.e. your # 
code will be reloaded on every request). 
MAX_REQUESTS={{ gunicorn_max_requests }} 
echo "Starting $NAME as `whoami`" 
# Activate the virtual environment. 
cd $DJANGODIR 
. ../../bin/activate 
# Set additional environment variables. 
. ../../bin/postactivate 
# Create the run directory if it doesn't exist. 
RUNDIR=$(dirname $SOCKFILE) test -d $RUNDIR || mkdir -p $RUNDIR 
# Programs meant to be run under supervisor should not daemonize themselves # 
(do not use --daemon). 
exec gunicorn \ --name $NAME \ 
--workers $NUM_WORKERS \ 
--max-requests $MAX_REQUESTS \ 
--user $USER --group $GROUP \ 
--log-level debug \ 
--bind unix:$SOCKFILE \ 
{{ application_name }}.wsgi


Can anyone point me to any direction what could be causing the missing 
gunicorn.sock file ?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f4fa6c59-9b9c-4433-831d-0f563b5dd763%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django 1.5 AbstractBaseUser with char primary key not JSON serializable

[Kaloian]

Hi Russel,

Great to see this documented. I will most probably go with the "api_key *in 
addition* to the integer primary key" solution to avoid additional problems.

Thanks,
Kaloian

On Saturday, February 16, 2013 4:25:41 AM UTC+2, Russell Keith-Magee wrote:
>
> Hi Kaloian,
>
> Ah - you've just fired a neuron in my brain… This is a known issue, and 
> it's not just the permission_required decorator.
>
> See ticket #14881.
>
> I don't remember the permission_required decorator itself being a problem 
> at that time (not saying it isn't -- just that it wasn't reported as such, 
> or I don't recall it being reported as such) -- the issues that were being 
> reported were with admin URLs for User objects, and for password reset 
> tokens. 
>
> So - the short answer is that yes, non-integer primary keys will cause 
> some problems with custom User objects. This is something we should 
> probably document as a limitation. I've just added a note to this effect in 
> the docs.
>
> This doesn't mean you have to give up having the api_key as a unique 
> identifier; you just need to have the api_key *in addition* to the integer 
> primary key; Django's internals will use the integer primary key, and your 
> code can do lookups based on the API key.
>
> Of course, we're also open to patches to fix the situation :-)
>
> Yours,
> Russ Magee %-)
>
> On Fri, Feb 15, 2013 at 9:48 PM, Kaloian <kaloian...@gmail.com
> > wrote:
>
>>
>> Hi Russel I got into another small issue related to the character primary 
>> key of the user model. 
>> When I try to use the permission_required decorator on that model I got 
>> the following error. 
>>
>> Exception Value: 
>>
>> invalid literal for int() with base 10: 
>> '3DDz0Vi7zonFDq9JfByKkeparghaWwupVwbMCbL7JHo'
>>
>>  Exception Location: 
>> /usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__.py 
>> in get_prep_value, line 554
>> Here is the latest definition of my model: 
>>
>> class Merchant(AbstractBaseUser,PermissionsMixin):  
>> """User with app settings."""
>> id = models.CharField(max_length=256, primary_key=True)
>> email = models.EmailField(unique=True, db_index=True)
>>
>> company_name = models.CharField(max_length=256)
>> website = models.URLField()
>> description = models.TextField(blank=True)
>> #api_key = models.CharField(blank=True, max_length=256, 
>> primary_key=True)   
>>   
>> USERNAME_FIELD = 'email'  
>> REQUIRED_FIELDS = ['company_name','website']
>>
>> objects = MerchantManager()
>>
>>
>> class Meta:
>> verbose_name = _('Merchant')
>> verbose_name_plural = _('Merchants')
>>
>>
>>
>>
>> I can easily find workaround for that problem by writing custom decorator 
>> for example but I am not sure this is supposed to be this way. Or may be I 
>> am missing something here ? 
>>
>> Thanks,
>> Kaloian
>>
>>
>>  -- 
>> 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 AbstractBaseUser with char primary key not JSON serializable

[Kaloian]

Hi Russel I got into another small issue related to the character primary 
key of the user model. 
When I try to use the permission_required decorator on that model I got the 
following error. 

Exception Value: 

invalid literal for int() with base 10: 
'3DDz0Vi7zonFDq9JfByKkeparghaWwupVwbMCbL7JHo'

 Exception Location: 
/usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__.py 
in get_prep_value, line 554
Here is the latest definition of my model: 

class Merchant(AbstractBaseUser,PermissionsMixin):  
"""User with app settings."""
id = models.CharField(max_length=256, primary_key=True)
email = models.EmailField(unique=True, db_index=True)
company_name = models.CharField(max_length=256)
website = models.URLField()
description = models.TextField(blank=True)
#api_key = models.CharField(blank=True, max_length=256, 
primary_key=True)   
  
USERNAME_FIELD = 'email'  
REQUIRED_FIELDS = ['company_name','website']

objects = MerchantManager()

class Meta:
verbose_name = _('Merchant')
verbose_name_plural = _('Merchants')




I can easily find workaround for that problem by writing custom decorator for 
example but I am not sure this is supposed to be this way. Or may be I am 
missing something here ? 

Thanks,
Kaloian


-- 
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 AbstractBaseUser with char primary key not JSON serializable

[Kaloian]

Hi Russell,


Thanks for the responce! I actually found the problem it was not where I 
was looking for it and it was more of a typo. 
And your suggestion No.2 appears to be right:

> * Do you have any models with foreign keys to your custom user? (i.e., is 
> the problem manifesting when serialising Merchant, or serialising foreign 
> keys to Merchant?)
>

I am having a Product model with foreignkey to the Merchant model which had 
natural key method defined as follows:

class Product(models.Model):
name = models.CharField(max_length=200)
#merchant = models.ForeignKey(Merchant, to_field='api_key')
merchant = models.ForeignKey(Merchant)
url = models.URLField(max_length = 2000)  
description = models.TextField(blank=True) 
client_product_id = models.CharField(max_length='100')

objects = ProductManager() 
class Meta:
verbose_name = 'Product'
verbose_name_plural = 'Products' 
unique_together = ('merchant', 'client_product_id',) 

def __unicode__(self):
return self.name 
  
def natural_key(self):
return (self.merchant, self.client_product_id) 

The natural_key method returned self.merchant instead of self.merchant_id 
so it was trying to serialize the whole merchant object to make a natural 
key.  After switching this to merchant_id it is working properly. 

As a side note -- if you're using email as your username field, you should 
> set it as unique=True -- USERNAME_FIELD needs to be unique or you'll 
> experience problems later on. This is something that should probably be 
> caught by validation - which is a bug deserving of it's own report. For 
> performance reasons, you also probably want to set it db_index=True, since 
> you're going to be searching on that field fairly often, so having an index 
> on it makes sense.
>

Thanks for the notes I will for sure add these, but shouldn't both(unique 
and db_index) be added by default when you set your USERNAME_FIELD . 

Regards,
Kaloian 






On Wednesday, February 13, 2013 3:04:47 AM UTC+2, Russell Keith-Magee wrote:
>
>
> On Tue, Feb 12, 2013 at 9:03 PM, Kaloian <kaloian...@gmail.com
> > wrote:
>
>> I am having the following custom user model trying to use the Django 1.5 
>> AbstractBaseUser:
>>
>> class Merchant(AbstractBaseUser): 
>> email = models.EmailField()
>> company_name = models.CharField(max_length=256)
>> website = models.URLField()
>> description = models.TextField(blank=True)
>> api_key = models.CharField(blank=True, max_length=256, primary_key=True) 
>>   
>>
>> USERNAME_FIELD = 'email' 
>> REQUIRED_FIELDS = ['company_name','website']
>>
>>
>>class Meta:
>> verbose_name = _('Merchant')
>> verbose_name_plural = _('Merchants')
>>
>>def __unicode__(self):
>> return self.company_name 
>>
>>
>> The model works perfectly and database is as expected, but the problem is 
>> when I try to dumpdata to create fixtures for my tests. 
>>
>> python manage.py dumpdata --natural --exclude=contenttypes 
>> --exclude=auth.permission --indent=4 > fixtures/initial_data.json
>>
>>
>> Then I get the error:
>>
>> CommandError: Unable to serialize database:  is not 
>> JSON serializable
>>
>>
>>
>> Do you have ideas what could be the reason for this. Could it be the 
>> charfield primary key or something with the abstractbaseuser model?
>>
>> It's not immediately clear. The use of natural keys could also be a 
> contributing factor here. 
>
> What you've described isn't a problem I've seen previously, so you should 
> open a ticket to track it. It would also be exceedingly helpful if you can 
> try running a few tests to remove possible causes - e.g., 
>
>  * Does serialising *without* natural keys work? 
>  * Do you have any models with foreign keys to your custom user? (i.e., is 
> the problem manifesting when serialising Merchant, or serialising foreign 
> keys to Merchant?)
>  * Do you still have problems if you use a 'normal' integer key?
>
> Essentially, any help you can provide in narrowing down the exact cause 
> would be most helpful.
>
> Also, if you can run the tests with --traceback, we can get the full error 
> logs.
>
> As a side note -- if you're using email as your username field, you should 
> set it as unique=True -- USERNAME_FIELD needs to be unique or you'll 
> experience problems later on. This is something that should probably be 
> caught by validation - which is a bug deserving of it's own report. For 
> performance reasons, you also probably want to set it db_index=True, since

Django 1.5 AbstractBaseUser with char primary key not JSON serializable

[Kaloian]

I am having the following custom user model trying to use the Django 1.5 
AbstractBaseUser:

class Merchant(AbstractBaseUser): 
email = models.EmailField()
company_name = models.CharField(max_length=256)
website = models.URLField()
description = models.TextField(blank=True)
api_key = models.CharField(blank=True, max_length=256, primary_key=True)   

USERNAME_FIELD = 'email' 
REQUIRED_FIELDS = ['company_name','website']


   class Meta:
verbose_name = _('Merchant')
verbose_name_plural = _('Merchants')

   def __unicode__(self):
return self.company_name 


The model works perfectly and database is as expected, but the problem is 
when I try to dumpdata to create fixtures for my tests. 

python manage.py dumpdata --natural --exclude=contenttypes 
--exclude=auth.permission --indent=4 > fixtures/initial_data.json


Then I get the error:

CommandError: Unable to serialize database:  is not JSON 
serializable



Do you have ideas what could be the reason for this. Could it be the charfield 
primary key or something with the abstractbaseuser model?
  
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.

Django fixture load DeserializationError: 'unicode' object has no attribute 'pk'?

[Kaloian]

Hello,

   I am getting the following error when trying to run my tests with 
fixtures:

File 
"/usr/local/lib/python2.7/dist-packages/django/core/management/commands/loaddata.py",
 line 190, in handle
for obj in objects:
  File 
"/usr/local/lib/python2.7/dist-packages/django/core/serializers/json.py", line 
47, in Deserializerraise DeserializationError(e)DeserializationError: 'unicode' 
object has no attribute 'pk'


I am using the following to create the fixture:

manage.py dumpdata --natural --exclude=contenttypes --exclude=auth.permission 
--indent=4 > fixtures/initial_data.json 


I tried implementing natural key managers and methods for my models but 
still got the same error.

Here is the code of my models: http://pastebin.com/HbFariAC

I am really stuck with this so any clues would help me.

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.