Re: Reverse for 'reg/{{post.pk}}/' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

[meInvent bbird]

https://drive.google.com/file/d/0Bxs_ao6uuBDUQm5jOEdCOFowa0U/view?usp=sharing

On Tuesday, May 24, 2016 at 9:07:25 PM UTC+8, ludovic coues wrote:
>
> It should work better this way: 
>  onClick="window.location.href='{% url 'post_detail' pk=post.pk 
> %}'">Save 
>
> the url template tag take a route name, not an url as it first argument. 
>
> 2016-05-24 10:19 GMT+02:00 meInvent bbird  >: 
> > Reverse for 'reg/{{post.pk}}/' with arguments '()' and keyword 
> arguments 
> > '{}' not found. 0 pattern(s) tried: [] 
> > 
> > i follow django girl web , expect to go to /reg to fill a form and press 
> > save button then go to web /reg/ 
> > 
> > it has error 
> > 
> > INSTALLED_APPS = ( 
> > 'django.contrib.admin', 
> > 'django.contrib.auth', 
> > 'django.contrib.contenttypes', 
> > 'django.contrib.sessions', 
> > 'django.contrib.messages', 
> > 'django.contrib.staticfiles', 
> > 'django.contrib.sites', 
> > ) 
> > 
> > MIDDLEWARE_CLASSES = ( 
> > 'django.contrib.sessions.middleware.SessionMiddleware', 
> > 'django.middleware.common.CommonMiddleware', 
> > 'django.middleware.csrf.CsrfViewMiddleware', 
> > 'django.contrib.auth.middleware.AuthenticationMiddleware', 
> > 'django.contrib.auth.middleware.SessionAuthenticationMiddleware', 
> > 'django.contrib.messages.middleware.MessageMiddleware', 
> > 'django.middleware.clickjacking.XFrameOptionsMiddleware', 
> > 'django.middleware.security.SecurityMiddleware', 
> > 'site1.reg.models.Post', 
> > ) 
> > 
> > registration.html 
> > 
> > {% block content %} 
> > 
> > New user registration 
> > 
> > {% csrf_token %} 
> > 
> > {{ form.as_p }} 
> > 
> >  > onClick="window.location.href='{% url 'reg/{{post.pk}}/' 
>  %}'">Save 
> > 
> >  
> > 
> > {% endblock %} 
> > 
> > urls.py 
> > 
> > from django.conf.urls import include, url 
> > 
> > from . import views 
> > 
> > 
> > 
> > urlpatterns = [ 
> > 
> > url(r'^reg/$', views.post_new, name='post_new'), 
> > 
> > url(r'^reg/(?P\d+)/$', views.post_detail, name='post_detail'), 
> > 
> > ] 
> > 
> > views.py 
> > 
> > from .forms import PostForm 
> > 
> > from django.shortcuts import render 
> > 
> > from django.template.loader import get_template 
> > 
> > 
> > 
> > def post_new(request): 
> > 
> > form = PostForm() 
> > 
> > return render(request, 'registration.html', {'form': form}) 
> > 
> > 
> > 
> > def post_detail(request, pk): 
> > 
> > post = get_object_or_404(Post, pk=pk) 
> > 
> > if request.method == "POST": 
> > 
> > form = PostForm(request.POST, instance=post) 
> > 
> > if form.is_valid(): 
> > 
> > post = form.save(commit=False) 
> > 
> > post.author = request.user 
> > 
> > post.ProjectName = request.ProjectName 
> > 
> > post.UserName = request.UserName 
> > 
> > post.Company = request.Company 
> > 
> > post.Contact = request.Contact 
> > 
> > post.InitialPassword = request.InitialPassword 
> > 
> > post.UserType = request.UserType 
> > 
> > post.BusinessType = request.BusinessType 
> > 
> > post.published_date = timezone.now() 
> > 
> > post.save() 
> > 
> > return redirect('registration.html', pk=post.pk) 
> > 
> > else: 
> > 
> > form = PostForm(instance=post) 
> > 
> > 
> > return render(request, 'registration.html', {'form': form}) 
> > 
> > models.py 
> > 
> > from django.db import models 
> > 
> > from django.utils import timezone 
> > from django.apps import AppConfig 
> > 
> > import csv 
> > import os.path 
> > 
> > USERTYPE = ( 
> > ('Cyberport Tenant', 'Cyberport Tenant'), 
> > ('SmartSpace User', 'SmartSpace User'), 
> > ('Cyberport Incubate', 'Cyberport Incubate'), 
> > ('Collaboration Center Subscriber', 'Collaboration Center 
> Subscriber'), 
> > ('Cyberport Alumnus', 'Cyberport Alumnus'), 
> > ('Technology Partner', 'Technology Partner'), 
> > ('HKOSUG', 'HKOSUG'), 
> > ('Others', 'Others'), 
> > ) 
> > 
> > 
> > BUSINESSTYPE = ( 
> > ('Building', 'Building'), 
> > ('Data Analysis', 'Data Analysis'), 
> > ('Digital Entertainment', 'Digital Entertainment'), 
> > ('Education', 'Education'), 
> > ('Games', 'Games'), 
> > ('Gaming', 'Gaming'), 
> > ('ICT', 'ICT'), 
> > ('Marketing', 'Marketing'), 
> > ('Social Media', 'Social Media'), 
> > ('Others', 'Others'), 
> > ) 
> > 
> > 
> > class MyAppConfig(AppConfig): 
> > name = 'src.my_app_label' 
> > 
> > def ready(self): 
> > post_migrate.connect(do_stuff, sender=self) 
> > 
> > 
> > class Post(models.Model): 
> > 
> > author = models.ForeignKey('auth.User') 
> > 
> > Email = models.CharField(max_length=70) 
> > ProjectName = models.CharField(max_length=70) 
> > UserName = models.CharField(max_length=70) 
> > Company = models.CharField(max_length=70) 
> >  

Re: Reverse for 'reg/{{post.pk}}/' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

[meInvent bbird]

what is the url template tag take a route name?

so far, error is Reverse for 'views.post_detail' with arguments '()' and 
keyword arguments '{u'pk': ''}' not found. 0 pattern(s) tried: []


On Tuesday, May 24, 2016 at 9:07:25 PM UTC+8, ludovic coues wrote:
>
> It should work better this way: 
>  onClick="window.location.href='{% url 'post_detail' pk=post.pk 
> %}'">Save 
>
> the url template tag take a route name, not an url as it first argument. 
>
> 2016-05-24 10:19 GMT+02:00 meInvent bbird  >: 
> > Reverse for 'reg/{{post.pk}}/' with arguments '()' and keyword 
> arguments 
> > '{}' not found. 0 pattern(s) tried: [] 
> > 
> > i follow django girl web , expect to go to /reg to fill a form and press 
> > save button then go to web /reg/ 
> > 
> > it has error 
> > 
> > INSTALLED_APPS = ( 
> > 'django.contrib.admin', 
> > 'django.contrib.auth', 
> > 'django.contrib.contenttypes', 
> > 'django.contrib.sessions', 
> > 'django.contrib.messages', 
> > 'django.contrib.staticfiles', 
> > 'django.contrib.sites', 
> > ) 
> > 
> > MIDDLEWARE_CLASSES = ( 
> > 'django.contrib.sessions.middleware.SessionMiddleware', 
> > 'django.middleware.common.CommonMiddleware', 
> > 'django.middleware.csrf.CsrfViewMiddleware', 
> > 'django.contrib.auth.middleware.AuthenticationMiddleware', 
> > 'django.contrib.auth.middleware.SessionAuthenticationMiddleware', 
> > 'django.contrib.messages.middleware.MessageMiddleware', 
> > 'django.middleware.clickjacking.XFrameOptionsMiddleware', 
> > 'django.middleware.security.SecurityMiddleware', 
> > 'site1.reg.models.Post', 
> > ) 
> > 
> > registration.html 
> > 
> > {% block content %} 
> > 
> > New user registration 
> > 
> > {% csrf_token %} 
> > 
> > {{ form.as_p }} 
> > 
> >  > onClick="window.location.href='{% url 'reg/{{post.pk}}/' 
>  %}'">Save 
> > 
> >  
> > 
> > {% endblock %} 
> > 
> > urls.py 
> > 
> > from django.conf.urls import include, url 
> > 
> > from . import views 
> > 
> > 
> > 
> > urlpatterns = [ 
> > 
> > url(r'^reg/$', views.post_new, name='post_new'), 
> > 
> > url(r'^reg/(?P\d+)/$', views.post_detail, name='post_detail'), 
> > 
> > ] 
> > 
> > views.py 
> > 
> > from .forms import PostForm 
> > 
> > from django.shortcuts import render 
> > 
> > from django.template.loader import get_template 
> > 
> > 
> > 
> > def post_new(request): 
> > 
> > form = PostForm() 
> > 
> > return render(request, 'registration.html', {'form': form}) 
> > 
> > 
> > 
> > def post_detail(request, pk): 
> > 
> > post = get_object_or_404(Post, pk=pk) 
> > 
> > if request.method == "POST": 
> > 
> > form = PostForm(request.POST, instance=post) 
> > 
> > if form.is_valid(): 
> > 
> > post = form.save(commit=False) 
> > 
> > post.author = request.user 
> > 
> > post.ProjectName = request.ProjectName 
> > 
> > post.UserName = request.UserName 
> > 
> > post.Company = request.Company 
> > 
> > post.Contact = request.Contact 
> > 
> > post.InitialPassword = request.InitialPassword 
> > 
> > post.UserType = request.UserType 
> > 
> > post.BusinessType = request.BusinessType 
> > 
> > post.published_date = timezone.now() 
> > 
> > post.save() 
> > 
> > return redirect('registration.html', pk=post.pk) 
> > 
> > else: 
> > 
> > form = PostForm(instance=post) 
> > 
> > 
> > return render(request, 'registration.html', {'form': form}) 
> > 
> > models.py 
> > 
> > from django.db import models 
> > 
> > from django.utils import timezone 
> > from django.apps import AppConfig 
> > 
> > import csv 
> > import os.path 
> > 
> > USERTYPE = ( 
> > ('Cyberport Tenant', 'Cyberport Tenant'), 
> > ('SmartSpace User', 'SmartSpace User'), 
> > ('Cyberport Incubate', 'Cyberport Incubate'), 
> > ('Collaboration Center Subscriber', 'Collaboration Center 
> Subscriber'), 
> > ('Cyberport Alumnus', 'Cyberport Alumnus'), 
> > ('Technology Partner', 'Technology Partner'), 
> > ('HKOSUG', 'HKOSUG'), 
> > ('Others', 'Others'), 
> > ) 
> > 
> > 
> > BUSINESSTYPE = ( 
> > ('Building', 'Building'), 
> > ('Data Analysis', 'Data Analysis'), 
> > ('Digital Entertainment', 'Digital Entertainment'), 
> > ('Education', 'Education'), 
> > ('Games', 'Games'), 
> > ('Gaming', 'Gaming'), 
> > ('ICT', 'ICT'), 
> > ('Marketing', 'Marketing'), 
> > ('Social Media', 'Social Media'), 
> > ('Others', 'Others'), 
> > ) 
> > 
> > 
> > class MyAppConfig(AppConfig): 
> > name = 'src.my_app_label' 
> > 
> > def ready(self): 
> > post_migrate.connect(do_stuff, sender=self) 
> > 
> > 
> > class Post(models.Model): 
> > 
> > author = models.ForeignKey('auth.User') 
> > 
> > Email = models.CharField(max_length=70) 
> > ProjectName = models.CharField(max_length=7

Model inheritance with constraints

[Arnab Banerji]

Hi all,

I currently have a set of models associated with my Django app, with the 
database already containing data with respect to these tables (models). 

What I have
=

class MyFunModel(models.Model):
my_foo_field = 

What I am attempting to add
=

class MyAnotherFunModel(MyFunModel):
my_another_foo_field = 

Such that the migration gives me *only* _myanotherfunmodel table with 
fields "my_foo_field" and "my_another_foo_field", *without* touching any 
data in the _myfunmodel table. 

None of the options 
in https://docs.djangoproject.com/en/dev/topics/db/models/#model-inheritance 
seem to address this case, or maybe I am missing something?

Thanks,
AB

-- 
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/4f897668-3400-4d28-9c67-5d303ddd27e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: get all columns as a list

[Larry Martell]

I am the OP. I was implementing what my customer asked for. But you
make a good point that they might want the latest data not the oldest.
I will suggest that to them. Thanks.

On Wed, May 25, 2016 at 9:29 AM, Derek  wrote:
> We are both speaking as non-users of the OP's system. ;)
>
> I agree that there are some use cases for keeping the first measurement IF
> the actual date of measurement makes no difference at all.  We have an app
> like that, where we process real-time data and use a filter that only lets a
> record through if there has been a "change since previous".  On the other
> hand, changing the date means that the user has some reassurance that status
> changes have been, and are, continuing to be made.  I think we saying the
> same thing though: in general, in the absence of other constraints, try to
> retain as much data as possible and archive it in preference to simply
> tossing it.
>
> On Wednesday, 25 May 2016 00:52:01 UTC+2, James Schneider wrote:
>>
>>
>> On May 24, 2016 9:11 AM, "Derek"  wrote:
>> >
>> > Interesting. In all the cases I can think of, I would almost always want
>> > to keep the most recent check (not the oldest)... that tells me how 
>> > recently
>> > the status of X was checked.  A more pedantic administrator might also want
>> > all those times stored, so a history can be created.
>> >
>>
>> Not necessarily. You would want record of the initial change, not a record
>> of the last time that value was seen. The assumption would be that the value
>> remained constant until the next change event. What happens when the sensor
>> goes offline and online, and then continues to report the same value on
>> initialization? You wouldn't see anything until the sensor reported a
>> changed value, which could be seconds, or years. That also means you've lost
>> a data point that probably should have been captured.
>>
>> In doing so, you also potentially save a ton of write operations, since
>> keeping the latest check would require extra logic to delete the old entry
>> and create the new entry, or update the existing entry in place.
>>
>> The use case for the data would be the driver for what data needs to be
>> retained. And also the use cases that haven't been thought of.
>>
>> I personally would prefer to keep all of the data points, and summarize
>> the data in a report using logic similar to the OP's storage strategy.
>> People tend to find interesting ways to use data, and you always end up with
>> egg on your face if you are summarizing/tossing  the data on input rather
>> than filtering/analyzing output.
>>
>> Obviously this is all barring other technical restrictions that may
>> enforce a reduced data set.
>>
>> -James

-- 
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/CACwCsY6RK1rSxAm_tai2ZJBm9uoxdJtA4_PcrRvhU_JkmVs9kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: get all columns as a list

[Derek]

We are both speaking as non-users of the OP's system. ;)

I agree that there are some use cases for keeping the first measurement IF 
the actual date of measurement makes no difference at all.  We have an app 
like that, where we process real-time data and use a filter that only lets 
a record through if there has been a "change since previous".  On the other 
hand, changing the date means that the user has some reassurance that 
status changes have been, and are, continuing to be made.  I think we 
saying the same thing though: in general, in the absence of other 
constraints, try to retain as much data as possible and archive it in 
preference to simply tossing it.

On Wednesday, 25 May 2016 00:52:01 UTC+2, James Schneider wrote:
>
>
> On May 24, 2016 9:11 AM, "Derek" > wrote:
> >
> > Interesting. In all the cases I can think of, I would almost always want 
> to keep the most recent check (not the oldest)... that tells me how 
> recently the status of X was checked.  A more pedantic administrator might 
> also want all those times stored, so a history can be created.
> >
>
> Not necessarily. You would want record of the initial change, not a record 
> of the last time that value was seen. The assumption would be that the 
> value remained constant until the next change event. What happens when the 
> sensor goes offline and online, and then continues to report the same value 
> on initialization? You wouldn't see anything until the sensor reported a 
> changed value, which could be seconds, or years. That also means you've 
> lost a data point that probably should have been captured.
>
> In doing so, you also potentially save a ton of write operations, since 
> keeping the latest check would require extra logic to delete the old entry 
> and create the new entry, or update the existing entry in place.
>
> The use case for the data would be the driver for what data needs to be 
> retained. And also the use cases that haven't been thought of.
>
> I personally would prefer to keep all of the data points, and summarize 
> the data in a report using logic similar to the OP's storage strategy. 
> People tend to find interesting ways to use data, and you always end up 
> with egg on your face if you are summarizing/tossing  the data on input 
> rather than filtering/analyzing output.
>
> Obviously this is all barring other technical restrictions that may 
> enforce a reduced data set.
>
> -James
>

-- 
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/ac1260ee-c256-4ca0-8fe6-88fdca6141dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Reportlab no module named pdfgen

[Avraham Serour]

maybe you are using a version different from the documentation you are
reading
check the version you installed using 'pip freeze' or 'pip list'


On Mon, May 23, 2016 at 11:33 PM, david rodgers 
wrote:

> Hello All,
>
> I am trying to use reportlab to generate pdfs from html. When I pip
> install reportlab it say its installed correctly. However, when I try 'from
> reportlab.pdfgen import canvas' I get an error saying no module named
> pdfgen. Any ideas to help solve this would be much appreciated.
>
> 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/56450467-71c1-496c-9e48-a82d12660743%40googlegroups.com
> 
> .
> 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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFWa6tKkfnF-cuZ5rwQQtcWwCuqNZ4Qcvf40Ybvq-_1h0aGxuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading staticfiles in every single template file

[Avraham Serour]

template tag loading are not inherited


On Tue, May 24, 2016 at 2:56 PM, Branko Zivanovic <
international11...@gmail.com> wrote:

> I'm not sure why I need to add following line *{% load staticfiles %} *in
> every single template file if there is inheritance.Can I avoid this somehow?
>
> --
> 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/e98b82ac-7d6b-415d-a16c-0bb3ccc0f11e%40googlegroups.com
> 
> .
> 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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFWa6tKK5omn6-2wK2GkoAD2MaF_BFNgZgQctaaZRnoBdeNgUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: overriding date format

[Larry Martell]

On Wed, May 25, 2016 at 3:58 AM, James Schneider
 wrote:
>
> On May 24, 2016 3:32 PM, "Larry Martell"  wrote:
>>
>> I have 1 page in my app where I want to override the app's date
>> format. I tried assigning to settings.DATE_FORMAT in the view but that
>
> Django warns that settings should not be modified at runtime, which is
> probably why it had no effect:
>
> https://docs.djangoproject.com/en/1.9/topics/settings/#altering-settings-at-runtime
>
>> had no effect. I know I can format the date in the template, but
>> without making a lot of changes, I don't know what fields are dates. I
>> thought perhaps the date filter would just pass through non-dates
>> unchanged, but that's not what it did.
>>
>> How can I override the date format just for 1 view or how can I tell
>> in the template if a field is date or not?
>
> I would use one of a couple options:
>
> - Examine the data within the view, and modify those fields with the correct
> date format before passing your data off to the context to be rendered. At
> that point you still have the full complement of Python tools at your
> disposal without the drag of the template processor nuances and slower
> processing time.

Yes, that is what I ended up doing.

-- 
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/CACwCsY6kxvCXvNmXqUpC10FF0hdcycdk3eLYcVLnP4yd6Cn9dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: overriding date format

[James Schneider]

On May 24, 2016 3:32 PM, "Larry Martell"  wrote:
>
> I have 1 page in my app where I want to override the app's date
> format. I tried assigning to settings.DATE_FORMAT in the view but that

Django warns that settings should not be modified at runtime, which is
probably why it had no effect:

https://docs.djangoproject.com/en/1.9/topics/settings/#altering-settings-at-runtime

> had no effect. I know I can format the date in the template, but
> without making a lot of changes, I don't know what fields are dates. I
> thought perhaps the date filter would just pass through non-dates
> unchanged, but that's not what it did.
>
> How can I override the date format just for 1 view or how can I tell
> in the template if a field is date or not?

I would use one of a couple options:

- Examine the data within the view, and modify those fields with the
correct date format before passing your data off to the context to be
rendered. At that point you still have the full complement of Python tools
at your disposal without the drag of the template processor nuances and
slower processing time.

- Create a custom filter that acts similar to the date filter that Django
provides, but give it more intelligence to detect what values should be
modified and what format your dates should use. Run it against all of your
fields. If the field is not a date, then return the field data unscathed.

Hopefully your 'dates' are true date or datetime objects, which would be
easy to detect and format. If they are strings, obviously you'll need to be
able to determine whether or not formatting is necessary by analyzing the
string contents. If you can easily detect a date field within your custom
filter, you can probably take advantage of the Django date filter directly
since it is just another function to save yourself writing code to format
the dates once the target fields are identified.

If it were me in a one-off exception page like you stated, I'd just mangle
the data in the view and move on with life. It'll likely be faster than
having the template processor handle it for any significant number of
fields. If there is a chance you'll need this formatting magic later in
another page, the template filter may be the way to go.

-James

-- 
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/CA%2Be%2BciWnPt7urkjTpCMeBiSVuDxOseJNM7S-oipzre%2B3jPer1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.