Re: Business logic constants

[Derek]

There are many types of constants. We have a 'utils' directory (at same 
level as 'apps') and under that 'constants' sub-directory - with different 
files for different types of constants that are generally applicable across 
all apps.  But because we have lots of client-specific constants and coding 
of their business rules, those sit under their own structure elsewhere.  
Using imports though, makes it relatively easier to reorganise over time if 
you need to.

The Django settings file is really only for constants related to starting 
up the program itself (and in our case a single flag to track who the 
client is). 

On Sunday, 30 May 2021 at 13:17:10 UTC+2 ypolo...@gmail.com wrote:

> When working with business logic implementation code and you do not want 
> use magic numbers in the code - where is the best place to put all those 
> CONSTANTS ? Django settings file ?
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/0ea0826a-e313-43f5-b65b-e488cfd194b3n%40googlegroups.com.

Re: Filtering fields in http response data from http request url ?

[Mottaz Hegaze]

Using Django Rest Framework , you can alter the output by overriting
function to_represent in serializer.

On Mon, 31 May 2021, 1:26 am Adaeit Telle,  wrote:

> Hi Django Developers,
> Json response from the django server is huge as the data fields contained
> are of big size.
> So, can I restrict the *fields* required in the response data from the
> *HTTP Request Url* ?
> Is there a generic param, which can be used ?
>
> Just like QuerySet, can we have "ValueSet" to restrict the fields(or
> columns) in the json response data ?
>
> Regards,
> Adaeit
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/f274b86b-e3fb-483b-802e-857362087619n%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAHV4E-dB0%3DHha6HgCoG4igdBbyyjPbQMO3rjkZBPaHH6_Kwscw%40mail.gmail.com.

Filtering fields in http response data from http request url ?

[Adaeit Telle]

Hi Django Developers,
Json response from the django server is huge as the data fields contained 
are of big size. 
So, can I restrict the *fields* required in the response data from the 
*HTTP Request Url* ? 
Is there a generic param, which can be used ? 

Just like QuerySet, can we have "ValueSet" to restrict the fields(or 
columns) in the json response data ? 

Regards,
Adaeit

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f274b86b-e3fb-483b-802e-857362087619n%40googlegroups.com.

Re: Newbee help on deploying Django App to Apache2

[Moose Smith]

Thanks Guy  Very helpful thanks for the information. I'm working the issue 
right now.

On Sunday, May 30, 2021 at 10:30:18 AM UTC-4 Antonis Christofides wrote:

> Apache and nginx are called "web servers". Windows and FreeBSD are called 
> "operating systems". What is the term for Gunicorn, uWSGI and mod_wsgi? I 
> believe there's no good term, which is one reason for the confusion.
>
> Gunicorn, uWSGI and mod_wsgi are specialized web servers that run Python 
> WSGI-compliant applications. For lack of a better name, I'll call them 
> Python application servers, but don't forget that they are nothing more 
> (and nothing less) than specialized web servers that run Python 
> WSGI-compliant applications.
>
> What the Python application server does is
>
> from djpro.wsgi import application
>
> and then, in each HTTP request, it calls application() in a standard way 
> that is specified by the WSGI specification. The fact that the interface of 
> this function is standardized is what permits you to choose between many 
> different Python application servers such as Gunicorn, uWSGI, or mod_wsgi, 
> and why each of these can interact with many Python application frameworks 
> like Django or Flask.
>
> The Python application server does not *communicate* with the Django 
> project, it *imports* the Django project. From the point of view of the 
> operating system, it is the same process. You don't have a separate server 
> which "runs" or "communicates with" Django, which would mean that the 
> Python application server and Django could run in separate virtualenvs. You 
> have a single Python program and there is only one virtualenv. What we do 
> for Gunicorn, for example, is install it in the same virtualenv where we 
> have Django (pip install gunicorn), and then run it from there.
>
> I am not familiar with mod_wsgi, but the thing is, by the time it's ready 
> to import the Django project, Python is already running, and you can't 
> select or change a virtualenv any more. So selecting a virtualenv (which I 
> assume is possible) must be in the mod_wsgi configuration. I hope these 
> principles help you understand mod_wsgi's documentation.
>
> I find Gunicorn an easier and better way to deploy, regardless the web 
> server. More information:
>
>- How to setup Apache with Gunicorn 
>
>  
>- Detailed instructions on setting up Gunicorn 
>
>
> Antonis Christofides+30-6979924665 <+30%20697%20992%204665> (mobile)
>
>
>
> On 30/05/2021 09.29, Moose Smith wrote:
>
> App written in ubuntu virtual environment python 3.8.5. Works well on 
> Visual Studio Code development server. Am trying to make it run on Apache2 
> development server.  I have been able to install WSGI module on Apache 
> Server and ran a test Hello World in Python and it worked. However, the 
> django app when ported over does not work.  
> The error log confirms that the mod_wsgi has been created using by Python 
> 3.8  
> [mpm_event:notice] [pid 607786:tid 140700034231360] AH00489: Apache/2.4.41 
> (Ubuntu) mod_wsgi/4.6.8 Python/3.8 configured -- resuming normal operations
> The error I am getting indicates that the Apache / WSGI is reading the 
> files in the virtual environment I copied over.  
>
> mod_wsgi (pid=609049): Exception occurred processing WSGI script '/ File 
> "/usr/public/apache/MCE/learn/djpro/wsgi.py", line 12, in 
> from django.core.wsgi import get_wsgi_application
> ModuleNotFoundError: No module named 'django'
>
> My research indicates that this error occurs when the mod--wsgi in being 
> interpreted by a different version than what was used to create my virtual 
> environment. It also might be permissions/ownership issues with the file 
> and directories copied over to the server, or improperly configured module. 
>
> My question is this: Does the mod_WSGI module have to be the same as the 
> one that created my virtual environment?  My understanding is that WSGI has 
> two components, the server side, and the application side. It would not 
> make sense that the Server side MUST match the application side because it 
> would not be possible to service various apps with different versions of 
> Python/Django. I assumed the server side was python version independent and 
> that the requirement for Python similarity was only on the application side 
> in that the Python used to create the virtual environment and my app must 
> match the version used to create the WSGI interface on the application side 
> (this side not the server). That said, I have discovered there is a Python 
> 2.7 version of the mod_WSGI for the server side which differs from the 3.7 
> version. 
>
> Can someone clear up the Python version requirement and if it does require 
> a match between the server and the app side, how will I be able to run 
> future versions of Python/Django apps without

Re: Newbee help on deploying Django App to Apache2

[Antonis Christofides]

Apache and nginx are called "web servers". Windows and FreeBSD are called 
"operating systems". What is the term for Gunicorn, uWSGI and mod_wsgi? I 
believe there's no good term, which is one reason for the confusion.


Gunicorn, uWSGI and mod_wsgi are specialized web servers that run Python 
WSGI-compliant applications. For lack of a better name, I'll call them Python 
application servers, but don't forget that they are nothing more (and nothing 
less) than specialized web servers that run Python WSGI-compliant applications.


What the Python application server does is

    from djpro.wsgi import application

and then, in each HTTP request, it calls application() in a standard way that is 
specified by the WSGI specification. The fact that the interface of this 
function is standardized is what permits you to choose between many different 
Python application servers such as Gunicorn, uWSGI, or mod_wsgi, and why each of 
these can interact with many Python application frameworks like Django or Flask.


The Python application server does not *communicate* with the Django project, it 
*imports* the Django project. From the point of view of the operating system, it 
is the same process. You don't have a separate server which "runs" or 
"communicates with" Django, which would mean that the Python application server 
and Django could run in separate virtualenvs. You have a single Python program 
and there is only one virtualenv. What we do for Gunicorn, for example, is 
install it in the same virtualenv where we have Django (pip install gunicorn), 
and then run it from there.


I am not familiar with mod_wsgi, but the thing is, by the time it's ready to 
import the Django project, Python is already running, and you can't select or 
change a virtualenv any more. So selecting a virtualenv (which I assume is 
possible) must be in the mod_wsgi configuration. I hope these principles help 
you understand mod_wsgi's documentation.


I find Gunicorn an easier and better way to deploy, regardless the web server. 
More information:


 * How to setup Apache with Gunicorn
   
 * Detailed instructions on setting up Gunicorn
   

Antonis Christofides
+30-6979924665 (mobile)



On 30/05/2021 09.29, Moose Smith wrote:
App written in ubuntu virtual environment python 3.8.5. Works well on Visual 
Studio Code development server. Am trying to make it run on Apache2 
development server.  I have been able to install WSGI module on Apache Server 
and ran a test Hello World in Python and it worked. However, the django app 
when ported over does not work.

The error log confirms that the mod_wsgi has been created using by Python 3.8
[mpm_event:notice] [pid 607786:tid 140700034231360] AH00489: Apache/2.4.41 
(Ubuntu) mod_wsgi/4.6.8 Python/3.8 configured -- resuming normal operations
The error I am getting indicates that the Apache / WSGI is reading the files 
in the virtual environment I copied over.


mod_wsgi (pid=609049): Exception occurred processing WSGI script '/ File 
"/usr/public/apache/MCE/learn/djpro/wsgi.py", line 12, in 

from django.core.wsgi import get_wsgi_application
ModuleNotFoundError: No module named 'django'

My research indicates that this error occurs when the mod--wsgi in being 
interpreted by a different version than what was used to create my virtual 
environment. It also might be permissions/ownership issues with the file and 
directories copied over to the server, or improperly configured module.


My question is this: Does the mod_WSGI module have to be the same as the one 
that created my virtual environment?  My understanding is that WSGI has two 
components, the server side, and the application side. It would not make sense 
that the Server side MUST match the application side because it would not be 
possible to service various apps with different versions of Python/Django. I 
assumed the server side was python version independent and that the 
requirement for Python similarity was only on the application side in that the 
Python used to create the virtual environment and my app must match the 
version used to create the WSGI interface on the application side (this side 
not the server). That said, I have discovered there is a Python 2.7 version of 
the mod_WSGI for the server side which differs from the 3.7 version.


Can someone clear up the Python version requirement and if it does require a 
match between the server and the app side, how will I be able to run future 
versions of Python/Django apps without having to go back and "recomplie"?


Also if someone has any clues on solving my error that would be very much 
appreciated.


Thanks
Moose
--
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...@googlegroup

Re: Newbee help on deploying Django App to Apache2

[Chetan Ganji]

I think, you are using the default python version installed on the machine,
not the one of the virtualenv.
You will have to configure the mod_wsgi to use the python of the virtuelanv.

This might help you.
https://modwsgi.readthedocs.io/en/develop/user-guides/virtual-environments.html#


Regards,
Chetan Ganji
+91-900-483-4183
ganji.che...@gmail.com
http://ryucoder.in


On Sun, May 30, 2021 at 4:46 PM Moose Smith <47kanga...@gmail.com> wrote:

> App written in ubuntu virtual environment python 3.8.5. Works well on
> Visual Studio Code development server. Am trying to make it run on Apache2
> development server.  I have been able to install WSGI module on Apache
> Server and ran a test Hello World in Python and it worked. However, the
> django app when ported over does not work.
> The error log confirms that the mod_wsgi has been created using by Python
> 3.8
> [mpm_event:notice] [pid 607786:tid 140700034231360] AH00489: Apache/2.4.41
> (Ubuntu) mod_wsgi/4.6.8 Python/3.8 configured -- resuming normal operations
> The error I am getting indicates that the Apache / WSGI is reading the
> files in the virtual environment I copied over.
>
> mod_wsgi (pid=609049): Exception occurred processing WSGI script '/ File
> "/usr/public/apache/MCE/learn/djpro/wsgi.py", line 12, in 
> from django.core.wsgi import get_wsgi_application
> ModuleNotFoundError: No module named 'django'
>
> My research indicates that this error occurs when the mod--wsgi in being
> interpreted by a different version than what was used to create my virtual
> environment. It also might be permissions/ownership issues with the file
> and directories copied over to the server, or improperly configured module.
>
> My question is this: Does the mod_WSGI module have to be the same as the
> one that created my virtual environment?  My understanding is that WSGI has
> two components, the server side, and the application side. It would not
> make sense that the Server side MUST match the application side because it
> would not be possible to service various apps with different versions of
> Python/Django. I assumed the server side was python version independent and
> that the requirement for Python similarity was only on the application side
> in that the Python used to create the virtual environment and my app must
> match the version used to create the WSGI interface on the application side
> (this side not the server). That said, I have discovered there is a Python
> 2.7 version of the mod_WSGI for the server side which differs from the 3.7
> version.
>
> Can someone clear up the Python version requirement and if it does require
> a match between the server and the app side, how will I be able to run
> future versions of Python/Django apps without having to go back and
> "recomplie"?
>
> Also if someone has any clues on solving my error that would be very much
> appreciated.
>
> Thanks
> Moose
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/d3041741-1604-473f-8810-263bb3b16c59n%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAMKMUjuOXoG5O0-aGFpMD3wfkNHkOMqBf8PNsKhFeeJvwrpYAQ%40mail.gmail.com.

Re: CSS not linking with HTML

[Kasper Laudrup]

On 30/05/2021 05.43, sukhy gill wrote:
> Getting error while using using command python manage.py collectstatic
> Regarda
>

Try fixing the error and see if that makes the problem go away.

I know it's a long shot, but it's worth a try at least.

Kind regards,

Kasper Laudrup


> On Sat, May 29, 2021, 21:23 Mehdi Ismail   wrote:
> 
> python manage.py collectstatic 
> 
> 
> try that... and update
> On Saturday, 29 May 2021 at 20:44:48 UTC+5:30 sukhy.g...@gmail.com
>  wrote:
> 
> Project Folder ➡️static ➡️css➡️style.css➡️
> 
> On Sat, May 29, 2021, 19:16 Fabiano Leite  wrote:
> 
> 
> Where is located your 'css/style.css';
> Em sábado, 29 de maio de 2021 às 10:04:50 UTC-3,
> sukhy.g...@gmail.com escreveu:
> 
> No dear
> 
> On Sat, May 29, 2021, 18:29 Chelsea Fan
>  
> Is it working now?
> 
> On Sat, 29 May 2021, 3:40 pm lalit suthar,
>  wrote:
> 
> read
> this 
> https://docs.djangoproject.com/en/2.2/intro/tutorial06/
> 
> 
> and check how you are giving paths. Also after
> loading the page on your browser go to "View
> Page Source" and click on the CSS file link and
> check if the file is opening or not.
> 
> On Saturday, 29 May 2021 at 17:57:21 UTC+5:30
> sukhy.g...@gmail.com wrote:
> 
> Yes Sir,There was no mistake in code. Code
> problem was only in mail content actually
> code was correct as instruction given by
> Aniket Sir
> 
> Regards
> 
> 
> On Sat, May 29, 2021, 13:14 lalit suthar
>  
> have you checked Aniket's answer?
> 
> On Saturday, 29 May 2021 at 11:09:07
> UTC+5:30 sukhy.g...@gmail.com wrote:
> 
> Done Sir, but not working
> 
> On Sat, May 29, 2021, 10:50 Venu
> Gopal  
> In Firefox  Goto Preferences
> ---> Choose Privacy and Security
> ---> scroll down until you get
> cookies and site data --> clear data
> Chrome  Goto Settings --->
> Choose Privacy and Security --->
> select cookies and other site
> data --> select see all cookies
> and site data --> Remove all
> 
> On Sat, May 29, 2021 at 9:50 AM
> sukhy gill
>  wrote:
> 
> @Venu Gopal
> 
> No Sir, I don't know, how to
> do this.
> 
> May I know Sir, how to do
> the same?
> 
> Regards
> 
> On Sat, May 29, 2021, 09:41
> Venu Gopal
>  
> Hi, Have you tried
> deleting existing cache
> and cookies in the browser?
> 
> On Sat, May 29, 2021 at
> 12:08 AM sukhy gill
> 
> wrote:
> 
> Dear Frnds
>                 I am
> unable to  link CSS
> with HTML
> HTML working but CSS
> not working inside
> the .html file with
> the help of LINK in
> 

Re: CSS not linking with HTML

[Mehdi Ismail]

you want to mention (provide screenshot) of the error?

On Sunday, 30 May 2021 at 09:14:22 UTC+5:30 sukhy.g...@gmail.com wrote:

> Getting error while using using command python manage.py collectstatic
> Regarda
>
> On Sat, May 29, 2021, 21:23 Mehdi Ismail 
>> python manage.py collectstatic 
>>
>>
>> try that... and update
>> On Saturday, 29 May 2021 at 20:44:48 UTC+5:30 sukhy.g...@gmail.com wrote:
>>
>>> Project Folder ➡️static ➡️css➡️style.css➡️
>>>
>>> On Sat, May 29, 2021, 19:16 Fabiano Leite >>

 Where is located your 'css/style.css';
 Em sábado, 29 de maio de 2021 às 10:04:50 UTC-3, sukhy.g...@gmail.com 
 escreveu:

> No dear
>
> On Sat, May 29, 2021, 18:29 Chelsea Fan 
>> Is it working now?
>>
>> On Sat, 29 May 2021, 3:40 pm lalit suthar,  
>> wrote:
>>
>>> read this https://docs.djangoproject.com/en/2.2/intro/tutorial06/ 
>>> and check how you are giving paths. Also after loading the page on your 
>>> browser go to "View Page Source" and click on the CSS file link and 
>>> check 
>>> if the file is opening or not.
>>>
>>> On Saturday, 29 May 2021 at 17:57:21 UTC+5:30 sukhy.g...@gmail.com 
>>> wrote:
>>>
 Yes Sir,There was no mistake in code. Code problem was only in mail 
 content actually code was correct as instruction given by Aniket Sir

 Regards


 On Sat, May 29, 2021, 13:14 lalit suthar >>> wrote:

> have you checked Aniket's answer?
>
> On Saturday, 29 May 2021 at 11:09:07 UTC+5:30 sukhy.g...@gmail.com 
> wrote:
>
>> Done Sir, but not working
>>
>> On Sat, May 29, 2021, 10:50 Venu Gopal > wrote:
>>
>>> In Firefox  Goto Preferences ---> Choose Privacy and 
>>> Security ---> scroll down until you get cookies and site data --> 
>>> clear data
>>> Chrome  Goto Settings ---> Choose Privacy and Security ---> 
>>> select cookies and other site data --> select see all cookies and 
>>> site data 
>>> --> Remove all
>>>
>>> On Sat, May 29, 2021 at 9:50 AM sukhy gill  
>>> wrote:
>>>
 @Venu Gopal

 No Sir, I don't know, how to do this.

 May I know Sir, how to do the same?

 Regards

 On Sat, May 29, 2021, 09:41 Venu Gopal >>> wrote:

> Hi, Have you tried deleting existing cache and cookies in the 
> browser? 
>
> On Sat, May 29, 2021 at 12:08 AM sukhy gill <
> sukhy.g...@gmail.com> wrote:
>
>> Dear Frnds
>> I am unable to  link CSS with HTML
>> HTML working but CSS not working inside the .html file with 
>> the help of LINK in  tag 
>>
>> I am using thefollowings:-
>> Setting.py -  STATICFILES_DIRS=[os.path.join(BASE_DIR, 
>> 'static'),]
>> HTML- {% load static %}
>> > To unsubscribe from this group and stop receiving emails from 
>> it, send an email to django-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/3ca2aba0-a58f-4298-b248-16c51bdf90a6n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> 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/qGMoFXNAgww/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an 
> email to django-users...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CAOhYkiyqw8k5zCL1XZo9U%2BY9_JR57p55xf-%3DtFf6Fa4HVskPSw%40mail.gmail.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...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/django-users/CAJ8btZave0utnYTAcrxafKes6sUZ3%2BX%2

Business logic constants

[yuriy polonskiy]

When working with business logic implementation code and you do not want 
use magic numbers in the code - where is the best place to put all those 
CONSTANTS ? Django settings file ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/0d394489-0407-4b74-adf8-0f2c46b1da9en%40googlegroups.com.

Newbee help on deploying Django App to Apache2

[Moose Smith]

App written in ubuntu virtual environment python 3.8.5. Works well on 
Visual Studio Code development server. Am trying to make it run on Apache2 
development server.  I have been able to install WSGI module on Apache 
Server and ran a test Hello World in Python and it worked. However, the 
django app when ported over does not work. 
The error log confirms that the mod_wsgi has been created using by Python 
3.8  
[mpm_event:notice] [pid 607786:tid 140700034231360] AH00489: Apache/2.4.41 
(Ubuntu) mod_wsgi/4.6.8 Python/3.8 configured -- resuming normal operations
The error I am getting indicates that the Apache / WSGI is reading the 
files in the virtual environment I copied over.  

mod_wsgi (pid=609049): Exception occurred processing WSGI script '/ File 
"/usr/public/apache/MCE/learn/djpro/wsgi.py", line 12, in 
from django.core.wsgi import get_wsgi_application
ModuleNotFoundError: No module named 'django'

My research indicates that this error occurs when the mod--wsgi in being 
interpreted by a different version than what was used to create my virtual 
environment. It also might be permissions/ownership issues with the file 
and directories copied over to the server, or improperly configured module. 

My question is this: Does the mod_WSGI module have to be the same as the 
one that created my virtual environment?  My understanding is that WSGI has 
two components, the server side, and the application side. It would not 
make sense that the Server side MUST match the application side because it 
would not be possible to service various apps with different versions of 
Python/Django. I assumed the server side was python version independent and 
that the requirement for Python similarity was only on the application side 
in that the Python used to create the virtual environment and my app must 
match the version used to create the WSGI interface on the application side 
(this side not the server). That said, I have discovered there is a Python 
2.7 version of the mod_WSGI for the server side which differs from the 3.7 
version. 

Can someone clear up the Python version requirement and if it does require 
a match between the server and the app side, how will I be able to run 
future versions of Python/Django apps without having to go back and 
"recomplie"?

Also if someone has any clues on solving my error that would be very much 
appreciated.

Thanks
Moose

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d3041741-1604-473f-8810-263bb3b16c59n%40googlegroups.com.