Re: Scaling Django for Multiple Teams

2016-04-18 Thread Ben Liyanage
My bad--see you guys on the other side. -Ben On Mon, Apr 18, 2016 at 5:31 PM, Tim Graham wrote: > This mailing list is for the development of Django itself. Please use > django-users for usage questions. Is there some place we could improve that > would have helped you identify the correct list

Re: Scaling Django for Multiple Teams

2016-04-18 Thread Tim Graham
This mailing list is for the development of Django itself. Please use django-users for usage questions. Is there some place we could improve that would have helped you identify the correct list? On Monday, April 18, 2016 at 8:11:38 PM UTC-4, bliy...@rentlytics.com wrote: > > Hey, > > I have two

Scaling Django for Multiple Teams

2016-04-18 Thread bliyanage
Hey, I have two issues I'm looking at solving at work, and I'm looking for a couple suggestions as to how other people have solved this. The two things are: * scale out their django installation to allow for smaller releases (I'm thinking microservices, but it could also be internal django ap

Re: Django template 'if ... is' feature design

2016-04-18 Thread Sven R. Kunze
Hi Tim, due to Stephen's response, my concerns are not valid. :) Still, my comments among your lines: Am Freitag, 15. April 2016 02:30:46 UTC+2 schrieb Tim Graham: > > Here are some examples of when the "is" operator isn't equivalent to "==". > > http://stackoverflow.com/questions/3647692/when-i

Re: Django template 'if ... is' feature design

2016-04-18 Thread Sven R. Kunze
Am Donnerstag, 14. April 2016 21:04:04 UTC+2 schrieb Stephen: > > > As far as I understand from > > https://github.com/django/django/pull/6442 > > it it deliberate that the if tag exposes the entire implementation detail. > > Thanks for clarifying. I didn't know that exactly this was a deliber