Re: Official Projects DEP

I am happy to report that the Official Projects DEP, number 0007, was approved by the Technical Board and is now adopted as final! Andrwe On 4 Jul 2016 11:39 am, "Andrew Godwin" wrote: > I've revised the documentation section for clarity about external hosting, > and given the lack of further di

User representation on Django admin object history page.

Hello, I have been trying to update the user text on history of an object page. Looking into django source code I saw get_username being called directly. So overriding the __str__ method on User model will not update the User value on History page. Right now the __str__ method of an user is: def

Re: structural & functional review of django documentation

On Friday, January 1, 2016 at 11:48:24 PM UTC-5, Doug Epling wrote: > > Hey Tim -- > > Basically, we need data. My recommendation involves two separate > initiatives. > > First is, has been, a discussion open for spectators but limited > participants to core members. Asside from its subject

Re: status of 1.10 release blockers

Thank you for the update, Tim. #26888 will be taken care of by tomorrow. Either Marten or I are pushing a PR. Cheers, /Markus On Thu, Jul 14, 2016 at 06:41:51AM -0700, Tim Graham wrote: I'm planning for the release candidate on Monday. The one blocker is #26888

Re: Possible Bug in RegexURLResolver

Thanks everybody! While Aymeric's sounded great, your reasoning sounds even better, Marten. Thanks! Do you want to provide a PR for that, Marten? Cheers, /Markus On Thu, Jul 14, 2016 at 06:47:15AM -0700, Marten Kenbeek wrote: Using a singleton means that everything is cached for the lifetime

Re: Possible Bug in RegexURLResolver

Using a singleton means that everything is cached for the lifetime of the process after the resolver has been populated. The thread-local is so that concurrent calls to _populate() can correctly determine if it is a recursive call within the current thread. _populate() is called *at most* once

Re: status of 1.10 release blockers

I'm planning for the release candidate on Monday. The one blocker is #26888 - RegexURLResolver doesn't work in threaded environments. On Tuesday, June 21, 2016 at 4:29:47 PM UTC-4, Tim Graham wrote: > > The blocker is merged so I'll release the beta

Re: Possible Bug in RegexURLResolver

If you are using locals it means each thread will always end up calling the actual populate code? Is there any point for the RegexURLResolver class to be a singleton then? El jueves, 14 de julio de 2016, 9:12:54 (UTC-3), Marten Kenbeek escribió: > > It's not quite as simple. Concurrency is actu

Re: Possible Bug in RegexURLResolver

It's not quite as simple. Concurrency is actually not the main issue here. The issue is that self._populate() only populates the app_dict, namespace_dict and reverse_dict for the currently active language. By short-circuiting if the resolver is populating, you have the chance to short-circuit wh