Re: db selection from login form (a multi db app)

[acheraime]

Why would you need a db/fiscal year?

Sent from my iPhone

> On May 12, 2019, at 4:53 PM, Taimoor Qureshi  
> wrote:
> 
> Im quiet new to django. and working on a project of Accounting app in which i 
> want separate db for each fiscal year. so at the time of login their will be 
> a drop-down field of fiscal year for all values their will be a  corresponded 
> db.
> 
> any clue how to implement?
> roadmap?
> 
> TIA
> -- 
> 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/f09ec038-1f02-4f7a-9cf5-54007f9bd292%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/EFEA0B93-DB4A-4CD2-BD39-D2744AD2667C%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: formfield_overrides doesn't work

[Tim Johnson]

* Jim Illback  [190512 14:22]:
> Tim, this won’t help you to use or solve the formfield_overrides issues, but 
> maybe it will be helpful. I’ve not tried this for a CharField, but it works 
> great on a TextField (which has no max_length, so model size isn’t impacted):
> 
> 1. Install  widget tweaks and add {% load widget_tweaks %} at the top of your 
> HTML page.
> 2. On your HTML page, instantiate the field using this format: {{ 
> form.notes|attr:"rows:20"|attr:"cols:50" }} - you can use either row/cols or 
> both as in this case, and any char size.
> 
> Here’s a great usage example on widget tweaks: 
> https://simpleisbetterthancomplex.com/2015/12/04/package-of-the-week-django-widget-tweaks.html.
> 
> I hope this is useful for you.
  Thanks Jim. I had seen references to 'tweaks'
  and I will give it a try.
  cheers
-- 
Tim Johnson
http://www.tj49.com

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

db selection from login form (a multi db app)

[Taimoor Qureshi]

Im quiet new to django. and working on a project of Accounting app in which 
i want separate db for each fiscal year. so at the time of login their will 
be a drop-down field of fiscal year for all values their will be a  
corresponded db.

any clue how to implement?
roadmap?

TIA

-- 
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/f09ec038-1f02-4f7a-9cf5-54007f9bd292%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: formfield_overrides doesn't work

[Jim Illback]

Tim, this won’t help you to use or solve the formfield_overrides issues, but 
maybe it will be helpful. I’ve not tried this for a CharField, but it works 
great on a TextField (which has no max_length, so model size isn’t impacted):

1. Install  widget tweaks and add {% load widget_tweaks %} at the top of your 
HTML page.
2. On your HTML page, instantiate the field using this format: {{ 
form.notes|attr:"rows:20"|attr:"cols:50" }} - you can use either row/cols or 
both as in this case, and any char size.

Here’s a great usage example on widget tweaks: 
https://simpleisbetterthancomplex.com/2015/12/04/package-of-the-week-django-widget-tweaks.html.

I hope this is useful for you.

Jim Illback


On May 12, 2019, at 3:03 PM, Tim Johnson 
mailto:t...@akwebsoft.com>> wrote:

* Joe Reitman mailto:jreitma...@gmail.com>> [190512 
13:34]:
Tim,

I found this in the Django source code on Github searching for
'formfield_overrides'. It is in a test module testing formfield_overrides
functionality. I'm assuming you imported TextInput from forms? This should
work to change your *admin* display. Are trying to change your Admin panel
form or a form going out to the user?


class BandAdmin(admin.ModelAdmin):
formfield_overrides = {
CharField: {'widget': forms.TextInput(attrs={'size': '10'})}
}
 I am trying to change a form going to the user.
 The form in the admin page __does__ show the size attribute in
 the HTML source code for input/text.

 So it appears that formfield_overrides only affects the admin
 page.

 I'm going to call this solved - given that I can "widen" the field
 with css.

 Thanks again Joe. You've been a great help and I've learned a lot.
 cheers

--
Tim Johnson
http://www.tj49.com

--
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/20190512220300.GF2372%40mail.akwebsoft.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/8AA27AC7-87A9-4857-BFD3-929386B4EEE2%40hotmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: formfield_overrides doesn't work

[Tim Johnson]

* Joe Reitman  [190512 13:34]:
> Tim,
> 
> I found this in the Django source code on Github searching for 
> 'formfield_overrides'. It is in a test module testing formfield_overrides 
> functionality. I'm assuming you imported TextInput from forms? This should 
> work to change your *admin* display. Are trying to change your Admin panel 
> form or a form going out to the user?
> 
> 
> class BandAdmin(admin.ModelAdmin):
>  formfield_overrides = {
>  CharField: {'widget': forms.TextInput(attrs={'size': '10'})}
>  }
  I am trying to change a form going to the user. 
  The form in the admin page __does__ show the size attribute in
  the HTML source code for input/text.

  So it appears that formfield_overrides only affects the admin
  page.

  I'm going to call this solved - given that I can "widen" the field
  with css.

  Thanks again Joe. You've been a great help and I've learned a lot.
  cheers

-- 
Tim Johnson
http://www.tj49.com

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

Re: formfield_overrides doesn't work

[Joe Reitman]

Tim,

I found this in the Django source code on Github searching for 
'formfield_overrides'. It is in a test module testing formfield_overrides 
functionality. I'm assuming you imported TextInput from forms? This should 
work to change your *admin* display. Are trying to change your Admin panel 
form or a form going out to the user?


class BandAdmin(admin.ModelAdmin):
 formfield_overrides = {
 CharField: {'widget': forms.TextInput(attrs={'size': '10'})}
 }


Regards,
Joe

On Saturday, May 11, 2019 at 2:10:06 PM UTC-5, tim042849 wrote:
>
>  2.1.5 with python 3.7.2 
>
> I have a models.py class as follows: 
> class Article(models.Model): 
> title = models.CharField(max_length=255,) 
>  
> And I want to override the rendered default size attribute to 100 in 
> the input/text form field. 
>
> the template rendering is done as follows 
>  
> {% csrf_token %} 
> {{ form.as_p}} 
> Save 
>  
>
> in the application admin.py I have the following: 
> class ArticleAdmin(admin.ModelAdmin): 
> formfield_overrides = { 
> models.CharField: {'widget': TextInput(attrs={'size': '100'}), }, 
> } 
> # registered as 
> admin.site.register(Article, ArticleAdmin) 
>
> Sadly it appears to have no effect. 
> Viewing the rendered source, I do not see a size attribute. 
> the field is rendered as: 
>  
>
> Have I ommited a step? 
> thanks 
> -- 
> Tim Johnson 
> http://www.tj49.com 
>

-- 
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/97e5ce92-a476-467f-a323-a724c16c8421%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django ORM internals

[Mahdi Xareie]

Hello everyone,

I got interested in contributing to the django project recently and I 
noticed lots of tickets are related to the ORM, so it seems to me, 
contributing to the ORM is very valuable at moment.
I started to read OMR related tickets and also checking related pull 
requests, but since ORM is a big package and contains lots of modules,  
I found it very difficult to understand the changes in the pull requests.
Do you know any good resource about the internal structure of the django 
ORM? a blog post perhaps, anythong to help me get started on the ORM 
internals.


Thank you very much


--
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/ab604221-d821-ef39-0f46-c48a985020a6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: formfield_overrides doesn't work

[Tim Johnson]

* Joe Reitman  [190512 10:31]:
> Tim,
> 
> Here is an example of a custom form field limiting the input to 100 
> characters. The model is defined to accept 255 chars. BTW, the text widget 
> 'attrs' sets the HTML form element attributes.
> 
> class SearchForm(forms.Form):
> 
>  search_for = forms.CharField(
>  label='',
>  label_suffix='',
>  max_length=100,
>  required=True,
>  widget=forms.TextInput(attrs={'placeholder': 'search', ' autofocus': ''}),
>  help_text='',
>  error_messages={'required': ''},
>  )
  Hi Joe:
  Thanks for the reply.
  I did try using a custom class in admin.py
  class LongTextinput(TextInput):
def __init__(self, *args, **kwargs):
attrs = kwargs.setdefault('attrs', {})
# code below aims to add a size="100" attribute
# to rendered html
attrs.setdefault('size', 100)
super(LongTextinput, self).__init__(*args, **kwargs)
implemented with formfields_ovverides as 
in :
formfield_overrides = {
models.CharField: {'widget': LongTextinput},
}
but did not have the desired effect.

the larger question is:
why is formfield_overrides not having the effect I expected?
I.E. size="100" is added to the rendered html.

According to documentation the implementation should be pretty straightforward.

Do you suppose that there is a particular plugin that enables 
formfield_overrides?

**OR** is {{ form.as_p }} in the template inhibiting the rendering?

My goal was not to change the max_length attribute, but the size attribute in
the rendered HTML code.

For the record, css widens the input field, and that gave me the
input width I sought, but the edification I seek is to understand
how to use formfield_overrides.

cheers
-- 
Tim Johnson
http://www.tj49.com

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

Re: formfield_overrides doesn't work

[Joe Reitman]

Tim,

Here is an example of a custom form field limiting the input to 100 
characters. The model is defined to accept 255 chars. BTW, the text widget 
'attrs' sets the HTML form element attributes.

class SearchForm(forms.Form):

 search_for = forms.CharField(
 label='',
 label_suffix='',
 max_length=100,
 required=True,
 widget=forms.TextInput(attrs={'placeholder': 'search', ' autofocus': ''}),
 help_text='',
 error_messages={'required': ''},
 )


On Saturday, May 11, 2019 at 2:10:06 PM UTC-5, tim042849 wrote:
>
> django 2.1.5 with python 3.7.2 
>
> I have a models.py class as follows: 
> class Article(models.Model): 
> title = models.CharField(max_length=255,) 
>  
> And I want to override the rendered default size attribute to 100 in 
> the input/text form field. 
>
> the template rendering is done as follows 
>  
> {% csrf_token %} 
> {{ form.as_p}} 
> Save 
>  
>
> in the application admin.py I have the following: 
> class ArticleAdmin(admin.ModelAdmin): 
> formfield_overrides = { 
> models.CharField: {'widget': TextInput(attrs={'size': '100'}), }, 
> } 
> # registered as 
> admin.site.register(Article, ArticleAdmin) 
>
> Sadly it appears to have no effect. 
> Viewing the rendered source, I do not see a size attribute. 
> the field is rendered as: 
>  
>
> Have I ommited a step? 
> thanks 
> -- 
> Tim Johnson 
> http://www.tj49.com 
>

-- 
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/9bd73f0f-a944-4a0e-9c2e-2ea2db7974c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: problems with mysql client

[Rob W]

I did, but believe it or not, that install fails too.


> On May 11, 2019, at 12:12 PM, Jorge Gimeno  wrote:
> 
> Rob,
> 
> On the off chance you haven't seen it, I found a Stack Overflow question on 
> this:  
> https://stackoverflow.com/questions/25459386/mac-os-x-environmenterror-mysql-config-not-found
>  
> .
>  Unfortunately, I don't know Mac OS all that well to offer more help than 
> that.
> 
> -Jorge
> 
> On Sat, May 11, 2019 at 9:04 AM Rob Gmail  > wrote:
> Mac OS 
> 
> Rob 
> 203-671-6514
> Sent from my mobile device, please excuse the typos. 
> 
> On May 11, 2019, at 11:42 AM, Jorge Gimeno  > wrote:
> 
>> 
>> 
>> On Sat, May 11, 2019 at 8:16 AM Rob W > > wrote:
>> for my django project, we are using mysql.
>> 
>> no matter how i try to install it, python-mysqldb, or just pip install 
>> mysqlclient, it fails.
>> 
>> i've installed mysqlconnector, i've tried everything. 
>> 
>> any suggestions ?
>> 
>> 
>> Collecting mysqlclient
>> 
>>   Downloading 
>> https://files.pythonhosted.org/packages/f4/f1/3bb6f64ca7a429729413e6556b7ba5976df06019a5245a43d36032f1061e/mysqlclient-1.4.2.post1.tar.gz
>>  
>> 
>>  (85kB)
>> 
>>  || 92kB 1.3MB/s 
>> 
>> ERROR: Complete output from command python setup.py egg_info:
>> 
>> ERROR: /bin/sh: mysql_config: command not found
>> 
>> Traceback (most recent call last):
>> 
>>   File "", line 1, in 
>> 
>>   File "/private/tmp/pip-install-suhqq3eh/mysqlclient/setup.py", line 
>> 16, in 
>> 
>> metadata, options = get_config()
>> 
>>   File "/private/tmp/pip-install-suhqq3eh/mysqlclient/setup_posix.py", 
>> line 51, in get_config
>> 
>> libs = mysql_config("libs")
>> 
>>   File "/private/tmp/pip-install-suhqq3eh/mysqlclient/setup_posix.py", 
>> line 29, in mysql_config
>> 
>> raise EnvironmentError("%s not found" % (_mysql_config_path,))
>> 
>> OSError: mysql_config not found
>> 
>> 
>> 
>> ERROR: Command "python setup.py egg_info" failed with error code 1 in 
>> /private/tmp/pip-install-suhqq3eh/mysqlclient/
>> 
>> 
>> -- 
>> 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/31f86e65-7e0a-49c7-b574-1670fba1ca18%40googlegroups.com
>>  
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
>> 
>> Rob,
>> 
>> What operating system are you using?
>> 
>> -Jorge 
>> 
>> -- 
>> 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/CANfN%3DK-vw16fWxhZYa3f8VP6t6cCi5BA%2BoNtjmof99CQWNKb-Q%40mail.gmail.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 
> 

Re: How to proceed with my Pull request?

[Mahdi Xareie]

   Mahdi,


   You may be waiting for a bit.  As a general statement, package and
   framework maintainers are volunteers and tend to work on their
   projects around the other priorities in their lives. It's normal for
   a bit of a delay in getting something accepted.  You can certainly
   contact the maintainer, but I wouldn't expect a response right away.

   -Jorge


Hey Jorge,

I'm thinking maybe I miss something in my pull request, some 
contribution rules perhaps, it would be great if you could take a look 
at my pull request, just to ensure if it's ready for review.


thank you very much


--
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/70230b86-60a1-8edb-71f7-f3bf682cf954%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to proceed with my Pull request?

[Jorge Gimeno]

Mahdi,

You may be waiting for a bit.  As a general statement, package and
framework maintainers are volunteers and tend to work on their projects
around the other priorities in their lives. It's normal for a bit of a
delay in getting something accepted.  You can certainly contact the
maintainer, but I wouldn't expect a response right away.

-Jorge

On Sun, May 12, 2019 at 7:27 AM Mahdi Xareie  wrote:

> Hello everyone
>
> I'm newbie in open-source contribution and I need a little guidance.
> I've sent a pull request containing a few lines of tests to django
> repository few days ago, since nothing happened in the past three days
> I'm wondering what should I do now?did I miss something?
>
> Mahdi Xarei
>
> --
> 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/eab2cf43-2a5c-9c91-9a81-acf092eddccd%40gmail.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/CANfN%3DK-UYEzj7es2UAwrWs1PCpWRr5uqW5Zw_cKqZ1QgMGbH2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

How to proceed with my Pull request?

[Mahdi Xareie]

Hello everyone

I'm newbie in open-source contribution and I need a little guidance. 
I've sent a pull request containing a few lines of tests to django 
repository few days ago, since nothing happened in the past three days 
I'm wondering what should I do now?did I miss something?


Mahdi Xarei

--
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/eab2cf43-2a5c-9c91-9a81-acf092eddccd%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Static files won't match the path given

[Joe Reitman]

Configuring static files can be a headache. I personally use Whitenoise 
 to serve my static files. It is 
self contained and can be configured in Django settings after installation. 

A couple of advantages of Whitenoise:

1. During development you can override the Django's static file server by 
putting 'whitenoise.runserver_nostatic' in Installed Apps. This way you can 
have the same behaviour on your local machine as you'll have on your hosted 
server.
2. You don't have to mess with Apache or Nginx settings. 

On Saturday, May 11, 2019 at 12:23:11 AM UTC-5, Rookies DJ wrote:
>
> I apologise, I'm a hardware engineer, I'm not very familiar with coding; 
> I'm only on Django for the past 5 months. (under my boss order)
>
> I had managed to develop and establish a Django App, and manage to upload 
> it to remote server *NameCheap*. There on the server, the issue is unable 
> to locate the static files. Even when we directed the path to static files 
> folder.
>
> This static files, infrequently work and load the static, that's how we 
> concluded the static error was caused by the misdirection of the path.
>
> But reading over the Django documentary multiple time didn't help resolve 
>
> Please help our team had been trying resolve this issue for past 2months 
>

-- 
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/c73ff13e-4328-4a08-87c3-41a9e44db6bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.