Fellow Report - October 17, 2015

Report for week ending October 17, 2015: This week I spent three days at Microsoft HQ in Seattle at the first "open source data camp". As I understand it, the "data camps" are normally held to inform Microsoft partners about current and upcoming offerings in Microsoft cloud services and to

Re: Django 1.9 AppRegistryNotReady

This seems to be expected behavior, "In other words, your applications’ root packages and the modules that define your application configuration classes shouldn’t import any models, even indirectly." from https://docs.djangoproject.com/en/1.8/ref/applications/#how-applications-are-loaded You

Re: status of 1.9 release blockers

We're on schedule for Monday's beta release. Most of the backported fixes have been issues affecting 1.8 too. On Saturday, October 3, 2015 at 10:31:13 AM UTC-4, Tim Graham wrote: > > We've resolved a couple of release blockers on the stable/1.9.x branch > since the alpha, but overall bug

Re: Proposal: --debug-sql option for management commands

> On 17 oct. 2015, at 10:19, Claude Paroz wrote: > > I like the idea. However, instead of monkey-patching the Django > CursorDebugWrapper like DDT is doing now, I'd rather see a solution where we > use dynamic logging configuration to output the SQL commands, if possible.

Re: Proposal: --debug-sql option for management commands

I like the idea. However, instead of monkey-patching the Django CursorDebugWrapper like DDT is doing now, I'd rather see a solution where we use dynamic logging configuration to output the SQL commands, if possible. Claude -- You received this message because you are subscribed to the Google