Fellow Report - April 2, 2016

Triaged --- https://code.djangoproject.com/ticket/26413 - Abstract model inheritance regression with string model references in 1.9 (accepted) https://code.djangoproject.com/ticket/26418 - models.URLField does not validate with an rtmp:// url (wontfix) https://code.djangoproject.com/tic

Re: Add HTML5 required attribute on form widgets

On Wed, Mar 30, 2016 at 7:01 AM, Alex Riina wrote: > What's the plan for formsets with extra? > > I could see the required only getting applied to the first min forms but > I'm not sure there is an actual workable case there. It seems like it will > get too messy with adding and deleting at the s

Re: geodjango.org status

I'm not sure if that domain is under the control of the Django Software Foundation. It might be registered by Justin Bronn, the original author of GeoDjango. It looks like Justin works at Counsyl, which explains the last retweet on the Twitter account. On Saturday, April 2, 2016 at 10:12:22 AM

Re: Deprecating User.is_anonymous ?

> Do we know of any custom user models with this unconventional behaviour? FWIW, I have a project with the following code snippet: --- class AuthenticatedAnonymousUser(AnonymousUser): def is_authenticated(self): return True class AnonymousAuthenticationMiddleware(AuthenticationMidd

Re: Deprecating User.is_anonymous ?

On Sat, Apr 2, 2016 at 4:19 PM, Tim Graham wrote: > My concern is that if a project doesn't see the deprecation warnings > What about having a new property like User.authenticated (or User.anonymous)? User.is_anoymous and User.is_authenticated can be deprecate and removed from docs, leaving them

Re: Deprecating User.is_anonymous ?

Did you look into why both methods exist in the first place? I didn't know the reason. is_anonymous() preceded is_authenticated(). The concern was that template code like this: {% if not user.is_anonymous %}Content for logged in users.{% else %}Content for non-logged in users.{% endif %} wou

geodjango.org status

Hello, I'm working on issue #22274 and as part of this ticket I stumbled upon the domain geodjango.org website. I don't think this adds any value to GeoDjango, and in fact this is more a risk to confuse users by having an external website for a feature

Deprecating User.is_anonymous ?

I have been working on solving #25847 (making User.is_authenticated a property), and in the process I was wondering whether we want to keep User.is_anonymous at all in the long run. My reasoning is: - the documentation makes it quite clear you should use request.user.is_authenticated instead of r

Re: Annotate date intervals or ranges

On Monday 07 March 2016 12:20:59 Josh Smeaton wrote: > FYI I'm implementing date_trunc based transforms in this > patch: https://github.com/django/django/pull/6243 > > Since the transform names "__month" "__year" etc are already taken by the > Extract based transforms I've not yet implemented a lo

Re: Override the default form field for a model field

On Sat, Apr 2, 2016 at 10:44 AM, Florian Apolloner wrote: > Yeah, I am also mostly worried about this. formfield for me is a quick > shortcut, if you want to customize it, do it at the form level imo. Does this mean we can close #26369 ? -- You received this message because you are subscribed t

Help needed & Status of DEP0005 (middleware handling)

Hi, so here is a short update for DEP0005: I've moved from a branch on my private repository to a branch named dep0005 on Django to make it easier for core developers to push there and to allow others to easily make pull requests against it. The code as is works fine, the remaining tasks are b

Re: Override the default form field for a model field

On Thursday, March 17, 2016 at 2:17:40 PM UTC+1, Tim Graham wrote: > > It seems useful, but I'm not sure if it increases the coupling between > model and forms in an undesirable way? > Yeah, I am also mostly worried about this. formfield for me is a quick shortcut, if you want to customize it,

Re: Value of tightening URLValidator/EmailValidator regular expressions?

On Saturday 02 April 2016 09:44:54 Josh Smeaton wrote: > For what reason Zach? There is only one reason for which a strict and accurate validation is required, as far as I can see, and that is if your application is not just using existing email addresses (i.e. sending mail to users) but actual