Fellow Report - March 20, 2015

Another round of security releases this week and lots of patch review for fixes and small features for 1.9 (and a couple small issues in 1.8). Report for week ending March 20, 2015: Triaged --- https://code.djangoproject.com/ticket/24490 - Add LogEntry.change_message when an object is

Re: improving debug logging in development

The lack of a fathomable way to get a functional logging config is a huge pain point :-) In this case, I wish we improve Django’s logging tools rather than document how to bypass them :-/ -- Aymeric. > On 21 mars 2015, at 19:24, Tim Graham wrote: > > I think the lack of an obvious way to

improving debug logging in development

I think the lack of an obvious way to get a useful logging config for local development is a pain point we could address. Here's a patch from a contributor based on a blog post by Dan Poirier [1]: https://github.com/django/django/pull/4362 Do you think this is a good suggestion or do you have a

Re: [GSoC] Switching to Jinja2 proposal

On Wednesday, March 18, 2015 at 4:44:05 PM UTC+1, Asif Saifuddin wrote: > > Hi, chris, > > So as django have the jinja 2 support out of the box what do you think the > direction of the ticket? https://code.djangoproject.com/ticket/15667 > > should the form rendering based on jinja2? or whats on ou

Re: Gsoc 2015: SQLAlchemy / NoSQL integration

Hi Abhishek, I am in the process of updating the mailer in the next month. I will let you know when this has been done. Regards, Daniel 2015-03-16 11:53 GMT+01:00 Abhishek Kumar : > Hi, > > I was trying to run the django-mailer > written by Daniel. On