Re: Form field labels change proposal

Good evening everybody. :) I would like to reference this ticket: https://code.djangoproject.com/ticket/26497#comment:11 It appears we stumbled over this issue as well while designing a new model form. Quoting my comment from the ticket: Would it make sense to separate concepts here? 1) *user

Re: Django template 'if ... is' feature design

Good evening everybody. That's my first post here, so let's how this works. :) This particular discussion caught my sight as it might introduce something really "low-level" functionality into the template engine. I can contribute here to the "design consideration" that from my experience with

Re: Making Django more PaaS-friendly

Hi James et al, In general, I like the idea of adding a helper to Django to read settings from the environment. I think this helper should be kept as simple and non-magical as is reasonable. Thus: - I'm in favor of a flexible helper function that can be manually used in a settings file to read an

Re: Reopening of Ticket "list_display does not allow functions of referenced objects (#5863)"

I believe https://code.djangoproject.com/ticket/10743 is an accepted ticket for this (limited to allowing referencing fields, but not methods, of related objects. On Wednesday, April 13, 2016 at 1:54:29 PM UTC-4, Olivier Dalang wrote: > > Dear List, > > The idea of allowing relations lookups in

Reopening of Ticket "list_display does not allow functions of referenced objects (#5863)"

Dear List, The idea of allowing relations lookups in the list display was proposed in ticket #5863 , but it was closed as wontfix 5 years ago. The reason it was closed as wontfix is because it's quite easy to achieve exactly the same result with a metho

Re: Form field labels change proposal

Thanks for these specific use cases, I'll see if I can come up with some acceptable solutions in a reasonable time On Apr 13, 2016 6:47 PM, "Tim Graham" wrote: > Took a quick look at djangoproject.com with this change. I noticed we're > using the label to construct an input placeholder [0]. I thi

Re: Form field labels change proposal

Took a quick look at djangoproject.com with this change. I noticed we're using the label to construct an input placeholder [0]. I think adapting that for this change isn't so easy to do in a cross-browser way via CSS [1] but we could add capfirst in the code. The question of a deprecation seems

Re: Land Information System in Django

The django-developers mailing list is for the development of Django itself. Please use django-users for questions like this. Did you find out about this mailing list from somewhere where this distinction isn't clear? On Wednesday, April 13, 2016 at 8:36:49 AM UTC-4, Wanjohi Kibui wrote: > > Hel

Re: Land Information System in Django

Hello Claude. Thank you for the response. The section that bothers me is not the GIS part .Its more of the django section.If I allow users to access the services in the LIMS, it means they will be filling in some forms and submitting the forms to the admin.My issues arises when I want to track t

Re: Land Information System in Django

Thank you for the reply.I do understand it's a difficult question but as I described it,not really sure how to put it.I have no issues with the GIS part.Am okay in that.The part that bothers me is when a client applies for a service by submitting a form, it's acted upon by different departments

Re: Enforcing a max size for form field values read into memory (review/determination of next steps needed)

This was deferred from 1.9 as it was still under review around the alpha deadline. I've updated the patch to merge cleanly and am asking for anyone interested in reviewing it to do so in the next month (ideally well before the May 16 alpha release date) so we can get it into 1.10. Thanks! https

Re: Making Django more PaaS-friendly

I like the try to move things towards this kind of settings more PaaS-friendly. As a Django user, I'd like to see 'DSN' or 'URL' for the database as a built-in in Django. I don't mind setting it in the dict as so: ``` DATABASES = { 'default': { 'DSN': 'postgres://user:password@ip:p