Re: i need help

2018-08-11 Thread Aladin Masen
I want to use it in my admin 


Sent from my iPhone

> On Aug 9, 2018, at 7:16 PM, Kasper Laudrup  wrote:
> 
> Hi Aladin,
> 
>> On 09/08/2018 15.07, Aladin Masen wrote:
>> Please how can i use the django_markdown  with django 2
> 
> You probably can't, since the library seems to be unmaintained and not 
> updated for use with Django 2, unless you want to fork it and make the 
> changes needed for supporting Django 2.
> 
> I have used django-markdownx:
> 
> https://neutronx.github.io/django-markdownx/
> 
> Which was just fine for my (very basic) requirements.
> 
> A better option might be to use django-markup:
> 
> https://django-markup.readthedocs.io/en/latest/index.html
> 
> I don't have any experience with that, but I plan to look into it.
> 
> Hope that helps.
> 
> Kind regards,
> 
> Kasper Laudrup
> 
> -- 
> 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/46ae51c1-773b-8bda-7ecd-167d790654fa%40stacktrace.dk.
> 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/56039CF3-9CCC-4102-BCFA-A9C7E7FE9D35%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to connect to SQL Server 2012 from current version of DJango and Python

2018-08-11 Thread Jason
the dev for that library has specified that this is not compatible with 
django 2.1.  so your options are to either find another connector library 
compatible with 2.1 or downgrade to using 2.0.x

https://github.com/michiya/django-pyodbc-azure/blob/azure-2.0/setup.py#L29

>

-- 
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/c33146dc-209c-4978-8d38-2c87e55c6ea1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Unexpected behavior with icontains in query filter

2018-08-11 Thread Jason
Are you using sqlite for your db?  if so, there are some notes about case 
insensitive matching at 
https://docs.djangoproject.com/en/dev/ref/databases/#sqlite-string-matching

otherwise, I'd be interested in seeing what your SQL is like

in your django shell, do the following:

doctors = Doctors.objects.filter(name__icontains = 'joel')
print(doctors.query)

It should have something like 

SELECT ... FROM ... WHERE name ILIKE  '%joel%';

which should do the case insensitive search.

Otherwise, this is a database issue, and not a django issue.  Django just 
converts the filter call to the appropriate SQL and has the db execute it.

-- 
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/2b8dd9eb-b1ab-4eaf-ac17-4f03c1ed1c2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Unexpected behavior with icontains in query filter

2018-08-11 Thread ireoluwa fakeye
The only reasonable explanation is Django sees only upper case inputs as
being case sensitive .so inputting  a lower case and specifying icontains
wouldnt change anything .you could get your input from a form to confirm

On Fri., 10 Aug. 2018, 18:06 Joel,  wrote:

> I'm trying to do a case insensitive search for a substring within a field
> in my model.
>
> My model:
>
>
> class doctor(models.Model):
> docid = models.AutoField(primary_key=True, unique=True) # Need
> autoincrement, unique and primary
> name = models.CharField(max_length=35)
> username = models.CharField(max_length=15)
> regid = models.CharField(max_length=15, default="", blank=True)
> photo = models.CharField(
> max_length=35, default="", blank=True)
> email = models.EmailField(default="", blank=True)
> phone = models.CharField(max_length=15)
> qualifications = models.CharField(
> max_length=50, default="", blank=True)
> about = models.CharField(
> max_length=35, default="", blank=True)
> specialities = models.CharField(
> max_length=50, default="", blank=True)
> department = models.CharField(max_length=50, default="ENT", blank=
> True)
> fees = models.FloatField(default=300.0)
> displayfee = models.IntegerField(default=0, blank=True)
> slotrange = models.CharField(max_length=50, blank=True)
> slotdurn = models.IntegerField(default=10)
> breakrange = models.CharField(
> max_length=50, default="", blank=True)
> slotsleft = models.CharField(
> max_length=50, default="", blank=True)
> def __str__(self):
> return self.name
> def Range(self):
> return self.slotrange
> def listslots(self):
> SlotRange = self.slotrange
> SlotDurn = self.slotdurn
> startime = SlotRange.split('-')[0]
> endtime = SlotRange.split('-')[1]
> sthr, stmin = SplitTimeString(startime)
> enhr, enmin = SplitTimeString(endtime)
> print(stamptoday(sthr, stmin))
> print(stamptoday(enhr, enmin))
> startstamp = stamptoday(sthr, stmin)
> endstamp = stamptoday(enhr, enmin)
> secdurn = SlotDurn*60
> slotlist = []
> for sec in range(startstamp, endstamp, secdurn):
> enttime = sec + secdurn
> myrange = ("%s - %s" % (HumanTime(sec),
> HumanTime(enttime)))
> slotlist.append(myrange)
> return slotlist
>
>
> Under the field 'name' in my mysql database, are two rows with values for
> name as 'Joel' and 'Jaffy Joel'.
>
> When I do the search like this:
>
>
> from appointments.models import customer, doctor, appointment
> doctor.objects.filter(name__icontains='joel')
>
>
> Output:
>
>
> 
>
>
> But when I do:
>
> doctor.objects.filter(name__icontains='Joel')
>
>
>
> Output:
>
>
>  , ]>
>
>
> Why isnt the case insensitive search working for a lowercase search?
>
> I'm on django 2.0.7
>
> --
> 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/46579c92-8a12-4977-814c-9c3fcaa14711%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/CAO87g11GdDTaDAVNUXmn-09j7ZQ2c8Jr_kR6pc-6aq6L8JTjAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re:

2018-08-11 Thread Bill Freeman
A context contains the variables that you want your template to be able to
access.  It is common to want to access stuff from the request.  You could
copy those things that you need into the dict that you pass to the Context
constructor or define an element of the dict to hold the Request object and
let the template dig that stuff out..  RequestContext initializes the
Context according to the dictionary you pass, but also runs you configured
set of context processors, which can paw through the Request object and add
values to your Context's dictionary(s).  See:
https://docs.djangoproject.com/en/2.1/ref/templates/api/

render() turns your template (and context) into a string representing the
body of the response.  render_to_response() does that and uses it to
initialize an HttpResponse object that contains that, plus all suitable
response headers, some defaulted, like content type and content length,
override-able by you, and any additional headers you choose to add, and
also the response status, 200 by default, and corresponding status string,
which you can override if needed.  You need an HttpResponse object to
return from a view so that Django can build the whole response.

Of course, all this is in the documentation.

On Fri, Aug 10, 2018 at 5:37 PM shivam sharma <
talk2shivamsharma19...@gmail.com> wrote:

> Can someone explain me difference between Context object and
> RequestContext obj.
> And also difference between
> render_to_response() and render()
>
> --
> 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/CAKd5AUUPToxjMeg%2B47ENB3T5KQ%2BXyRVb%2BNKnGLKsGz10OyRFPg%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 
https://groups.google.com/d/msgid/django-users/CAB%2BAj0vxXEOg%3DY7Y-9GCBcVbwfaU9eHdG%3D91emsRi0JWUUqcXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Setting up a system for testing by users (tables are tables?)

2018-08-11 Thread Derek
*The users who should do the testing say "The new system should be like the 
production system."*
You need to let them know ASAP that that is very unlikely to be the case, 
unless you are using exactly the same tools.  You can probably provide 
similar functionality.

Otherwise you are too vague to give better feedback - "copying a system" 
has too many meanings.  If its just the database you need, and you plan to 
write a new front-end from scratch using Django, then that is "do-able" 
(assuming you can extract the data from SAP - that is a problem you will 
need to ask the SAP experts about).  Once you have the database available, 
you can follow this guide:

https://docs.djangoproject.com/en/2.1/howto/legacy-databases/


On Wednesday, 18 July 2018 11:45:00 UTC+2, guettli wrote:
>
> I have a task which looks simple at the first sight:
>
>  Setting up a system for testing by users. 
>
> In my case it is a custom issue tracking system.
>
> The users who should do the testing say "The new system should be like the 
> production system."
>
> If this would be true, then dump+restore of the database should work.
>
> No Nr2: the production system contains a lot of issues, and these should 
> not be in the new system.
>
> No Nr2: The production system contains configuration (in the database) of 
> remote storage systems. These
> database rows must not get copied, otherwise the testing system would 
> transfer testing data
> to the production storage system.
>
> Configuration like the list of ticket types should get copied.
>
> Tables are tables, or is there a difference between tables?
>
> Up to now I only found one hint to this task: In SAP this is called 
> "client copy" and there seem
> to be different "delivery classes" of a table:
>
>
> https://help.sap.com/doc/saphelp_crm70/7.0.0.18/en-US/43/45860774b711d2959700a0c929b3c3/content.htm?no_cache=true
>
> Are there tools/framework which support copying a system? I am curious, if 
> you know a framework outside django, please tell me.
>
> Up to now I could not find a tool or hint about solving this in a reusable 
> way in django. If I was blind, please let me know.
>
> Any kind of feedback is welcome.
>
> Regards,
>   Thomas Gütler
>

-- 
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/8508f0bd-e5f6-4401-9215-682bb39ee5a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: django

2018-08-11 Thread squal poreover
It means manage.py file is not in the same directory .. where you run
python manage.py runserver



On 10 Aug 2018 3:01 am, "Welly Iskand"  wrote:

On Friday, August 10, 2018 at 3:54:54 AM UTC+7, vasu wrote:
>
> while running python manage.py runserver 8080 this in cmd ...i am getting
> cant open file 'manage.py' .But i followed the documentation
> properly.help me with this
>


hi vasu
you can try use command
./manage.py runserver

regards
welly iskand

-- 
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/7a0517aa-d4ec-4905-9f19-abb1ea736762%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/CANQmjduT%2B8_HhQfnWQ6eY26acLdau3X2eNuZyRU_sE-QBedDEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Unexpected behavior with icontains in query filter

2018-08-11 Thread Joel Mathew
This is what I got:

In [8]: doct = doctor.objects.filter(name__icontains = 'joel')
   ...: print(doct.query)

SELECT `appointments_doctor`.`docid`, `appointments_doctor`.`name`,
`appointments_doctor`.`username`, `appointments_doctor`.`regid`,
`appointments_doctor`.`photo`, `appointments_doctor`.`email`,
`appointments_doctor`.`phone`, `appointments_doctor`.`qualifications`,
`appointments_doctor`.`about`, `appointments_doctor`.`specialities`,
`appointments_doctor`.`department`, `appointments_doctor`.`fees`,
`appointments_doctor`.`displayfee`, `appointments_doctor`.`slotrange`,
`appointments_doctor`.`slotdurn`, `appointments_doctor`.`breakrange`,
`appointments_doctor`.`slotsleft` FROM `appointments_doctor` WHERE
`appointments_doctor`.`name` LIKE %joel%


Sincerely yours,

Dr Joel G Mathew



On 11 August 2018 at 11:25, Jason  wrote:
> Are you using sqlite for your db?  if so, there are some notes about case
> insensitive matching at
> https://docs.djangoproject.com/en/dev/ref/databases/#sqlite-string-matching
>
> otherwise, I'd be interested in seeing what your SQL is like
>
> in your django shell, do the following:
>
> doctors = Doctors.objects.filter(name__icontains = 'joel')
> print(doctors.query)
>
> It should have something like
>
> SELECT ... FROM ... WHERE name ILIKE  '%joel%';
>
> which should do the case insensitive search.
>
> Otherwise, this is a database issue, and not a django issue.  Django just
> converts the filter call to the appropriate SQL and has the db execute it.
>
> --
> 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/2b8dd9eb-b1ab-4eaf-ac17-4f03c1ed1c2c%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/CAA%3Diw_8E0NcRCU142f6eRBTSrmuj9nrG2n8DSXV_-PaGAWwqyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Unexpected behavior with icontains in query filter

2018-08-11 Thread Joel Mathew
This workaround works.

In [10]: from django.db.models.functions import Lower
In [11]: from django.db.models import CharField

In [12]: CharField.register_lookup(Lower, "lower")
Out[12]: django.db.models.functions.base.Lower

In [13]: doctor.objects.filter(name__lower__contains="joel")
Out[13]: , ]>

I'm eager to solve this strange behavior though.
Sincerely yours,

Dr Joel G Mathew



On 10 August 2018 at 17:17, Matthew Pava  wrote:
> I’m fascinated by this problem.
>
> Try this workaround.
>
> https://docs.djangoproject.com/en/2.0/ref/models/database-functions/#lower
>
>
>
> Register the lookup Lower like so:
>
> CharField.register_lookup(Lower, "lower")
>
>
>
> Then use the contains lookup.
>
> doctor.objects.filter(name__lower__contains="joel")
>
>
>
>
>
> From: django-users@googlegroups.com [mailto:django-users@googlegroups.com]
> On Behalf Of Joel
> Sent: Friday, August 10, 2018 10:56 AM
> To: Django users
> Subject: Unexpected behavior with icontains in query filter
>
>
>
> I'm trying to do a case insensitive search for a substring within a field in
> my model.
>
>
>
> My model:
>
>
>
>
>
> class doctor(models.Model):
> docid = models.AutoField(primary_key=True, unique=True) # Need
> autoincrement, unique and primary
> name = models.CharField(max_length=35)
> username = models.CharField(max_length=15)
> regid = models.CharField(max_length=15, default="", blank=True)
> photo = models.CharField(
> max_length=35, default="", blank=True)
> email = models.EmailField(default="", blank=True)
> phone = models.CharField(max_length=15)
> qualifications = models.CharField(
> max_length=50, default="", blank=True)
> about = models.CharField(
> max_length=35, default="", blank=True)
> specialities = models.CharField(
> max_length=50, default="", blank=True)
> department = models.CharField(max_length=50, default="ENT",
> blank=True)
> fees = models.FloatField(default=300.0)
> displayfee = models.IntegerField(default=0, blank=True)
> slotrange = models.CharField(max_length=50, blank=True)
> slotdurn = models.IntegerField(default=10)
> breakrange = models.CharField(
> max_length=50, default="", blank=True)
> slotsleft = models.CharField(
> max_length=50, default="", blank=True)
> def __str__(self):
> return self.name
> def Range(self):
> return self.slotrange
> def listslots(self):
> SlotRange = self.slotrange
> SlotDurn = self.slotdurn
> startime = SlotRange.split('-')[0]
> endtime = SlotRange.split('-')[1]
> sthr, stmin = SplitTimeString(startime)
> enhr, enmin = SplitTimeString(endtime)
> print(stamptoday(sthr, stmin))
> print(stamptoday(enhr, enmin))
> startstamp = stamptoday(sthr, stmin)
> endstamp = stamptoday(enhr, enmin)
> secdurn = SlotDurn*60
> slotlist = []
> for sec in range(startstamp, endstamp, secdurn):
> enttime = sec + secdurn
> myrange = ("%s - %s" % (HumanTime(sec),
> HumanTime(enttime)))
> slotlist.append(myrange)
> return slotlist
>
>
>
>
>
> Under the field 'name' in my mysql database, are two rows with values for
> name as 'Joel' and 'Jaffy Joel'.
>
>
>
> When I do the search like this:
>
>
>
>
>
> from appointments.models import customer, doctor, appointment
> doctor.objects.filter(name__icontains='joel')
>
>
>
>
>
> Output:
>
>
>
>
>
> 
>
>
>
>
>
> But when I do:
>
>
>
> doctor.objects.filter(name__icontains='Joel')
>
>
>
> Output:
>
>
>
>
>
>  , ]>
>
>
>
>
>
> Why isnt the case insensitive search working for a lowercase search?
>
>
>
> I'm on django 2.0.7
>
> --
> 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/46579c92-8a12-4977-814c-9c3fcaa14711%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/djan

Re: Unexpected behavior with icontains in query filter

2018-08-11 Thread Jason
Check out https://code.djangoproject.com/ticket/9682.  Apparently this is a 
mysql specific thing.

-- 
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/fb9ad1c0-e955-48f7-8a3b-43c95271f9e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to include delete function in UpdateView instead a DeleteView

2018-08-11 Thread Melvyn Sopacua
On vrijdag 10 augustus 2018 16:51:54 CEST zengkeat wrote:

> I have a UpdateView for editing a post, but instead of making a DeleteView
> for delete a post, i try to make UpdateView include a function to delete
> the post. So ,i want to edit and delete a post in UpdateView. Is that
> possible ? i think i missing something in my code so the code keep getting
> error.

No, you're simply not conforming to the method signature.

> form_valid() missing 1 required positional argument: 'pk'

Your form_valid method wants an argument 'pk':

> def form_valid(self, form, pk):

But Django never will give you one. What you're looking for is 
self.kwargs['pk'] and the method for form_valid can only accept one argument, 
which is the form.

-- 
Melvyn Sopacua


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


How to serve this static file

2018-08-11 Thread Sandy Leon
Hello everyone,

I recently completed the Django first app tutorial and am decently happy 
with what I have.
I would like to continue adding to the site by making small improvements 
here and there. Anyways I found a cool cube clock on freefrontend.com but I 
can't seem
to figure out how to add it to my site. According to freefrontend.com, the 
cube clock uses HTML, CSS, and Java. I have already sorted the elements into
their corresponding locations based off of the tutorial but still can't 
seem to get it to work. This is the download link if that helps at all:

https://freefrontend.com/assets/zip/css-clocks/cube-clock.zip

Thank you in advance for the help.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/b95cab26-6eab-4567-a58a-e1aff0abf2ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.