Minify HTML in Django

2016-10-31 Thread Web Architect
Hi,

Is there an optimal and efficient way to minify HTML in Django?

I tried using django-htmlmin but it's affecting the performance. 

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/f7886579-ff7f-4be2-8f25-c12e3e010899%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Form Saving Related Issues

2016-10-31 Thread pradam programming
Thank you sir for the reply..
But I am using HTML forms then what should I do...?  I want error message
should display instantly when user enter existing mail id..!

On 1 Nov 2016 12:05 am, "Andromeda Yelton" 
wrote:

> If your model has the uniqueness constraint, you should get a form error
> message automatically. If you don't want your model to have that constraint
> but you still want your form to throw an error message, you can add a
> clean_ and a clean_ function
> that check for uniqueness and raise ValidationError if it fails (see
> examples here: https://docs.djangoproject.com/en/1.10/ref/
> forms/validation/ ).
>
> When the form saves successfully, the user will be redirected to the
> success_url you provide. That template can have success message text.
> Alternately, in your form_valid function in the view, you could add a
> success message that will get added to whatever page you're redirecting to
> (as long as you make sure your template is rendering messages) ->
> https://docs.djangoproject.com/en/1.10/ref/contrib/
> messages/#adding-a-message
>
> On Mon, Oct 31, 2016 at 1:55 AM, pradam programming <
> pradam.programm...@gmail.com> wrote:
>
>> Hi,
>> Please I need an advice on the best approach to take on the following
>> issues.
>> I have create a form to save user details like first name,last
>> name,email,mobile number etc...
>>
>> 1.Now I need to show error message (In Models i gave email and mobile no
>> field as unique = True) when user enter a email id if email id exists in
>> database show message like email id exists beside the email text field(also
>> for  the mobile no) else proceed with form.
>> 2.After i saving the form i need to show alert of success.
>>
>> regards,
>> Pradam Abhilash
>>
>> --
>> 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/ms
>> gid/django-users/CAGGVXBOz6kQs%2BHhR%2BsrTUApOGnR7t50HHQuvSN
>> _zJz6VMQosFw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Andromeda Yelton
> Vice President/President-Elect, Library & Information Technology
> Association: http://www.lita.org
> http://andromedayelton.com
> @ThatAndromeda 
>
> --
> 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/CAFE1XCbVpkpOboCKR_Xck-oTm2NJYCVQ6ssWZsBWRaNe3pQM9Q%
> 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/CAGGVXBPwq%2BGaEkfFYRx%3Df3uL3Wzbh1xn5BLKdC7%2BCp_PHapBtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


BaseInlineFormSet with unique_together Model

2016-10-31 Thread Matthew Pava
Good day,
I am new to this list, but I would like to understand better what is going on 
and how I can fix it the Django way.

I have a model similar to the ingredients list of a recipe.
class FoodItem(models.Model):
name = models.CharField()

class Recipe(models.Model):
input = models.ForeignKey(FoodItem, related_name="recipe", ...)
qty = models.FloatField()
ingredient = models.ForeignKey(FoodItem, ...)

class Meta:
unique_together = ('input', 'ingredient')

We don't want the recipe to list the same ingredient twice.
Then I make a basic BaseInlineFormSet.  I use Javascript to add forms and 
delete forms dynamically.  So let's say I first create this data:
Input, Qty, Ingredient
Cookies, 1, Sugar
Cookies, 2, Eggs
Cookies, 4, Flour
Cookies, 1, Chocolate Chips

It's perfect.  Then I go back and try to update the data.  I remove the Flour 
from the recipe.  It gets marked for deletion and hidden from the user.  Then I 
think, "Oh wait!  That was supposed to be 6 of the Flour!"  So I add a new data 
entry form to the formset with this data:
Cookies, 6, Flour

I click on save, and I get a validation error.  That input and ingredient 
already exist.  And it's right.  The form marked for deletion that has 4 Flour 
does not get deleted until the call to formset.save().  But the new form is not 
valid because it violates the unique constraint on the model.  I did develop a 
roundabout way of dealing with the situation: I simply delete all the instances 
from the database for forms that are marked for deletion before calling 
formset.is_valid().  But I keep thinking to myself that there must be something 
I am missing.

Thank you,
Matthew Pava



-- 
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/84f80d96f27b4370bb667740a9b75651%40ISS1.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.


Updating mixin subclassed instances

2016-10-31 Thread Radek Svarz
Hi,

I am using my custom permission mixin on several of my apps's models (not 
all).

For the case when I need to merge from the "old - context" permission to 
the "new - context" permission I want to have function which changes the 
corresponding permission reference attribute in all models, which 
subclassed this mixin.

How do I know which models subclassed this permission mixin and that they 
have the inherited permission reference attribute?

In fact I want to have such function in my mixin:

@classmethod
def merge_to(cls, from_perm_context, to_perm_context):

perm_context_models = []  # How to get this?

try:
with transaction.atomic():
for model in perm_context_models:
model.objects.filter(
perm_context=from_perm_context,
).update(perm_context=to_perm_context)
except IntegrityError as e:  # or DatabaseError
raise e




Thanks, 

Radek

-- 
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/576474f7-dace-4986-b121-0eb2e5428122%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Form Saving Related Issues

2016-10-31 Thread Andromeda Yelton
If your model has the uniqueness constraint, you should get a form error
message automatically. If you don't want your model to have that constraint
but you still want your form to throw an error message, you can add a
clean_ and a clean_ function
that check for uniqueness and raise ValidationError if it fails (see
examples here: https://docs.djangoproject.com/en/1.10/ref/forms/validation/
).

When the form saves successfully, the user will be redirected to the
success_url you provide. That template can have success message text.
Alternately, in your form_valid function in the view, you could add a
success message that will get added to whatever page you're redirecting to
(as long as you make sure your template is rendering messages) ->
https://docs.djangoproject.com/en/1.10/ref/contrib/messages/#adding-a-message

On Mon, Oct 31, 2016 at 1:55 AM, pradam programming <
pradam.programm...@gmail.com> wrote:

> Hi,
> Please I need an advice on the best approach to take on the following
> issues.
> I have create a form to save user details like first name,last
> name,email,mobile number etc...
>
> 1.Now I need to show error message (In Models i gave email and mobile no
> field as unique = True) when user enter a email id if email id exists in
> database show message like email id exists beside the email text field(also
> for  the mobile no) else proceed with form.
> 2.After i saving the form i need to show alert of success.
>
> regards,
> Pradam Abhilash
>
> --
> 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/CAGGVXBOz6kQs%2BHhR%2BsrTUApOGnR7t50HHQuvSN_
> zJz6VMQosFw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andromeda Yelton
Vice President/President-Elect, Library & Information Technology
Association: http://www.lita.org
http://andromedayelton.com
@ThatAndromeda 

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


Re: Redirect after Form

2016-10-31 Thread Moreplavec
Many thanks, works fine and looks much better to me.

Dne pondělí 31. října 2016 10:21:37 UTC+1 Michal Petrucha napsal(a):
>
> On Sun, Oct 30, 2016 at 06:39:19AM -0700, Moreplavec wrote: 
> > I found in Django Tutorial solution: 
> > https://docs.djangoproject.com/en/1.10/intro/tutorial04/ : 
> > 
> > Now i have: 
> > 
> > return HttpResponseRedirect(reverse('crm:company_detail', args=(
> company.pk,))) 
> > #return redirect('views.company_detail', pk=company.pk) 
> > 
> > 
> > And it works fine! 
>
> Just for the record, you should also be able to use this:: 
>
> return redirect('crm:company_detail', company.pk) 
>
> (That should be equivalent to the explicit HttpResponseRedirect with 
> reverse().) 
>
> Cheers, 
>
> Michal 
>

-- 
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/914fbb8f-9568-4f06-8e7d-6a6d7ade3da5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Using django pagination or slicing

2016-10-31 Thread ADEWALE ADISA
Thanks fedowag.
On Oct 31, 2016 12:01 PM, "王安刚"  wrote:

> hi
> i prefer method 2
>
> you can get all the list from db and store it in redis using zadd
> each time an ajax request comes, you get the data you need using zrange
>
>
> 在 2016年10月31日星期一 UTC+8上午9:05:07,ADEWALE ADISA写道:
>>
>> Hello,
>> Please I need an advice on the best approach to take on the following
>> issues.
>> I have a database table consist of about 1000 record. I need to be
>> displaying like 20 records at a time on a page such that when the user
>> scroll the browser another batches will be append to the browser.
>> Below are the 3 ways am aiming to achieve this:
>>
>> 1. Using django pagination feature.
>>
>> 2. Everytime records need to be appended to the browser , an ajax call is
>> made to the view, then the queryset is slice using appropriate lower and
>> upper band. Then the returned record is appended to the browser.
>>
>> 3. Fetch the whole records from the database and transfer everything to
>> the browser, then JavaScript is now use to slice and be appending as needed.
>>
>> NOTE: The webpage would work like yahoo.com mobile site.
>> Please with approach is the best in term of performance and speed.
>>
>> 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/022fd700-0edb-419c-9a0d-6e9714229599%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/CAMGzuy-s8X495UAXuQTibAXe9VLumhMvSUEhzo_rb55T4%3DsQ7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Using django pagination or slicing

2016-10-31 Thread ADEWALE ADISA
Thanks very much Ludovic for the advice.
On Oct 31, 2016 9:53 AM, "ludovic coues"  wrote:

> I would use 1 + 2 from your list.
>
> 3 might work on 1000 record, depending on how much data there is per
> record. But if you grow to more than 10,000 record, the page loading
> can take minutes. I have experienced that issue with two different
> project.
>
> Django pagination by itself won't give you the infinite scroll you are
> expecting. But it should give you an easy interface for slicing the
> data from your db.
>
> An easier way might be class based view. The following exemple create
> a view to a list of object, paginated:
>
> from django.http import JsonResponse
> from django.views.generic import ListView
>
> class ModelListView(ListView):
> model = RecordModel
> paginate_by = 20
>
> It will try to use the template at app/record_model_list.html, the
> context will have the keys paginator, page, is_paginated, object_list.
> You can override the method render_to_response to return a json
> response.
> The documentation on ListView is at [1] and there is an exemple for
> returning JsonResponse at [2]
>
>
> [1] https://docs.djangoproject.com/en/1.10/topics/class-
> based-views/generic-display/
> [2] https://docs.djangoproject.com/en/1.10/topics/class-
> based-views/mixins/#more-than-just-html
>
>
>
>
> 2016-10-31 2:04 GMT+01:00 ADEWALE ADISA :
> > Hello,
> > Please I need an advice on the best approach to take on the following
> > issues.
> > I have a database table consist of about 1000 record. I need to be
> > displaying like 20 records at a time on a page such that when the user
> > scroll the browser another batches will be append to the browser.
> > Below are the 3 ways am aiming to achieve this:
> >
> > 1. Using django pagination feature.
> >
> > 2. Everytime records need to be appended to the browser , an ajax call is
> > made to the view, then the queryset is slice using appropriate lower and
> > upper band. Then the returned record is appended to the browser.
> >
> > 3. Fetch the whole records from the database and transfer everything to
> the
> > browser, then JavaScript is now use to slice and be appending as needed.
> >
> > NOTE: The webpage would work like yahoo.com mobile site.
> > Please with approach is the best in term of performance and speed.
> >
> > 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/CAMGzuy8cK7ueHGPwuCjbrV-
> SdfZwkYYhg7_t7-Dmmt%3D6g787YA%40mail.gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
>
> Cordialement, Coues Ludovic
> +336 148 743 42
>
> --
> 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/CAEuG%2BTaPWphYQAwa9-rPW5VZ93yyA3kL%
> 3Dz8JAecdLRMiKdjihA%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/CAMGzuy_Tu7mdL4RTvNGWY%3Dm5PL0ttT4wv9QKeMfiLqd43MiaVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: question about returning file (pdf,image,zip...) in a request that made from temporary URL

2016-10-31 Thread Stefano Probst
You could use a whole deployment setup. Forward Django though nginx by 
using WSGI (Gnuicorn, etc). Then everything should work.

-- 
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/5df18a18-7656-4741-bb8a-948db39b8bcd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Using django pagination or slicing

2016-10-31 Thread 王安刚
hi 
i prefer method 2

you can get all the list from db and store it in redis using zadd
each time an ajax request comes, you get the data you need using zrange


在 2016年10月31日星期一 UTC+8上午9:05:07,ADEWALE ADISA写道:
>
> Hello,
> Please I need an advice on the best approach to take on the following 
> issues.
> I have a database table consist of about 1000 record. I need to be 
> displaying like 20 records at a time on a page such that when the user 
> scroll the browser another batches will be append to the browser. 
> Below are the 3 ways am aiming to achieve this:
>
> 1. Using django pagination feature.
>
> 2. Everytime records need to be appended to the browser , an ajax call is 
> made to the view, then the queryset is slice using appropriate lower and 
> upper band. Then the returned record is appended to the browser.
>
> 3. Fetch the whole records from the database and transfer everything to 
> the browser, then JavaScript is now use to slice and be appending as needed.
>
> NOTE: The webpage would work like yahoo.com mobile site.
> Please with approach is the best in term of performance and speed.
>
> 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/022fd700-0edb-419c-9a0d-6e9714229599%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Form Saving Related Issues

2016-10-31 Thread pradam programming
Hi,
Please I need an advice on the best approach to take on the following
issues.
I have create a form to save user details like first name,last
name,email,mobile number etc...

1.Now I need to show error message (In Models i gave email and mobile no
field as unique = True) when user enter a email id if email id exists in
database show message like email id exists beside the email text field(also
for  the mobile no) else proceed with form.
2.After i saving the form i need to show alert of success.

regards,
Pradam Abhilash

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


Re: Redirect after Form

2016-10-31 Thread Michal Petrucha
On Sun, Oct 30, 2016 at 06:39:19AM -0700, Moreplavec wrote:
> I found in Django Tutorial solution: 
> https://docs.djangoproject.com/en/1.10/intro/tutorial04/ :
> 
> Now i have: 
> 
> return HttpResponseRedirect(reverse('crm:company_detail', args=(company.pk,)))
> #return redirect('views.company_detail', pk=company.pk)
> 
> 
> And it works fine!

Just for the record, you should also be able to use this::

return redirect('crm:company_detail', company.pk)

(That should be equivalent to the explicit HttpResponseRedirect with
reverse().)

Cheers,

Michal

-- 
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/20161031092105.GJ8307%40konk.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature


Re: Using django pagination or slicing

2016-10-31 Thread ludovic coues
I would use 1 + 2 from your list.

3 might work on 1000 record, depending on how much data there is per
record. But if you grow to more than 10,000 record, the page loading
can take minutes. I have experienced that issue with two different
project.

Django pagination by itself won't give you the infinite scroll you are
expecting. But it should give you an easy interface for slicing the
data from your db.

An easier way might be class based view. The following exemple create
a view to a list of object, paginated:

from django.http import JsonResponse
from django.views.generic import ListView

class ModelListView(ListView):
model = RecordModel
paginate_by = 20

It will try to use the template at app/record_model_list.html, the
context will have the keys paginator, page, is_paginated, object_list.
You can override the method render_to_response to return a json
response.
The documentation on ListView is at [1] and there is an exemple for
returning JsonResponse at [2]


[1] 
https://docs.djangoproject.com/en/1.10/topics/class-based-views/generic-display/
[2] 
https://docs.djangoproject.com/en/1.10/topics/class-based-views/mixins/#more-than-just-html




2016-10-31 2:04 GMT+01:00 ADEWALE ADISA :
> Hello,
> Please I need an advice on the best approach to take on the following
> issues.
> I have a database table consist of about 1000 record. I need to be
> displaying like 20 records at a time on a page such that when the user
> scroll the browser another batches will be append to the browser.
> Below are the 3 ways am aiming to achieve this:
>
> 1. Using django pagination feature.
>
> 2. Everytime records need to be appended to the browser , an ajax call is
> made to the view, then the queryset is slice using appropriate lower and
> upper band. Then the returned record is appended to the browser.
>
> 3. Fetch the whole records from the database and transfer everything to the
> browser, then JavaScript is now use to slice and be appending as needed.
>
> NOTE: The webpage would work like yahoo.com mobile site.
> Please with approach is the best in term of performance and speed.
>
> 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/CAMGzuy8cK7ueHGPwuCjbrV-SdfZwkYYhg7_t7-Dmmt%3D6g787YA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 

Cordialement, Coues Ludovic
+336 148 743 42

-- 
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/CAEuG%2BTaPWphYQAwa9-rPW5VZ93yyA3kL%3Dz8JAecdLRMiKdjihA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.