Re: Issue with save/save_model/clean from admin (django 1.6.3dev)

Hi Stefano, You are leaving out important details -- the error you are getting is clearly about a "related field" (ForeignKey, OneToOne or ManyToMany), but there is no such field in the model you provided. I suspect it is more likely to be a usage issue rather than a problem in Django code or

Re: GSoC 2014 proposal [Improving error reporting]

On Tuesday, February 25, 2014 5:02:26 AM UTC+5:30, Tim Graham wrote: > > "Now I would like to know whether it would be suitable for GSoC?" > > Maybe! As these tickets touch many different aspects of Django, I'm > guessing you'll need to do quite a bit of research in order to convince us > you

Re: [GSoC] Switching to Jinja2 proposal

The link is here: http://pastebin.com/DWjE1axV It times only rendering -- templates are parsed and cached in the setup. On Tuesday, February 25, 2014 8:34:14 AM UTC+1, Curtis Maloney wrote: > > Did I miss the link to your benchmark code? > Does it time just rendering, or parsing also? > -- >

Re: Issue with save/save_model/clean from admin (django 1.6.3dev)

I _think_ your problem might lie in the confusion between "blank" and "null"; taken from https://docs.djangoproject.com/en/dev/ref/models/fields/#blank; null is purely database-related, whereas

Spell checker

Hi, I've added spell checker for documentation. Ticket: https://code.djangoproject.com/ticket/22141 and PR: https://github.com/django/django/pull/2354 In summary it allows to check documentation against typos. One disadvantage is that there must be wordlist for words, that are not recognized

Re: The unsettings project

Not sure whether this has already been covered. Maybe it is. I'd like to specify the settings as a class instead of a module. Mostly because I don't like the "from settings_local import *" pattern to extend some base settings with machine specific settings. By having the possibility to define

Re: GSOC 2014 Project Proposal

One more note in this thread: http://www.amazon.co.uk/The-Definitive-Guide-Django-Development/dp/1430258810 The Definitive Guide to Django is being revised. Apress has added Katie Cunningham to the author list, something that now I just remembered Jacob Kaplan-Moss mentioned to me in early

Re: [GSoC] Switching to Jinja2 proposal

> > What kind of support do you except for third-party template tags? Suppose, > that > `cycle` tag is not builtin. Would it be acceptable to write sth like that: > > dtl cycle '1' '2' as rows > > It could be quite easily implemented as a Jinja2 extensions. Of course, I > guess > that you'd

Re: [GSoC] Switching to Jinja2 proposal

Yah... my oops ... I was reading on my phone and missed the link :) On 25 February 2014 21:03, Christopher Medrela wrote: > The link is here: http://pastebin.com/DWjE1axV > > It times only rendering -- templates are parsed and cached in the setup. > > > On Tuesday,

Re: Django cross reference: www.xrefs.info

Hi John, Thanks, but for future reference - this isn't an appropriate topic for Django Developers. Django-dev is the mailing list for people wanting to contribute to Django. If you want to make a Django-related product announcement, use django-users instead. Yours, Russ Magee %-) On Tue, Feb

allow list_display in admin to traverse onetoonfields and foreign key relations

Hello, Right now I have a School model containing a OneToOne-relation to User. In the admin, in search_fields, I can use double underscores to search in related fields, for example: search_fields = ('place__name', 'school__name') But in list_display, I can't. For example, list_display

Re: [GSOC 2014 proposal] enhancing security features in django

Hi Prithviraj, I suspect the reason you haven't had a response is that there isn't much to respond to here. Regarding integrating django-secure -- I agree that this would be a worthwhile activity; it was part of the plan for last year's GSoC project on the validation framework, but got dropped

Re: allow list_display in admin to traverse onetoonfields and foreign key relations

I agree that the current behaviour is confusing and needs change in order to be DRY[1] and consistent[2]. [1] https://docs.djangoproject.com/en/dev/misc/design-philosophies/#don-t-repeat-yourself-dry [2] https://docs.djangoproject.com/en/dev/misc/design-philosophies/#consistency This is how

Re: GSoC 2014 proposal [Improving error reporting]

On Tuesday, February 25, 2014 5:02:26 AM UTC+5:30, Tim Graham wrote: > > "Now I would like to know whether it would be suitable for GSoC?" > > Maybe! As these tickets touch many different aspects of Django, I'm > guessing you'll need to do quite a bit of research in order to convince us > you

Re: GSoC 2014 proposal [Improving error reporting]

Regarding the 'improving error reporting' part, I have started with some issues which may be comparatively easier: Improving error reporting django.forms #15069 In forms.py: self._errors[name] = self.error_class(e.messages) When the list of errors is created, the value of the

#20824 - Email-based auth contrib module; some help required

Hi all, tl;dr; I've been working on a last little feature for 1.7 - an email-based User model for contrib, but I need some help/guidance on the last step - getting the tests working. The idea here is that we just ship a normal auth.User, but with email identification rather than username. This