Re: How to pass data between Django module/app functions without using database in asynchronous web service

[Ken McDonald]

On Thursday, December 29, 2016 at 6:00:03 AM UTC-5, Andrew Godwin wrote:
>
> *Q) Are the websocket and the AJAX calls going to different clients/pages 
> entirely, rather than them both being in the same page context? It sounds 
> like the websocket is going to a server somewhere that's allocating 
> resources and not going to a webpage/browser at all.*
>
> A) Currently the websockets are used in a background system running on 
Django and most of the use for websockets on this service are so the remote 
system we are interfacing with can pull a list of subscribers from a Django 
model and then the remote system does uncoordinated stuff with that. 
Occasionally, the remote system updates data to Django models for debugging 
information or sending statistics back.

In the normal course of the application, the web server web page interface 
is between user and Django model and has no need for a direct connection to 
the remote system through websockets; they are just setting up subscription 
types as a seller or buying subscriptions as a buyer. Later, when they are 
using the remote system, which happens with a completely different client 
native compiled application, not Django or web interface, they make use of 
the real purpose of our system which is enhanced by the subscriptions we 
sell. Basically, we
are using the Django web service to sell subscriptions which are then 
periodically download through websockets to a remote native compiled 
application.
 

*On Thursday, December 29, 2016 at 6:00:03 AM UTC-5, Andrew Godwin wrote:*

> *Q) - Could it potentially take the websocket client that is sending the 
> LOBBY data back that needs to then be conveyed over AJAX some time to 
> reply? Say, more than ten seconds?*
>
> A) The return replies are just about instantaneous and very small in size. 
Although ultimately the system will interface with potentially 1000's of 
distinct remote systems, the Django web service is only used for a very, 
very short period of time by a user, and then maybe never again if they 
just continue to renew their subscription. The users are at the remote 
systems. We just sell stuff that makes that experience better. The need for 
displaying return data as envisioned in my original question is a rare 
occurannce almost exclusively used by sellers and more so, just by 
administrators of the system.
 

*On Thursday, December 29, 2016 at 6:00:03 AM UTC-5, Andrew Godwin wrote:*

> *Q) I think I have an idea of what you're trying to do here and how to 
> solve it, but I just need to be a bit more clear on the architecture first.*
>

A) My primary purpose for the django-channels to remote system is working 
great. I can download from a model and upload to a model through websockets 
(just for reference: the interface at the remote system is a C++ compiled 
application (w/ websockets) connected to a C# final product). 

There are various need, by this example can best describe a single feature:

1) We have a debugging system on the remote system that will upload 
transactions from there to our Django model through websockets.
2) In that debugging system, we can set various levels of verbosity to 
control how much detail is returned.
3) I have a working Django web page now that can send commands that change 
the debugging level through a websocket-routed command in a JSON message 
with a particular debugging level (like 1-7). This web page uses a Django 
template with a radio button form for the 1-7 choices.
4) When a choice is changed on the form, Javascript catches it and calls a 
Django function that send the websocket command to the remote system to 
change the debugging (we track websocket instances of channel names in a 
database, so I can always contact a particular remote system by knowing our 
own internally-assign db id to lookup the Django channel name for that 
websocket connection).

In the above example, what I am looking for is that when the web page is 
initially rendered (url'd in browser), fetch the current debugging level 
from the remote system and pre-set the radio buttons. Right now of course, 
the page just renders with a default layout of the radio button without 
reference to what the current debugging level actually is at the remote 
site.

In addition to the websocket JSON command to tell the remote system to set 
a particular debugging level, I also have a command that requests the 
current debugging level. It's connecting the reply back data from that 
request command to the webpage when it's initially rendered that is proving 
difficult to understand.

Thanks for any help you or anyone can provide. I'm dealing with a lot of 
technologies and a lot of languages that I'm not totally expert or 
experienced with, but I will complete this project in one form or another. 
My system engineering background leads me to want a design that is more 
push and event-driven, than pull and polling. I can find a solution that is 
pull and polling (store in table, Javascript 

Re: User model not using persistent DB connection?

[Bobby Mozumder]

I’m actually already setting CONN_MAX_AGE to None on a connection pool.  The 
rest of the queries in the view are using the persistent connection pools.

It’s only this specific request.user object that keeps creating a new 
connection instead of using the persistent connection for some reason.

-bobby

> On Dec 29, 2016, at 4:16 PM, James Bennett  wrote:
> 
> See the documentation for details:
> 
> https://docs.djangoproject.com/en/1.10/ref/settings/#conn-max-age 
> 
> 
> Also, generally speaking maintaining a connection pool has been seen as out 
> of scope for Django itself, and most people use a standalone connection 
> pooler (such as pgpool for Postgres).
> 
> On Thu, Dec 29, 2016 at 1:13 PM, Bobby Mozumder  > wrote:
> Hi,
> 
> It seems Django doesn’t use a persistent DB connection whenever I use the 
> Request.User object.
> 
> I always get a signal saying a new DB connection occurs when I call the 
> object.
> 
> For example:
> 
> class MyView(DetailView):
> def get(self, request, slug):
> print(request.user) # <--- Boom, new database connection signal is 
> sent here.
> # continue processing view
>   pass
> 
> Is that by design?  Or is it an error?  
> 
> I’d like it to use the same persistent DB connection across all requests. 
> 
> I’m looking through the Django source (auth & sessions backend) and can’t 
> find where the DB connection is happening.  I haven’t touched the User models 
> at all, although I do have a DB connection receiver that runs prepared 
> statements when the app starts - it’s where I found this. 
> 
> Any info on this is appreciated, & happy Holidays!
> 
> -bobby
> 
> -- 
> 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/A56E8EB4-EE0A-477F-B8DD-F39AA43F71EB%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/CAL13Cg8FmJRC%2Br9VoKoa3R4o_wURMc6kJGQGUB_WG5NJgcZEQg%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/5CB94F19-DA9A-4898-856F-DEEABA725CF4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: User model not using persistent DB connection?

[James Bennett]

See the documentation for details:

https://docs.djangoproject.com/en/1.10/ref/settings/#conn-max-age

Also, generally speaking maintaining a connection pool has been seen as out
of scope for Django itself, and most people use a standalone connection
pooler (such as pgpool for Postgres).

On Thu, Dec 29, 2016 at 1:13 PM, Bobby Mozumder  wrote:

> Hi,
>
> It seems Django doesn’t use a persistent DB connection whenever I use the
> Request.User object.
>
> I always get a signal saying a new DB connection occurs when I call the
> object.
>
> For example:
>
> class MyView(DetailView):
> def get(self, request, slug):
> print(request.user) # <--- Boom, new database connection signal
> is sent here.
> # continue processing view
> pass
>
> Is that by design?  Or is it an error?
>
> I’d like it to use the same persistent DB connection across all requests.
>
> I’m looking through the Django source (auth & sessions backend) and can’t
> find where the DB connection is happening.  I haven’t touched the User
> models at all, although I do have a DB connection receiver that runs
> prepared statements when the app starts - it’s where I found this.
>
> Any info on this is appreciated, & happy Holidays!
>
> -bobby
>
> --
> 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/A56E8EB4-EE0A-477F-B8DD-F39AA43F71EB%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/CAL13Cg8FmJRC%2Br9VoKoa3R4o_wURMc6kJGQGUB_WG5NJgcZEQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

User model not using persistent DB connection?

[Bobby Mozumder]

Hi,

It seems Django doesn’t use a persistent DB connection whenever I use the 
Request.User object.

I always get a signal saying a new DB connection occurs when I call the object.

For example:

class MyView(DetailView):
def get(self, request, slug):
print(request.user) # <--- Boom, new database connection signal is sent 
here.
# continue processing view
pass

Is that by design?  Or is it an error?  

I’d like it to use the same persistent DB connection across all requests. 

I’m looking through the Django source (auth & sessions backend) and can’t find 
where the DB connection is happening.  I haven’t touched the User models at 
all, although I do have a DB connection receiver that runs prepared statements 
when the app starts - it’s where I found this.  

Any info on this is appreciated, & happy Holidays!

-bobby

-- 
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/A56E8EB4-EE0A-477F-B8DD-F39AA43F71EB%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: existing database connectivity

[ludovic coues]

Have you done a tutorial on django ?

Part 4 of the official tutorial deal with altering an object from your
database according to a form.
https://docs.djangoproject.com/en/1.10/intro/tutorial04/

The django girls tutorial have a section on how to create an object
from a form and save it in your database.
https://tutorial.djangogirls.org/en/django_forms/

2016-12-27 7:10 GMT+01:00 Rasika :
> I know how to save a record from shell command in command prompt.
> I want to get values from html form and save it to database table which I
> have created.Please help on this I am not getting proper answer or code on
> net.
>
>
> On Monday, December 26, 2016 at 9:54:25 AM UTC+5:30, Rasika wrote:
>>
>> yes it worked well.
>> Thank you so much
>>
>> On Saturday, December 24, 2016 at 9:46:04 AM UTC+5:30, Collin Anderson
>> wrote:
>>>
>>> Hi,
>>>
>>> You could try re-installing psycopg2 to see if that fixes it.
>>>
>>> Collin
>>>
>>> On Thursday, December 22, 2016 at 1:55:53 AM UTC-6, Rasika wrote:


 I am followed the steps as I am getting in tutorials
 when I run the command :
 python manage.py migrate
 this is giving me following error

 from psycopg2._psycopg import BINARY, NUMBER, STRING, DATETIME,
 ROWID
 ImportError: DLL load failed: The specified module could not be found.

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "manage.py", line 22, in 
 execute_from_command_line(sys.argv)
 On Monday, December 19, 2016 at 7:50:19 PM UTC+5:30, Derek wrote:
>
> Suggest you look at Django authentication:
>
> https://docs.djangoproject.com/en/1.10/topics/auth/customizing/
> "Authentication backends provide an extensible system for when a
> username and password stored with the user model need to be authenticated
> against a different service than Django’s default."
>
> It also seems as if your Django project was not set up properly (again
> from the docs):
>
> "By default, the required configuration is already included in the
> settings.py generated by django-admin startproject, these consist of two
> items listed in your INSTALLED_APPS setting:
> 1. 'django.contrib.auth' contains the core of the authentication
> framework, and its default models.
> 2.  'django.contrib.contenttypes' is the Django content type system,
> which allows permissions to be associated with models you create"
>
>
> On Monday, 19 December 2016 13:34:39 UTC+2, Rasika wrote:
>>
>> Hello all,
>>  I am using Django framework for our website.I am stuck on the
>> database connectivity.I want to change the default database sqlite with 
>> our
>> for test purpose but in that also I am getting problems.
>>  My aim is I have to use our compnies database so that already
>> registered users have not to create their account again
>> AsDjango already comes with its own builtin apps for login,logout
>> authentication and registration .Also I am not able to find the
>> 'django.contrib.auth',
>> 'django.contrib.contenttypes',
>> 'django.contrib.sessions',
>> 'django.contrib.sites',
>> 'django.contrib.admin',
>> etc and all default apps also.
>> Please help me.
>>
>> Thank you.
>
> --
> 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/ba843bf7-2a27-4e3a-b2b1-83530f68658c%40googlegroups.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%2BTbBr9bqR17PF_CEhtYMa47ypLQW6hiFnbcZZOiBDbARqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: File/Folder Sync API?

[Alexander Joseph]

Thanks for the awesome resources! Yes, those are what I'm looking for. It
would be nice to have something more secure than dropbox though. Something
like Tresorit or Sync.com would be ideal, not sure if anything like that
exists for django dev or if those have APIs though. Thanks again

On Thu, Dec 29, 2016 at 1:17 AM, Luis Zárate  wrote:

> Are you looking for something like webdav
>
> https://github.com/meteozond/djangodav
> http://django-webdav-storage.readthedocs.io/en/latest/
>
> or something like dinamic dropbox storage
>
> https://github.com/andres-torres-marroquin/django-dropbox
>
>
> 2016-12-28 12:15 GMT-06:00 Alexander Joseph 
> :
>
>> I'm building a collection of apps that write custom .docx and .xlsx
>> files, and store them to a users account. These files need to be in a
>> specific hierarchy and each user will have their own files/folders they can
>> view and edit. It would really be great if I could allow each user to sync
>> their files/folders to their local hard drives so they can view, print,
>> etc. them outside of the web app. Does anyone know of a good API for doing
>> this? I know SugarSync has an API but they charge their users something
>> like $7/mo for their cheapest subscription. I'd like to make my apps free
>> if at all possible. 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/ms
>> gid/django-users/57b50b62-6bce-4197-8414-2afd5be7943b%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> "La utopía sirve para caminar" Fernando Birri
>
>
> --
> 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/WIUhKVPnnbQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAG%2B5VyP-F47D7wXOy2uR4H9ctgBJaa3tMMi2mS
> FF1z9XwbCeSQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Best Regards,

Alexander Joseph

The contents of this email message and any attachments are intended solely
for the addressee(s) and may contain confidential and/or privileged
information and may be legally protected from disclosure. If you are not
the intended recipient of this message or their agent, or if this message
has been addressed to you in error, please immediately alert the sender by
reply email and then delete this message and any attachments. If you are
not the intended recipient, you are hereby notified that any use,
dissemination, copying, or storage of this message or its attachments is
strictly prohibited

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

RE: Just added Python, Django and MySQL integration template for easier data visualization with AnyChart JS

[Matthew Pava]

I took a quick glance, and they are advertising Django integration to show an 
example of how to retrieve the data from the database through Django ORM to be 
used in the HTML template that is rendered by Django and includes the script 
tag with the AnyCharts.js file.

We are currently using two different charting JS plugins in our project, but we 
ought to simplify that so that we only have to support and learn one API.  
Perhaps AnyCharts would be of some consideration for our project.

From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On 
Behalf Of Avraham Serour
Sent: Thursday, December 29, 2016 7:30 AM
To: django-users
Subject: Re: Just added Python, Django and MySQL integration template for 
easier data visualization with AnyChart JS

I have no idea what anychartjs does, in any case I don't understand why a js 
lib would need django integration.

Also it seems they have no idea what they are doing, the guthub repo linked has 
.pyc files commited, anyone needing to use don't copy paste code from there and 
take it with a kilo of salt.

On Thu, Dec 29, 2016 at 12:21 PM, 
> wrote:
Hi all,

We at AnyChart JS Charts have just released a series 
of 20+ integration templates to help web developers add interactive charts, 
maps and dashboards to web apps much easier, no matter what your technology 
stack is.

In particular, now there is a template for using our JavaScript charting 
libraries with Python, Django and 
MySQL in 
our collection, distributed under the Apache 2.0 License and forkable on 
GitHub. (All technical integrations, just in case: 
http://www.anychart.com/integrations/.)

Check that out, and ask your questions if any. 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/aec8bb48-2ceb-4dcb-9486-d66b5b989bd3%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/CAFWa6tJpbLZQjYoeGYRz_TQ4wpp0dxNHuw_t1Z%2BCEPK_8_5o5g%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/1ea813201afb46e48f0dbfb4b194ade1%40ISS1.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.

Re: Django-Channels strange slowdowns - how to profile?

[jakub . skalecki]

I've prepared this simple script to measure roundtrip time (redis on remote 
host):

def check_time(path):   

t = time.time() 

channel_layer.send(u"http.request", {"reply_channel": 
u"http.response.test", "path": path, "method": "GET", "headers": {'host': 
'localhost'}})
response = channel_layer.receive_many([u'http.response.test']) 

print str(time.time() - t) + '   ' +  str(len(response[1]['content']) 
if response and response[1] else '')

Results are:
>> check_time('/health')  # really simple http endpoint
0.140397071838
>>> check_time('/health')
0.132459163666   27
>>> check_time('/health')
0.158210992813   27
>>> check_time('/health')
0.132560014725   27
>>> check_time('/health')
0.133027076721   27
>>> check_time('/health')
0.141057014465   27
>>> check_time('/health')
0.141141891479   27

But, when I'm making request to '/' endpoint, it takes more time (probably 
data transfer)

>>> check_time('/')
0.191249132156   21797
>>> check_time('/')
0.192593812943   21797
>>> check_time('/')
0.18672990799   21797
>>> check_time('/')
0.186357021332   21797
>>> check_time('/')
0.177523851395   21797
>>> check_time('/')
0.190500974655   21797
>>> check_time('/')
0.193222045898   21797

I know that received message is acually response to previous check_time 
call, but it shouldn't matter. Looks like redis request takes a lot of 
time. For example, same requests done to local redis instance:

>>> check_time('/')
0.000913858413696   21755
>>> check_time('/')
0.000931024551392   21755
>>> check_time('/')
0.000808000564575   21755
>>> check_time('/')
0.00170421600342   21755
>>> check_time('/')
0.00079607963562   21755
>>> check_time('/')
0.000899076461792   21755

So, I think that best what can be done is to move all docker containers to 
the same datacenter, because latency seems to be a problem... Do you agree 
with me?

W dniu czwartek, 29 grudnia 2016 13:51:34 UTC+1 użytkownik 
jakub.s...@pvpc.eu napisał:
>
> Thank you for your response. I'll do what you suggested regarding basic 
> consumer, and post my results here.
>
> Sadly, Docker Swarm and distributed hosts are much harder to debug than 
> "standard" deployment. Currently, full way of request is like this:
>
> External load balancer (5 hosts) -> Docker Swarm overlay network routing 
> to nginx -> nginx routing to one of Daphne servers (again using docker 
> overlay network) -> Daphne puts new http request to redis queue for 
> processing -> worker takes request, prepares response, and sends it back to 
> redis -> Daphne takes response and sends it to nginx -> nginx returns it to 
> user. 
>
> Each of this steps introduces some latency. Also response size is close to 
> 23000 bytes. Time spent inside django view is about 0.02-0.03s. Not all 
> hosts are inside the same datacenter. 
>
> I've prepared this setup because of high spikes of traffic on weekends, 
> where users generate about 80-100 rps. My last load tests showed that we 
> can handle right now ~200, but sometimes (quite rarely) something goes bad 
> and there is a major slowdown. It may be Docker fault, yesterday I found 
> out that only one of our Daphne servers was used, others were idle. Now 
> it's fixed. Previously I also tried gunicorn alongside ws workers, but 
> quite suprising, it was slower than http workers. 
>
> Andrew, I'll try to do what you suggested and post my results here. Also, 
> maybe you have some data what is a good proportion of workers / daphne 
> servers? ws workers / http workers? Some general advices about tuning up 
> redis / daphne / workers? Each of them can use one CPU core, it's my swarm 
> settings. Yesterday I checked that one interface server can handle up to 
> 150 simultaneous connections, some of them idle (I know that's only my 
> case), bigger values caused slowdowns. Not that much, but maybe it's my 
> fault. 
>
> Ouch, and If you would like to check our site, it's https://beta.pvpc.eu
>
> W dniu czwartek, 29 grudnia 2016 11:53:12 UTC+1 użytkownik Andrew Godwin 
> napisał:
>>
>> Hi Jakub,
>>
>> There's no full profiling path yet - this is something I hope to work on 
>> as we start integrating ASGI code at work early next year.
>>
>> 400ms for a request is already very long; I'm slightly concerned by that 
>> (unless that's normal without Channels installed as well).
>>
>> If you want to do a basic profiling test, you can just write a very basic 
>> consumer that sends something onto the reply channel and then:
>>
>> 1) Directly inject requests into the channel layer from a python script, 
>> listen for the response, and time the roundtrip. You can import 
>> `channel_layer` from your project's `asgi.py` - if you don't have one the 
>> docs talk about how to make one. You'll want to call 
>> channel_layer.send("http.request", {"reply_channel": 

Re: Just added Python, Django and MySQL integration template for easier data visualization with AnyChart JS

[Avraham Serour]

I have no idea what anychartjs does, in any case I don't understand why a
js lib would need django integration.

Also it seems they have no idea what they are doing, the guthub repo linked
has .pyc files commited, anyone needing to use don't copy paste code from
there and take it with a kilo of salt.

On Thu, Dec 29, 2016 at 12:21 PM,  wrote:

> Hi all,
>
> We at AnyChart JS Charts  have just released a
> series of 20+ integration templates to help web developers add interactive
> charts, maps and dashboards to web apps much easier, no matter what your
> technology stack is.
>
> In particular, now there is a template for using our JavaScript charting
> libraries with Python, Django and MySQL
> 
> in our collection, distributed under the Apache 2.0 License and forkable on
> GitHub. (All technical integrations, just in case:
> http://www.anychart.com/integrations/.)
>
> Check that out, and ask your questions if any. 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/aec8bb48-2ceb-4dcb-9486-d66b5b989bd3%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/CAFWa6tJpbLZQjYoeGYRz_TQ4wpp0dxNHuw_t1Z%2BCEPK_8_5o5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django-Channels strange slowdowns - how to profile?

[jakub . skalecki]

Thank you for your response. I'll do what you suggested regarding basic 
consumer, and post my results here.

Sadly, Docker Swarm and distributed hosts are much harder to debug than 
"standard" deployment. Currently, full way of request is like this:

External load balancer (5 hosts) -> Docker Swarm overlay network routing to 
nginx -> nginx routing to one of Daphne servers (again using docker overlay 
network) -> Daphne puts new http request to redis queue for processing -> 
worker takes request, prepares response, and sends it back to redis -> 
Daphne takes response and sends it to nginx -> nginx returns it to user. 

Each of this steps introduces some latency. Also response size is close to 
23000 bytes. Time spent inside django view is about 0.02-0.03s. Not all 
hosts are inside the same datacenter. 

I've prepared this setup because of high spikes of traffic on weekends, 
where users generate about 80-100 rps. My last load tests showed that we 
can handle right now ~200, but sometimes (quite rarely) something goes bad 
and there is a major slowdown. It may be Docker fault, yesterday I found 
out that only one of our Daphne servers was used, others were idle. Now 
it's fixed. Previously I also tried gunicorn alongside ws workers, but 
quite suprising, it was slower than http workers. 

Andrew, I'll try to do what you suggested and post my results here. Also, 
maybe you have some data what is a good proportion of workers / daphne 
servers? ws workers / http workers? Some general advices about tuning up 
redis / daphne / workers? Each of them can use one CPU core, it's my swarm 
settings. Yesterday I checked that one interface server can handle up to 
150 simultaneous connections, some of them idle (I know that's only my 
case), bigger values caused slowdowns. Not that much, but maybe it's my 
fault. 

Ouch, and If you would like to check our site, it's https://beta.pvpc.eu

W dniu czwartek, 29 grudnia 2016 11:53:12 UTC+1 użytkownik Andrew Godwin 
napisał:
>
> Hi Jakub,
>
> There's no full profiling path yet - this is something I hope to work on 
> as we start integrating ASGI code at work early next year.
>
> 400ms for a request is already very long; I'm slightly concerned by that 
> (unless that's normal without Channels installed as well).
>
> If you want to do a basic profiling test, you can just write a very basic 
> consumer that sends something onto the reply channel and then:
>
> 1) Directly inject requests into the channel layer from a python script, 
> listen for the response, and time the roundtrip. You can import 
> `channel_layer` from your project's `asgi.py` - if you don't have one the 
> docs talk about how to make one. You'll want to call 
> channel_layer.send("http.request", {"reply_channel": "http.response!test", 
> "path": }) and channel_layer.receive_many(["http.response!test"]).
>
> 2) Directly make HTTP requests on the server running Daphne to it via 
> localhost with a similar round trip measurement. Something like `ab` works 
> well for this; remember to either target a very simple view or compare it 
> with a similar test using a WSGI server.
>
> Andrew
>
> On Wed, Dec 28, 2016 at 7:31 PM,  wrote:
>
>> My question from StackOverflow:
>>
>>
>> My technology stack is Redis as a channels backend, Postgresql as a 
>> database, Daphne as an ASGI server, Nginx in front of a whole application. 
>> Everything is deployed using Docker Swarm, with only Redis and Database 
>> outside. I have about 20 virtual hosts, with 20 interface servers, 40 http 
>> workers and 20 websocket workers. Load balancing is done using Ingress 
>> overlay Docker network. Ouch, and I'm also using django-cacheops for low 
>> timeout caching (up to 15 min)
>>
>>
>> The problem is, sometimes very weird things happen regarding performance. 
>> Most of requests are handled in under 400ms, but sometimes request can take 
>> up to 2-3s, even during very small load. Profiling workers with Django 
>> Debug Toolbar or middleware-based profilers shows nothing (timing 50-100ms 
>> or so)
>>
>>
>> My question: is there any good method of profiling a whole request path 
>> with django-channels? I would like how much time each phase takes, i.e when 
>> request was processed by Daphne, when worker started processing, when it 
>> finished, when interface server sent response to the client. Currently, I 
>> have no idea how to solve this.
>>
>>
>> EDIT:
>>
>> Some more information:
>>
>> Website isn't that big, it tops at 1k users online, with some real-time 
>> features like notifications, chat, and real-time updates of few views. It 
>> looks like sometimes website is "blocked", like communication between redis 
>> / interface servers / workers were incredibly slooow. 
>>
>>
>> Maybe you have some experience about server / worker ratios, fine tuning 
>> channel and redis settings? 
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> 

Static CSS file for custom widget

[Antonis Christofides]

Hello everyone,

can a custom widget specify a static CSS file? I think the 

Re: How do I translate site.name to other languages?

[Uri Even-Chen]

Hi,

with django-modeltranslation you can add translations to any model, even if
it's built-in in Django, but the problem is that migrations are being
created in site-packages, outside our git repo, and this would cause issues
upgrading Django itself.

(speedy_net)net$ ./manage.py makemigrations
Migrations for 'sites':

/Users/xtr/.virtualenvs/speedy_net/lib/python3.5/site-packages/django/contrib/sites/migrations/0003_auto_20161229_1018.py:
- Change managers on site
- Add field name_en to site
- Add field name_he to site

Is there a way to move the migrations to inside our git repo?

Thanks,
Uri.


*Uri Even-Chen*
[image: photo] Phone: +972-54-3995700
Email: u...@speedy.net
Website: http://www.speedysoftware.com/uri/en/
  
    


On Mon, Dec 26, 2016 at 1:00 AM, Melvyn Sopacua 
wrote:

> Hi Uri,
>
>
>
> On Thursday 22 December 2016 19:40:15 Uri Even-Chen wrote:
>
>
>
> > We have our site.name and other site names (we have 4 sites in Django
>
> > right now) in templates such as base.html. The site is taken from
>
> > model Site (```from django.contrib.sites.models import Site```).
>
>
>
> Untested, but since Site is a Django Model, have a look at Django Model
> Translation
> .
> I suspect once you get the idea, you'll use it throughout the project.
>
> --
>
> 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/1672133.RzSWr4WvZz%40devstation
> 
> .
> 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/CAMQ2MsH6ZqiK7voGAWhuQedzZPcLV7KX_Ri%3DJxwFmBhGZfosWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: django.template.exceptions.TemplateSyntaxError: 'static' is not a registered tag library. Must be one of:

[jorrit787]

Have you added *django.contrib.staticfiles* to *INSTALLED_APPS* in your 
settings.py?

On Thursday, December 29, 2016 at 11:30:16 AM UTC+1, ragini dahihande wrote:
>
> Hello Guys,
> I am new to django.
> I created sample project while running it I am getting following error
>
> django.template.exceptions.TemplateSyntaxError: *'static'* is not a 
> registered tag  library. Must be one of:
>
>
>
> *following is my index.html*
> {% load static %}
>
> 
>
>
> {% if latest_question_list %}
> 
> {% for question in latest_question_list %}
> {{question.
> question_text}}
> {% endfor %}
> 
> 
> {% else %}
>  No polls are available
> {% endif %}
>
> Thanks,
> Ragini
>

-- 
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/6b9edfd2-f1ec-4302-b4a2-92b3aa094df6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django-Channels strange slowdowns - how to profile?

[Andrew Godwin]

Hi Jakub,

There's no full profiling path yet - this is something I hope to work on as
we start integrating ASGI code at work early next year.

400ms for a request is already very long; I'm slightly concerned by that
(unless that's normal without Channels installed as well).

If you want to do a basic profiling test, you can just write a very basic
consumer that sends something onto the reply channel and then:

1) Directly inject requests into the channel layer from a python script,
listen for the response, and time the roundtrip. You can import
`channel_layer` from your project's `asgi.py` - if you don't have one the
docs talk about how to make one. You'll want to call
channel_layer.send("http.request", {"reply_channel": "http.response!test",
"path": }) and channel_layer.receive_many(["http.response!test"]).

2) Directly make HTTP requests on the server running Daphne to it via
localhost with a similar round trip measurement. Something like `ab` works
well for this; remember to either target a very simple view or compare it
with a similar test using a WSGI server.

Andrew

On Wed, Dec 28, 2016 at 7:31 PM,  wrote:

> My question from StackOverflow:
>
>
> My technology stack is Redis as a channels backend, Postgresql as a
> database, Daphne as an ASGI server, Nginx in front of a whole application.
> Everything is deployed using Docker Swarm, with only Redis and Database
> outside. I have about 20 virtual hosts, with 20 interface servers, 40 http
> workers and 20 websocket workers. Load balancing is done using Ingress
> overlay Docker network. Ouch, and I'm also using django-cacheops for low
> timeout caching (up to 15 min)
>
>
> The problem is, sometimes very weird things happen regarding performance.
> Most of requests are handled in under 400ms, but sometimes request can take
> up to 2-3s, even during very small load. Profiling workers with Django
> Debug Toolbar or middleware-based profilers shows nothing (timing 50-100ms
> or so)
>
>
> My question: is there any good method of profiling a whole request path
> with django-channels? I would like how much time each phase takes, i.e when
> request was processed by Daphne, when worker started processing, when it
> finished, when interface server sent response to the client. Currently, I
> have no idea how to solve this.
>
>
> EDIT:
>
> Some more information:
>
> Website isn't that big, it tops at 1k users online, with some real-time
> features like notifications, chat, and real-time updates of few views. It
> looks like sometimes website is "blocked", like communication between redis
> / interface servers / workers were incredibly slooow.
>
>
> Maybe you have some experience about server / worker ratios, fine tuning
> channel and redis settings?
>
>
>
> --
> 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/18cd97f8-5505-470b-8c22-3d97b1586d83%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/CAFwN1uq2my6o9pnU411%3D2FgXembGkFjMwP5kSV6K_qbFcMCv8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

django.template.exceptions.TemplateSyntaxError: 'static' is not a registered tag library. Must be one of:

[ragini dahihande]

Hello Guys,
I am new to django.
I created sample project while running it I am getting following error

django.template.exceptions.TemplateSyntaxError: *'static'* is not a 
registered tag  library. Must be one of:



*following is my index.html*
{% load static %}




{% if latest_question_list %}

{% for question in latest_question_list %}
{{question.
question_text}}
{% endfor %}


{% else %}
 No polls are available
{% endif %}

Thanks,
Ragini

-- 
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/4a53fbaf-db2b-4dd3-901f-37084bb9ab16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Just added Python, Django and MySQL integration template for easier data visualization with AnyChart JS

[andrey . khachaturov]

Hi all,

We at AnyChart JS Charts  have just released a 
series of 20+ integration templates to help web developers add interactive 
charts, maps and dashboards to web apps much easier, no matter what your 
technology stack is.

In particular, now there is a template for using our JavaScript charting 
libraries with Python, Django and MySQL 
 in 
our collection, distributed under the Apache 2.0 License and forkable on 
GitHub. (All technical integrations, just in case: 
http://www.anychart.com/integrations/.)

Check that out, and ask your questions if any. 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/aec8bb48-2ceb-4dcb-9486-d66b5b989bd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django doesn't email reporting an internal server error (HTTP status code 500)

[Luis Zárate]

try to change de django loggin

https://docs.djangoproject.com/en/1.10/topics/logging/#examples

2016-12-28 9:45 GMT-06:00 Philip Lee :

> Please help! The question are also posted here
> http://stackoverflow.com/questions/41363888/django-
> doesnt-email-reporting-an-internal-server-error-http-status-code-500
>
> I could send mail using the following code
>
> E:\Python\django-test\LYYDownloaderServer>python manage.py shell
> Python 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:01:18) [MSC v.1900 32 bit 
> (In
> tel)] on win32Type "help", "copyright", "credits" or "license" for more 
> information.(InteractiveConsole)>>> from django.core.mail import 
> send_mail>> send_mail(... 'Subject here',... 'Here is the 
> message.',... 'redstone-c...@163.com',... ['2281570...@qq.com'],...   
>   fail_silently=False,... )1>>>
>
> According to the doc
> 
> :
>
> When DEBUG is False, Django will email the users listed in the ADMINS
> setting whenever your code raises an unhandled exception and results in an
> internal server error (HTTP status code 500). This gives the administrators
> immediate notification of any errors. The ADMINS will get a description of
> the error, a complete Python traceback, and details about the HTTP request
> that caused the error.
>
> but in my case, Django doesn't email reporting an internal server error
> (HTTP status code 500) [image: enter image description here]
> 
>
> what's the problem? please help fix the problem
>
>
> settings.py
>
> """
> Django settings for LYYDownloaderServer project.
>
> Generated by 'django-admin startproject' using Django 1.9.1.
>
> For more information on this file, 
> seehttps://docs.djangoproject.com/en/1.9/topics/settings/
>
> For the full list of settings and their values, 
> seehttps://docs.djangoproject.com/en/1.9/ref/settings/
> """
> import os
> ADMINS = [('Philip', 'r234327...@163.com'), ('Philip2', '768799...@qq.com')]
> EMAIL_HOST = 'smtp.163.com'  # 'localhost'#'smtp.139.com'# EMAIL_PORT = 25# 
> EMAIL_USE_TLS = True
>
> EMAIL_HOST_USER = 'r234327...@163.com'  # '13529123...@139.com'
> EMAIL_HOST_PASSWORD = '**'# DEFAULT_FROM_EMAIL = 'r234327...@163.com'# 
> Build paths inside the project like this: os.path.join(BASE_DIR, ...)
> BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
>
> # Quick-start development settings - unsuitable for production# See 
> https://docs.djangoproject.com/en/1.9/howto/deployment/checklist/
> # SECURITY WARNING: keep the secret key used in production secret!
> SECRET_KEY = 's4(z8qzt$=x(2t(ok5bb58_!u==+x97t0vpa=*8bb_68baekkh'
> # SECURITY WARNING: don't run with debug turned on in production!
> DEBUG = False
>
> ALLOWED_HOSTS = ['127.0.0.1']#, '.0letter.com'
>
> # Application definition
>
> INSTALLED_APPS = [
> 'VideoParser.apps.VideoparserConfig',
> 'FileHost.apps.FilehostConfig',
> 'django.contrib.admin',
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',]
>
> MIDDLEWARE_CLASSES = [
> 'django.middleware.common.BrokenLinkEmailsMiddleware',
> 'django.middleware.security.SecurityMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.middleware.common.CommonMiddleware',
> 'django.middleware.csrf.CsrfViewMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
> 'django.contrib.auth.middleware.SessionAuthenticationMiddleware',
> 'django.contrib.messages.middleware.MessageMiddleware',
> 'django.middleware.clickjacking.XFrameOptionsMiddleware',]
>
> ROOT_URLCONF = 'LYYDownloaderServer.urls'
>
> TEMPLATES = [
> {
> 'BACKEND': 'django.template.backends.django.DjangoTemplates',
> 'DIRS': [],
> 'APP_DIRS': True,
> 'OPTIONS': {
> 'context_processors': [
> 'django.template.context_processors.debug',
> 'django.template.context_processors.request',
> 'django.contrib.auth.context_processors.auth',
> 'django.contrib.messages.context_processors.messages',
> ],
> },
> },]
>
> WSGI_APPLICATION = 'LYYDownloaderServer.wsgi.application'
>
> # Database# https://docs.djangoproject.com/en/1.9/ref/settings/#databases
>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3',
> 'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
> }}
>
> # Password validation# 
> https://docs.djangoproject.com/en/1.9/ref/settings/#auth-password-validators
>
> AUTH_PASSWORD_VALIDATORS = [
> {
> 'NAME': 
> 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
> },
> {
> 'NAME': 
> 'django.contrib.auth.password_validation.MinimumLengthValidator',
> },
> {
>   

Re: File/Folder Sync API?

[Luis Zárate]

Are you looking for something like webdav

https://github.com/meteozond/djangodav
http://django-webdav-storage.readthedocs.io/en/latest/

or something like dinamic dropbox storage

https://github.com/andres-torres-marroquin/django-dropbox


2016-12-28 12:15 GMT-06:00 Alexander Joseph :

> I'm building a collection of apps that write custom .docx and .xlsx files,
> and store them to a users account. These files need to be in a specific
> hierarchy and each user will have their own files/folders they can view and
> edit. It would really be great if I could allow each user to sync their
> files/folders to their local hard drives so they can view, print, etc. them
> outside of the web app. Does anyone know of a good API for doing this? I
> know SugarSync has an API but they charge their users something like $7/mo
> for their cheapest subscription. I'd like to make my apps free if at all
> possible. 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/57b50b62-6bce-4197-8414-2afd5be7943b%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
"La utopía sirve para caminar" Fernando Birri

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